reply-to incorrectly added on administrative messages

[Dbadrak]

When the configuration parameter DEFAULT_REPLY_GOES_TO_LIST is set to 1 for
list or 2 for explicit address, and a message is sent for a subscription
request (administrative) to a single user, the Reply-To address is placed
in the message headers.

This isn't supposed to happen, since we don't want the reply for the
subscription to go to the list, we want it to go to the request address
(list-request).

I found the problem, in Handlers/CookHeaders.py. Line 79 should read
(Mailman 2.0b6):

    if not fasttrack and not msg.get('reply-to'):

I've submitted this in a patch (102090), since I don't see a way to answer
my own bug report. This will be easy for someone to close out.

[http://sourceforge.net/tracker/index.php?func=detail&aid=217522&group_id=103&atid=100103]

[Barry Warsaw (barry)]

This was fixed in revision 1.14 of CookHeaders.py (released as part of
Mailman 2.0rc1).