Hello

> It???s imperative that you have rdns, spf, dkim and dmarc set up and that it all matches.
>
> My MTA will reject you if your ptr doesn???t match your a record and your helo/ehlo hostname. spf, skim and dmarc are all scored via spamassassin. Google rejects, outright, if there is any sort of mismatch in any of that at all. Setting up dnssec for your domain is also helpful.
>
> DNG list traffic comes through just fine.

But look here: This is the sending host for the DNG mailing list:

Received: from mail.dyne.org (ns3218761.ip-162-19-139.eu [162.19.139.95])

As you can see that reverse IP doesn't match what the SMTP server
connects as.

So I am actually not quite sure if your MX is as strict as you
claim it to be ? Or am I missing something ? Do you have a different
Received header - it should be one of the first lines of every message ?

And your server isn't alone in being not quite as strict as claimed:

Despite the received wisdom that one had to have
SPF+DKIM+DMARC+YOLO+SPQR+WTF :) set up to send mail to the
dominant email servers, this wasn't actually true: At least until last
week I managed to get mail accepted reliably by google despite having
only a proper MX and reverse DNS entry - nothing else, not even SPF.
And given that real people answered to those mails, most of them
did not end up in their spam folders either. But this seems to have
changed recently... hence this thread.

regards

marc