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:   Thu, 27 Jun 2019 11:17:58 +0000
From:   Aaron Lindsay OS <>
To:     Linus Torvalds <>
CC:     Hoan Tran OS <>,
        Catalin Marinas <>,
        Will Deacon <>,
        Andrew Morton <>,
        Michal Hocko <>,
        Vlastimil Babka <>,
        Oscar Salvador <>,
        Pavel Tatashin <>,
        Mike Rapoport <>,
        Alexander Duyck <>,
        Benjamin Herrenschmidt <>,
        Paul Mackerras <>,
        Michael Ellerman <>,
        Thomas Gleixner <>,
        Ingo Molnar <>, Borislav Petkov <>,
        "H . Peter Anvin" <>,
        "David S . Miller" <>,
        Heiko Carstens <>,
        Vasily Gorbik <>,
        Christian Borntraeger <>,
        "open list:MEMORY MANAGEMENT" <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>,
        Open Source Submission <>
Subject: Re: [PATCH 0/5] Enable CONFIG_NODES_SPAN_OTHER_NODES by default for

On Jun 26 08:28, Linus Torvalds wrote:
> This is not a comment on the patch series itself, it is a comment on the emails.
> Your email is mis-configured and ends up all being marked as spam for
> me, because you go through the wrong smtp server (or maybe your smtp
> server itself is miconfigured)
> All your emails fail dmarc, because the "From" header is
>, but the DKIM signature is for

It appears Microsoft enables DKIM by default, but does so using keys
advertised at * domains, and our IT folks didn't
initially notice this. We believe we've rectified the situation, so
please let us know if our emails (including this one) continue to be an

> End result: it wil all go into the spam box of anybody who checks DKIM.

Interestingly, *some* receiving mail servers (at least were
reporting DKIM/DMARC pass for emails sent directly from our domain
(though not those sent through a mailing list), which I believe allowed
our IT to falsely think they had everything configured correctly.


Powered by blists - more mailing lists