In article <ea2d0aea-5309-3d55-ab8e-f74dc328e...@spamtrap.tnetconsulting.net> you write: >-=-=-=-=-=- >-=-=-=-=-=- > >On 4/27/19 3:54 AM, Simon Lyall wrote: >> The below message was bounced by everyone (I assume) in the list whose >> address is hosted by gmail. > >I would be surprised if it was just Gmail.
I wouldn't. Gmail has made it quite clear that on their v6 mail servers they will only accept mail that is SPF or DKIM authenticated. If you don't authenticate, send to their v4 mail servers. I don't know anyone else who does that. I suspect that if mailop.org had an SPF record to match the list's envelope bounce address, this particular problem would go away. >It looks like Brielle's message was DKIM signed, modified in transit >(likely by the mailop mailing list), and subsequently rejected (or >otherwise penalized) by DKIM enabled recipients. That would be a pretty broken implementation of DKIM. The spec makes it absolutely clear that an invalid DKIM signature is the same as no signature at all. R's, John _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
