Section 3.1.2.3 is just wrong. EAI specifically does not allow for downgrading of messages in transit from UTF-8 headers to ASCII headers. ...
Yes not in transit, but the downgrade is likely to happen at the source be it the human or the MUA (I have not seen an implementation of such yet and I do have an EAI). Reworded to be clearer.
That makes no sense. If you send mail to a different address, that's what will get signed and it has no DMARC issues.
In section 4.5.1, another mailing list workaround is to rewrite the From: address into another address with an aligned signature that forwards to the original address. LISTSERV does this by rewriting to some random looking address in the list's domain, I do it by appending a local domain such as DMARC.FAIL.
Do we really want to create a non existing domain, without standardization? It is a bit the same as the group syntax, it just remove information to assess email reputation. I think this is not cool in these days of serious breaches due to email attacks.
Again, that makes no sense. I'm not aware of anyone advocating a "non existing domain." Could you explain what you mean here?
Regards, John Levine, [email protected], Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
