It appears that Murray S. Kucherawy <superu...@gmail.com> said: >-=-=-=-=-=- > >On Mon, Oct 21, 2024 at 8:51 AM Todd Herr <todd.herr= >40valimail....@dmarc.ietf.org> wrote: > >> Issue is here - >> https://github.com/ietf-wg-dmarc/draft-ietf-dmarc-dmarcbis/issues/155
I replaced the last paragraph of 7.4, Interoperability Considerations, with the text below. The last sentence is intended to avoid people saying let's just wait for DKIM2 which will fix everything. (I hope it will, but I don't want to wait five years to find out.) In practice, despite this advice, few Mail Receivers apply any mitigation techniques when receiving indirect mail flows, few organizations consider the effect of DMARC policies on their users' indirect mail, and it is unlikely that any advice in this document will change that. As a result, mail forwarded through mailing lists with unmodified From: header lines is frequently rejected due to a p=reject policy. In the ten years since large consumer mail systems started publishing p=reject policies, mailing list software has all adopted workarounds to make the From: header line DMARC aligned. Some simply use the list's address, while others do per-address modifications intended to be reversible or to allow mail to be forwarded back to the original author, e.g., b...@example.com turned into bob=example.com@user.somelist.example. While these workarounds are far from ideal, they are firmly established and list operators treat them as a fact of life. Mail developers have been trying for a decade to invent technical methods to allow mailing lists to continue to work without modifying the From: header line, such as the Authenticated Received Chain (ARC) protocol described in [RFC8617]. While work continues, none of the methods have become widely used and there is little reason to believe that any future methods will be more successful. R's, John _______________________________________________ dmarc mailing list -- dmarc@ietf.org To unsubscribe send an email to dmarc-le...@ietf.org
