Message ID | 1561501810-25163-1-git-send-email-Hoan@os.amperecomputing.com (mailing list archive) |
---|---|
Headers | show |
Series | Enable CONFIG_NODES_SPAN_OTHER_NODES by default for NUMA | expand |
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 os.amperecomputing.com, but the DKIM signature is for amperemail.onmicrosoft.com. End result: it wil all go into the spam box of anybody who checks DKIM. Linus On Wed, Jun 26, 2019 at 6:30 AM Hoan Tran OS <hoan@os.amperecomputing.com> wrote: > > This patch set enables CONFIG_NODES_SPAN_OTHER_NODES by default > for NUMA. [...]
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 > os.amperecomputing.com, but the DKIM signature is for > amperemail.onmicrosoft.com. It appears Microsoft enables DKIM by default, but does so using keys advertised at *.onmicrosoft.com 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 issue. > End result: it wil all go into the spam box of anybody who checks DKIM. Interestingly, *some* receiving mail servers (at least gmail.com) 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. -Aaron