It appears that Murray S. Kucherawy <[email protected]> said: >1) Are list operators and developers tolerating this situation, >temporarily, because they think this crew is going to come up with a less >disruptive permanent solution to which they expect to migrate one day? > >2) If not, have they resigned themselves to such things as From rewriting >as the way of the future?
In my experience, most list operators don't know much about mail, and twiddle list settings based on guesses and advice from other list owners to try and minimize complaints. I am on a list where they put the list's name and only the list's name in the From header. You literally cannot tell who sent a message if the authors don't put their name in the body. When I suggested to the list owners that they fix it, they basically shrugged, isn't that how lists work? On a list that I host for a folk dancing group, I have had this dialog at least five times: Owner: X and Y complained that they were unsubscribed, some evil person must be hacking the list! Me: No, when they report a list message as spam, their mail provider sends an unsubscribe message. Owner: They say they didn't do that. Me: Well, someone at their provider sent unsubs from their addresses. The logs don't lie. Owner: Oh. >3) If so, how big (or small) is the set of DMARC accommodations on which >they seem to be converging? The sophisticated ones do reversible address rewrites like we do, but that requires having access to the underlying MTA to reverse the rewrites. Everyone else munges the From header. If you're lucky they'll put the author's name in the From comment and the address in the Reply-To, but as often as not, they don't, probably because they don't understand why it matters. _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
