[Mailman-Developers] [ mailman-Bugs-652001 ] Reply-to munging not using correct host

[noreply at sourceforge.net]

Bugs item #652001, was opened at 2002-12-11 07:43
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=652001&group_id=103

Category: mail delivery
Group: 2.1 beta
>Status: Closed
>Resolution: Works For Me
Priority: 5
Submitted By: David Gibbs (midrangeman)
Assigned to: Nobody/Anonymous (nobody)
Summary: Reply-to munging not using correct host

Initial Comment:
Mailman 5.1b6 is not using the lists configured host 
name for the reply_to address ... it is using the default 
host name instead.


I have mailman configured for virtual hosting ... the two 
hosts registered are 'midrange.com' 
and 'lists.fallingrock.net'.

Default.py has the standard:
add_virtualhost(DEFAULT_URL_HOST, 
DEFAULT_EMAIL_HOST)

and I've added the following to mm_cfg.py:
VIRTUAL_HOST_OVERVIEW = 1
add_virtualhost('lists.fallingrock.net', 'lists.fallingrock.net')

My test list is configured with:
host_name = 'lists.fallingrock.net'
first_strip_reply_to = 1
reply_goes_to_list = 1
reply_to_address = ''

When I post a message to my test list, the reply-to 
header reflects my DEFAULT host name instead of the 
list's host name...

>Return-Path: <beta-testers-
bounces@lists.fallingrock.net>
>Received: from linux.midrange.com (localhost 
[127.0.0.1])
>         by linux.midrange.com (8.11.6/8.11.6) with 
ESMTP id gB8FtTa02925;
>         Sun, 8 Dec 2002 09:55:29 -0600
>Received: from GRYFFINDOR.midrange.com 
(gryffindor.midrange.com
>         [192.168.1.100])
>         by linux.midrange.com (8.11.6/8.11.6) with 
ESMTP id gB8FtLi02900
>         for <beta-testers@lists.fallingrock.net>;
>         Sun, 8 Dec 2002 09:55:21 -0600
>Message-Id: 
<5.2.0.9.2.20021208095147.02ccf150@linux.midrange.c
om>
>X-Sender: david@linux.midrange.com (Unverified)
>X-Mailer: QUALCOMM Windows Eudora Version 
5.2.0.9
>Date: Sun, 08 Dec 2002 09:55:17 -0600
>To: beta-testers@lists.fallingrock.net
>From: David Gibbs <david@midrange.com>
>Subject: Re: [beta-testers] Up for another round?
>In-Reply-To: 
<5.2.0.9.2.20021208094537.02c70330@linux.midrange.c
om>
>Mime-Version: 1.0
>Content-Type: text/plain; charset="us-ascii"; 
format=flowed
>X-MailScanner: Found to be clean
>X-BeenThere: beta-testers@lists.fallingrock.net
>X-Mailman-Version: 2.1b5
>Precedence: list
>Reply-To: New Feature Beta Testers <beta-
testers@midrange.com>
>List-Id: New Feature Beta Testers <beta-
testers.lists.fallingrock.net>
>List-Unsubscribe: 
><http://lists.fallingrock.net/mailman2/listinfo/beta-
testers>,
> 
><mailto:beta-testers-request@lists.fallingrock.net?
subject=unsubscribe>
>List-Archive: 
<http://lists.fallingrock.net/mailman2/private/beta-
testers>
>List-Post: <mailto:beta-testers@lists.fallingrock.net>
>List-Help: <mailto:beta-testers-
request@lists.fallingrock.net?subject=help>
>List-Subscribe: 
<http://lists.fallingrock.net/mailman2/listinfo/beta-
testers>,
>         <mailto:beta-testers-
request@lists.fallingrock.net?subject=subscribe>
>Sender: beta-testers-bounces@midrange.com
>Errors-To: beta-testers-bounces@midrange.com



----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 23:40

Message:
Logged In: YES 
user_id=12800

I still cannot reproduce this.  When I turn the reply-to
options on I get the expected virtual host, regardless of
whether the host was my primary or secondary host.

Without the patch, I'm going to have to close this as
irreproducible.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=652001&group_id=103