[ mailman-Feature Requests-923122 ] reply_goes_to_list allow poster+list option

SourceForge.net noreply at sourceforge.net
Thu Nov 25 19:32:51 CET 2004

Feature Requests item #923122, was opened at 2004-03-25 14:01
Message generated for change (Comment added) made by shub
You can respond by visiting: 

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: karl berry (kberry)
Assigned to: Nobody/Anonymous (nobody)
Summary: reply_goes_to_list allow poster+list option

Initial Comment:
Right now, the reply_goes_to_list option allows (a)
poster, (b), list, and (c) explicit.  How about (d)
poster AND list?  That is, insert/override a reply-to:
header containing both the list name, and the original
reply-to (if present, else From: address).  For extra
credit, omit the original poster if they are a list member.

This would be very useful for a number of lists I
maintain, where 90% of the traffic is among the list
members (hence having a simple reply go to the list),
yet a few messages come in from the outside world
(hence including the original poster's address).

I'm using mailman 2.1.4 on GNU/Linux.

karl at freefriends.org


Comment By: Brad Knowles (shub)
Date: 2004-11-25 18:32

Logged In: YES 

The problem is that this idea is likely to cause a number of programs to 
break, probably pretty badly.

I think this is a very bad idea.  We don't want to be doing things to 
encourage people to break the standards, especially since most people 
who would use this option would not understand the true scope of the 

Using two "Reply-to:" headers doesn't resolve this issue, either.

If you want to munge the "Reply-to:" header to point back to the list, 
then Mailman gives you the ability to do that.  It's a bad idea, for the 
reasons laid out in the FAQ, but you do have that capability.


Comment By: karl berry (kberry)
Date: 2004-11-25 18:20

Logged In: YES 

I'm trying to help my users avoid a fairly common mistake,
not engage in arguments about standards. Fine,
Reply-to: list, poster
may not work for the population of some lists.  So those
lists won't enable it.

Meanwhile, it will help some people and lists, and there's
no other way to accomplish the behavior (that I know of). 
It's trivial to add and a tiny change in the user interface.  

I am not asking for per-user control of this, which is what
the FAQ entry you cited mostly discusses.  Obviously some
compromise has already been made with the "reply-to
considered harmful" stance.  (For which I am very thankful,
because it is very useful.)


Comment By: Brad Knowles (shub)
Date: 2004-11-25 15:26

Logged In: YES 

I don't think this is possible.  "Reply-to:" goes back to one address, not 
two.  The action of having multiple "Reply-to:" headers is also undefined, 
and some clients may work the way you want, while others may work in 
ways you do not.

Pretty much everything to do with "Reply-to:" is really a client problem, 
and needs to be solved there.  See <http://www.python.org/cgi-bin/
faqw-mm.py?req=show&file=faq03.048.htp> for details.


Comment By: URA Hiroshi (ura)
Date: 2004-05-10 10:44

Logged In: YES 

I uploaded the patch by different method. see following URL:


You can respond by visiting: 

More information about the Mailman-coders mailing list