lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 10 Aug 2018 11:28:53 +0300
From:   "Matwey V. Kornilov" <>
To:     Linus Torvalds <>
Cc:     Linux Media Mailing List <>,
        lkml <>,
        Tomasz Figa <>,
        Laurent Pinchart <>,
        Alan Stern <>,
        Ezequiel Garcia <>,
        Hans de Goede <>,
        Hans Verkuil <>,
        Mauro Carvalho Chehab <>,
        Steven Rostedt <>,,
        Mike Isely <>,
        Bhumika Goyal <>,
        Colin Ian King <>,
        Kieran Bingham <>,
Subject: Re: [PATCH v4 0/2] media: usb: pwc: Don't use coherent DMA buffers
 for ISO transfer

Hi Linus,

Thanks for pointing it out, I'll try to do my best to avoid this in future.

As I see now, in my case, the 'sender' in DKIM is triggered when using
GMail with alien domain in "Send From:".
I would not say that it is configuration "bug" (at least I can imagine
why do they do that), but it definitely must be avoided for maillists.
It is also interesting that if I use alien "From" email address with
google-apps (g suite) domain, then GMail generated two DKIM-Signature
headers, both for and for the google-apps domain.

2018-08-09 22:31 GMT+03:00 Linus Torvalds <>:
> Matwey,
>  your DKIM signature is garbage, and it causes your emails to be
> marked as spam when they go through a mailing list.
> The reason is this:
>   DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
>; s=20161025;
>         h=sender:from:to:cc:subject:date:message-id;
> where the problem is that the "sender" field is included in the DKIM
> hash calculation.
> That is completely incorrect, since a mailing list will - by
> definition - change the sender to the list, not the original sender.
> This is not a mailing list bug. This is a bug in your DKIM setup on
> the sending side.
> I'm leaving everybody cc'd., because this problem is starting to be
> annoyingly common. We had two people with addresses with
> the same misconfiguration, and I want people to be aware of this.
> I get too much email, and too much spam, and so when people have
> misc-onfigured email sending that causes problems for spam systems, it
> needs to get fixed.
> Your situation *may* be the same as the Chromium guys. Quoting Doug:
>  "Looks like it's all fixed.  Both Kees and I setup our
>   accounts a long time ago.  IIRC during that time the suggested way to
>   do things was that you'd use your SMTP settings even when
>   you were sending as your account.  These days it
>   doesn't appear that there's even any UI in gmail to configure things
>   that way, so presumably nobody else will be stuck in the same hole
>   that Kees and I were in"
> and he may have been wrong about that "presumably nobody else will be
> stuck in the same hole" guess.
> So you might want to check what the SMTP settings are for your setup.
>                Linus

With best regards,
Matwey V. Kornilov

Powered by blists - more mailing lists