MM2 adds the header "Sender: LISTNAME-bounces@DOMAIN" to messages sent to list members.
That causes Outlook (among others?) to display the "originator" of a message from a REAL POSTER as:
LISTNAME-bounces@DOMAIN on behalf of REAL POSTER <REAL.POSTER@DOMAIN>That phrasing helps identify instantly what list a message is coming from, when that list doesn't use a Subject prefix and when its address isn't in the To: or Cc: headers. (And it turned out that some of our list members were even relying on it to trigger security alerts!)
It doesn't look like there's any current MM3 setting that would accomplish the same result, so the question is: How difficult would it be to revive the Sender: header?
I admit that I didn't read all 285 Mailman-users search results for query "Sender:", so apologies if that had been discussed before.
Thanks.
On 11/30/21 7:51 PM, Philippe B wrote:
MM2 adds the header "Sender: LISTNAME-bounces@DOMAIN" to messages sent to list members.
That causes Outlook (among others?) to display the "originator" of a message from a REAL POSTER as:
LISTNAME-bounces@DOMAIN on behalf of REAL POSTER <REAL.POSTER@DOMAIN>
That phrasing helps identify instantly what list a message is coming from, when that list doesn't use a Subject prefix and when its address isn't in the To: or Cc: headers. (And it turned out that some of our list members were even relying on it to trigger security alerts!)
Mailman 2's adding of a Sender: header is an artifact from a time when some MTAs would return bounces to the Sender:. I think yours is the first comment I've seen that actually likes the way Outlook renders it. Most want to know how to prevent that which is why MM 2 has an option to not add it. As far as triggering alerts or filtering is concerned, there are other headers in list mail that can be used for that purpose.
It doesn't look like there's any current MM3 setting that would accomplish the same result, so the question is: How difficult would it be to revive the Sender: header?
By revive, do you mean add a feature in MM 3 to add a Sender: header. If so, you could submit a request at `https://gitlab.com/mailman/mailman/-/issues`. If you mean how difficult would it be for you to do it. here's a one line patch that will unconditionally remove any pre-existing Sender: header and add one with the list posting address. ``` --- a/src/mailman/handlers/rfc_2369.py +++ b/src/mailman/handlers/rfc_2369.py @@ -67,6 +67,7 @@ def process(mlist, msg, msgdata): ('List-Owner', '<mailto:{}>'.format(mlist.owner_address)), ('List-Unsubscribe', '<mailto:{}>'.format(mlist.leave_address)), ('List-Subscribe', '<mailto:{}>'.format(mlist.join_address)), + ('Sender', mlist.posting_address), )) if not msgdata.get('reduced_list_headers'): # List-Post: is controlled by a separate attribute, which is somewhat ``` -- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Philippe B