[ mailman-Bugs-420482 ] Bad info in monthly reminder headers

[SourceForge.net]

Bugs item #420482, was opened at 2001-05-01 12:35
Message generated for change (Comment added) made by robellis
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=420482&group_id=103

Category: mail delivery
Group: 2.0.x
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: D.J. Atkinson (deejster)
Assigned to: Nobody/Anonymous (nobody)
Summary: Bad info in monthly reminder headers

Initial Comment:
It appears that "Return-Path", "Sender", "Errors-
To", "X-BeenThere" are all being set to the incorrect 
list when sending out the monthly info.  [on the 4 
list servers that I run, it turned out to be the 
alphabetically first list in all 4 cases]

See the example below where dj at subscriber.com is a 
member of "junk" and "testa" yet "Return-
Path", "Sender", "Errors-To" and "X-BeenThere" are all 
attributed to the "alist", and if subscriber.com 
bounced the message for some reason, "alist-admin" 
would be wondering why s/he couldn't find him amongst 
the list members.  [BTW - this is information exactly 
as I received it for my subscriptions on one server.  
Domains and IPs are the only things changed (for 
privacy).]

In a perfect world this wouldn't be an issue, however, 
the poor admin of alist (example headers below) 
receives all the returns from all list reminders that 
get sent out every month (and is starting to get tired 
of it).  Wouldn't it be better if these were 
attributed to (one of) the list(s) that the subscriber 
is a member of?  Or if not that,  shouldn't they at 
least be attributed to mailman-owner (as in the "From" 
header field)?



Return-Path: <alist-admin at listhost.net>
Received: from listhost.net (listhost.net [10.0.0.1])
	by mail.subscriber.com (8.9.2/8.9.2) with SMTP 
id FAA01735
	for <dj at subscriber.com>; Tue, 1 May 2001 
05:06:37 -0600 (MDT)
Received: from listhost.net (localhost [127.0.0.1])
	by listhost.net (8.9.3/8.9.3) with ESMTP id 
FAA18897
	for <dj at subscriber.com>; Tue, 1 May 2001 
05:06:18 -0600 (MDT)
Date: Tue, 1 May 2001 05:06:18 -0600 (MDT)
Message-Id: <200105011106.FAA18897 at listhost.net>
Subject: listhost.net mailing list memberships reminder
From: mailman-owner at listhost.net
To: dj at subscriber.com
X-No-Archive: yes
X-Ack: no
Sender: alist-admin at listhost.net
Errors-To: alist-admin at listhost.net
X-BeenThere: alist at listhost.net
X-Mailman-Version: 2.0.1
Precedence: bulk
X-UIDL: c3f7736e3c6bdbe9eb75e264e35e8768

<standard message body snipped>

Passwords for dj at subscriber.com:

List                                     Password // 
URL
----                                     --------  
junk at listhost.net                        <pw>    
http://listhost.net/mailman/options/junk/dj%
40subscriber.com

testa at listhost.net                       <pw>    
http://listhost.net/mailman/options/testa/dj%
40subscriber.com


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

Comment By: Rob Ellis (robellis)
Date: 2003-12-08 11:38

Message:
Logged In: YES 
user_id=338888

A fix/workaround for anyone who might still be running 2.0.x --
create a list for sending password reminders, e.g.
'mm-reminders',
and make this change to cron/mailpasswds:

<     a_public_list = None
---
>     # a_public_list = None
>     some_admin_list = 'mm-reminders'
>     a_public_list = MailList.MailList(some_admin_list, lock=0)

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-04-05 14:07

Message:
Logged In: YES 
user_id=12800

Note that in MM2.0, all reminders appear to come from the
first public list at your site.  This is a design flaw
that's fixed in MM2.1.

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

Comment By: Russell Whitaker (whitaker)
Date: 2001-12-10 19:59

Message:
Logged In: YES 
user_id=68054

I should have added this information: the problem was seen
in our (my company's) Mailman 2.0.6 and 2.0.8 installations.

In the meantime, we have disabled the monthly 'mailpasswds'
cron entry for security reasons.

Russell Whitaker

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

Comment By: Russell Whitaker (whitaker)
Date: 2001-12-10 19:57

Message:
Logged In: YES 
user_id=68054

Is this issue fixed in subsequent (post 2.0.1) versions
of Mailman?  For that matter, is this issue going to be
assigned a fixer?

Thanks,
Russell Whitaker

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

Comment By: Paula B Morrison (morri027)
Date: 2001-08-06 11:38

Message:
Logged In: YES 
user_id=290757

We are experiencing the same problem - the return mail for all lists is going to the administrators of 
another list.  However, the list that is getting the return mail is NOT the first list alphabetically.

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

Comment By: Sean Reifschneider (jafo)
Date: 2001-05-03 02:16

Message:
Logged In: YES 
user_id=81797

Hmm, I just verified this on one the messages sent out on
one of our boxes running Mailman 2.0.4.  FYI.

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

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