I've seen recent angst about DMARC on the IPv6 mailing list, but nothing against DKIM
Mailing lists only have problems with DMARC, not with DKIM. The problem we're looking at in -009 through -011 is a fairly exotic one, MSAs that rewrite headers after signing. The more typical path is that the message comes in, the MSA cleans it up (adds missing headers, rewrites obsolete syntax, etc.) and then signs it. Any MSA that works that way should have no problems.
-----Original Message----- From: UA-EAI <ua-eai-bounces@icann.org> On Behalf Of John Levine Sent: Tuesday, August 28, 2018 22:17 To: Evan Hanson <evanh@catalyst.net.nz> Cc: ua-eai@icann.org Subject: Re: [UA-EAI] EAI Evaluation - Phase 1
Hi again.
EAI-MTA-009, -010, -011 If this means you expect MSAs to re-code addresses or headers on the fly, they should not unless you can verify that they didn't break DKIM signatures when doing so.
Too true, I've added a note that DKIM should not be used for these test cases if the software applies recoding.
These days, if your MSA can't send mail with DKIM signatures, you're not going to get mail delivered. Perhaps split the test so that either the MSA passes through incoming signatures, or it applies them after any transformations.
Regards, John Levine, john.levine@standcore.com Standcore LLC
_______________________________________________ UA-EAI mailing list UA-EAI@icann.org https://mm.icann.org/mailman/listinfo/ua-eai
Regards, John Levine, john.levine@standcore.com Standcore LLC