All,
The munged From: header in MM3 still says 'name' via ‘listname’ <‘listaddress’>
This caused me and my subscribers a lot of grief in MM2: Some mail clients use the first part up to the From for future key-ahead for new email to ’name’, hiding the address, so what they think is a personal message for ’name’, instead goes to the entire list. Red faces all around.
Stephen Thurnbull earlier suggested further munging by replacing the list address in the From: header like this:
'name' via ‘listname’ <‘whoopsieaddress’>
Which will return an automated reply explaining the issue. I like this option. How can I get that in?
Yours,
Allan Hansen allan_hansen@icloud.com
PS: I always use sender in Reply-To.
On 1/26/20 4:43 PM, Allan Hansen wrote:
All,
The munged From: header in MM3 still says 'name' via ‘listname’ <‘listaddress’>
This caused me and my subscribers a lot of grief in MM2: Some mail clients use the first part up to the From for future key-ahead for new email to ’name’, hiding the address, so what they think is a personal message for ’name’, instead goes to the entire list. Red faces all around.
Stephen Thurnbull earlier suggested further munging by replacing the list address in the From: header like this:
'name' via ‘listname’ <‘whoopsieaddress’>
Which will return an automated reply explaining the issue. I like this option. How can I get that in?
You can file an issue at <https://gitlab.com/mailman/mailman/issues>. That will at least get it on the table, but there are no guarantees as to if/when it would be implemented.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark, et al.,
I have entered a ticket at gitlab. Thanks.
Is there a way for me to make this change to the From header munging until it is implemented in the production version? I made MM2 do the munging using such a change on your recommendation and it has worked.
Our installation is from source, which might make it possible/easier?
I have played a lot with the wrapping option and have come to the conclusion that it will not work. In some cases, the Apple Mail client for the desktop simply did not display the internal message, while iOS worked fine. The header munging is safer.
Yours,
Allan Hansen allan_hansen@icloud.com
On Jan 26, 2020, at 22:32 , Mark Sapiro <mark@msapiro.net> wrote:
On 1/26/20 4:43 PM, Allan Hansen wrote:
All, The munged From: header in MM3 still says 'name' via ‘listname’ <‘listaddress’> This caused me and my subscribers a lot of grief in MM2: Some mail clients use the first part up to the From for future key-ahead for new email to ’name’, hiding the address, so what they think is a personal message for ’name’, instead goes to the entire list. Red faces all around. Stephen Thurnbull earlier suggested further munging by replacing the list address in the From: header like this: 'name' via ‘listname’ <‘whoopsieaddress’> Which will return an automated reply explaining the issue. I like this option. How can I get that in?
You can file an issue at <https://gitlab.com/mailman/mailman/issues>. That will at least get it on the table, but there are no guarantees as to if/when it would be implemented.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On 1/29/20 4:39 PM, Allan Hansen wrote:
Is there a way for me to make this change to the From header munging until it is implemented in the production version? I made MM2 do the munging using such a change on your recommendation and it has worked.
See <https://gitlab.com/mailman/mailman/issues/674#note_279196921>
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Allan Hansen -
Mark Sapiro