[Mailman-Users] Reply-To bug

Tokio Kikuchi tkikuchi at is.kochi-u.ac.jp
Fri Sep 29 12:31:49 CEST 2000

mailman-users-request at python.org wrote:

>   ------------------------------------------------------------
> Subject: RE: [Mailman-Users] bad Reply-To in subscription confirmation
> Date: Fri, 29 Sep 2000 11:10:09 +0100
> From: Richard Barrett <R.Barrett at ftel.co.uk>
> To: mailman-users at python.org
> I'm running 2.0beta6.
> I have found a definite bug (or is it a feature?) in the headers of
> outgoing confirmation requests.
> It appears that if:
> 1. The user is trying to subscribe from the web interface.
> 2. The reply_goes_to_list option on the General Options of a list is
> set to "This list" or "Explicit address" rather than poster then a
> Reply-To header is inserted.
> When the subscribing user tries to confirm by doing a simple reply,
> the reply does not get sent to the <list name>-request mail name but
> to the <list name> mail name of the explicit address.

Try this:

in Mailman/Handlers/CookHeaders.py

>     #
>     # Reply-To: munging.  Do not do this if the message is "fast tracked",
>     # meaning it is internally crafted and delivered to a specific user,
>     # or if there is already a reply-to set.  If the user has set
>     # one we assume they have a good reason for it, and we don't
>     # second guess them.
>     if not fasttrack or msg.get('reply-to'):
this line should be
      if not fasttrack and not msg.get('reply-to'):

Sorry but I have no time to use diff.


More information about the Mailman-Users mailing list