[David Birnbaum]

Here's the headers for the reminder:

Return-Path: <mailman-owner@chelsea.net> Received: from killian.chelsea.net (localhost [127.0.0.1]) by killian.chelsea.net (8.9.3/8.9.3) with ESMTP id FAA15246 for <donad@gaigo.sundai.ac.jp>; Wed, 1 Mar 2000 05:52:23 -0500 (EST) Date: Wed, 1 Mar 2000 05:52:23 -0500 (EST) Message-Id: <200003011052.FAA15246@killian.chelsea.net> From: mailman-owner@chelsea.net Subject: thebody.com mailing list memberships reminder To: ###A USER### X-No-Archive: yes Precedence: bulk X-Mailman-Version: 1.1 Precedence: bulk List-Id: The Test List <test.chelsea.net>

It should be from (I think), thebody-admin@thebody.com, with an Errors-To: header.

Not sure why List-Id: is The Test List...that's odd.

That's because the script, while iterating through all lists, looks for the first "public" list. When found, that list is remembered, and that list's (fasttrack) delivery pipeline is used for sending out all the messages. As the "test" list is usually created pretty early on in any particular Mailman installation, it is not entirely uncommon that this list's List-Id: gets stuck on all password reminders...

Normally it is nice that Mailman indicates which list's fasttrack pipeline you received a particular message through, but I can see that it might be confusing in this situation.

However, a proper remedy is complicated by the lack of a list-independent Mailman mail address -- and thus, as Barry mentioned, also by the lack of a user database.

Harald