It appears that Todd Herr <[email protected]> said: >RFC 7960 isn't a specification for rewriting 5322.From per se, but section >4.1.3.1 discusses the topic of rewriting that header, including this text: > > Another option for ReSenders is to rewrite the RFC5322 ><https://www.rfc-editor.org/rfc/rfc5322>.From header > field address to a locally controlled address that will be forwarded > back to the original sender (subject to its own ReSender forwarding > mitigations).
This is my rewrite hack which approximately nobody does. I do it on my handful of lists, the IETF does with custom code, and commercial LISTSERV has an option to rewrite the address into <hash>@list.domain. To do so, the list software has to be able to futz with the configuration of the underlying MTA to manage the forwarding, and places running list software like Mailman and Sympa on top of postfix can't do that. (I think LISTSERV has a built in MTA but it is quite expensive.) What it does *not* say is to put the list address in the From header which is the ugly hack that list software has resorted to. See endless prior discussions of why that makes lists worse. Barry is right. If you don't care about interoperability, you can and will do whatever you want, but if you do, you don't set a DMARC policy on domains that send mail from people. R's, John _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
