[ mailman-Feature Requests-1707731 ] Don't munge reply-to if one already exists -- feature reques

SourceForge.net noreply at sourceforge.net
Thu Apr 26 03:50:37 CEST 2007

Feature Requests item #1707731, was opened at 2007-04-25 15:13
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Knut Auvor Grythe (auvor)
Assigned to: Nobody/Anonymous (nobody)
Summary: Don't munge reply-to if one already exists -- feature reques

Initial Comment:
As you all know, a few (loud) users still seem to think reply-to header munging is a good idea, and thus I and many others feel forced to enable it on certain lists. This causes problems every time people would like a reply off-list, since people tend to reply to the list by mistake, obeying the munged reply-to. 

Turning off first_strip_reply_to looks like it would help at first glance, but it still requires users to edit the headers manually to remove the added list address, and many forget this.

A simple solution would be to simply allow leaving any existing reply-to-headers alone, and only add one if none are already defined. This way, the munging will act as a default, allowing the sender to override it by adding an explicit one.

The change should be fairly simple, and something similar to the attached diff should suffice. Naturally, the setting "leave_existing_reply_to_alone" would also have to be added and documented. The diff is just to illustrate the idea (although I can create a complete diff if you wish).


>Comment By: Mark Sapiro (msapiro)
Date: 2007-04-25 18:50

Logged In: YES 
Originator: NO

Per your comment I am moving this to Feature Requests. I'm sorry for the
confusion, but it's not my tracker either :-)


Comment By: Knut Auvor Grythe (auvor)
Date: 2007-04-25 15:28

Logged In: YES 
Originator: YES

Ooops. I didn't realize that the "Submit new" menu choice acted
differently based on where one was in the tracker when clicking it, and
expected to be able to mark the request as a feature request on the next
page or something. I'm very sorry about that. I'd normally try to clean up
after myself, but this time I expect I'd just worsen the mess :-|

As you've probably guessed, I've never used the SourceForge bugtracker
before ;-)


You can respond by visiting: 

More information about the Mailman-coders mailing list