Munge-from "From:" addresses and address auto-complete
We have a number of Mailman V2 lists with "Munge-from" turned on, due to DMARC issues at receiving mail systems. This rewrites the From: addresses to something like:
From: Dan Halbert via SOME-LIST SOME-LIST@example.org
The problem is some email clients (I'm not sure which ones) pick up these "From:" addresses and add them automatically to the user's address book. Then, when the user wants to send a private (not list) message to some person on the mailing list, they start typing the person's name, and the email client may autocomplete with the list address, not the person's address. If the sender doesn't check the address carefully, they may send to the list inadvertently. This has led to several mildly embarrassing private messages being sent to a list.
Is there some configuration I can set up that can alter these "From:" addresses to avoid putting the person's name first, but still including it? Or is there some other way to ameliorate this problem? We could choose something other than "Munge-from", but we do not want to lose the identity of the sender, which is worse.
We are using a third-party provider and have no direct control over the formatting of the rewritten "From:" header; I would change the Mailman code directly if I could.
Thanks, Dan
On 11/14/19 3:36 PM, Dan Halbert wrote:
Is there some configuration I can set up that can alter these "From:" addresses to avoid putting the person's name first, but still including it? Or is there some other way to ameliorate this problem? We could choose something other than "Munge-from", but we do not want to lose the identity of the sender, which is worse.
We are using a third-party provider and have no direct control over the formatting of the rewritten "From:" header; I would change the Mailman code directly if I could.
Changing the format of the munged From: header would require changes to the code in Mailman/Handlers/CookHeaders.py. There's no way to do this with list configuration settings.
The only other thing you could do is not apply DMARC mitigations to the From: header and set your list to not make DKIM breaking transformations to the message. See item 2) at https://wiki.list.org/x/17891458.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Dan Halbert
-
Mark Sapiro