Just on one point, for us to consider: > Personally, I think mailing lists changing From has horrible UX and I don't > really think anyone disagrees. It's only advantages are that it's relatively > easy to implement in a Mailing List Manager (MLM) and it solves the entire > DMARC problem for a specific mailing list without needing anyone else to > change > anything. I understand the appeal.
I think Scott is right that we all agree that rewriting From mitigates problems that mailing lists have with DMARC, but at a significant cost in usability. I think it would be bad to publish From-rewriting as a standard. But here: I think it is reasonable, perhaps advisable, to informationally document From-rewriting as a mechanism that is in use, and to include in that documentation a clear exposition of the problems that it causes. Why not get those horrible UX issues down on paper so that when someone decides to deploy it they are better informed? Perhaps we can lead people to take steps to reduce the UX challenges (for example, rewriting the way the IETF is doing it at least addresses the issue of knowing who sent the message, and how to reply to the actual sender, as compared to a rewrite directly to the mailing list address). Doesn't that make sense? Barry _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
