Regarding this section: Experience with DMARC has revealed some issues of interoperability with email in general that require due consideration before deployment, particularly with configurations that can cause mail to be rejected. These are discussed in Section 9.
I suggest replacing it with a scope statement, such as this: DMARC checks are applicable when a message is received directly from the domain owner, or received indirectly from a mediator without in-transit modification. As discussed in Section 9, these two criteria do not cover all legitimate email flows. When a message is received indirectly with modification, DMARC cannot produce a usable result, and the message should be evaluated using alternate criteria. When messages may have been forwarded with modifications, the algorithm for distinguishing between authorized and unauthorized messages becomes difficult to define. On Thu, Dec 31, 2020 at 12:51 PM John R Levine <jo...@taugh.com> wrote: > >> The main effect is that the mail they'd been sending from their ESP > >> with their Yahoo address on the From: line used to work, and now falls > >> on the floor or worse. > > > > Why can't the ESPs do From: rewriting? > > To what? The Yahoo address is the only address the scout troop has? > > Regards, > John Levine, jo...@taugh.com, Taughannock Networks, Trumansburg NY > Please consider the environment before reading this e-mail. https://jl.ly > > _______________________________________________ > dmarc mailing list > dmarc@ietf.org > https://www.ietf.org/mailman/listinfo/dmarc >
_______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
