On 4/27/19 11:16 AM, John Levine wrote:
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.
Hum.
I suspect that if mailop.org had an SPF record to match the list's envelope bounce address, this particular problem would go away.
I'm surprised that mailop doesn't have an SPF record at all. I would have expected a fairly restrictive SPF record.
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.
Specs make a lot of things clear, including the intent of the spec. That doesn't stop people from consciously doing things contrary to the spec. After all, each email server operator is free to implement their server as they see fit.
Be it SPF or DKIM, I think that mailop should contemplate doing something. I'd personally like to see both.
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
