On Wed 10/Jun/2026 13:32:24 +0200 Tero Kivinen wrote:
Alessandro Vesely writes:

Ietf.org does not have to do that, and I think it is bad idea that it does. This mungling was caused because people started complaining about DMARC, and the correct solution should have been to implement ARC in ietf.org mailing lists and users who subscribe the ietf.org mailing list should just configure to trust ARC-Authentication-Results of the ietf.org for ietf mailing lists.

It's that "should just configure". Until the list has some way to know whether a recipient has configured trust for the list's ARC assertions, it cannot rely on that trust being present and therefore cannot generally avoid From: munging. Without a mechanism to communicate or confirm the recipient's authorization policy, the mailing-list problem remains unsolved.

Mailing lists have all kind of per user configurations already, i.e., whether you want to get digests of the mailing list discussion or not, etc. Adding one more configuration parameter which can disable From mangling for that recipient would not be that difficult.


I wouldn't do it that way. Consider that all the other parameters that can be set by end users, while altering some characteristics of the communication, never put the communication itself at stake.


Then when user do add that list server to trusted forwarders list he could also go and turn off the list mangling option in the mailing list for him, and get emails without extra From address manglings.


Non-technical users cannot alter the configuration of their email servers, so it makes no sense for them to be able to say they have done so. However, having the recipient's postmaster communicate that to the mailing-list manager is just as straightforward.

Adding a "skip-From-munging" parameter is easy, but until such parameter is available, it is possible to use sibling lists, one that munges and one that doesn't.


Best
Ale
--







_______________________________________________
dmarc mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to