Turns out that others have had this problem. I finally solved it when I found that there were some lists that were working.

The problem was that in some places (on multiple servers) I had

listname-owner -> listname-admin

so when mailman sent a message out, it didn't get rewritten to the owner, but came back in on an address that made it look like a bounce. Not good.

I ran the genaliases program in the bin directory, ran that through AWK and blew away all of my old aliases files (on multiple servers!) and now all appears to be well.

So if you have this problem. Make sure that all your aliases are parallel (in an Euclidean geometry kind of way :-)

--Brett

On Tue, 2004-05-25 at 17:30, Brett Thorson wrote:

I just upgraded mailman from 2.0.something to 2.1.5. Everything went really well (thanks, that was great). However, I am running into one weird even that is occurring.

When a non-user sends a message that requires approval. The approval message gets sent from listname-owner to listname-owner. This address because of the setup I have actually gets routed off the box and then returns. And I think it is the returning to the box that makes mailman think that the message actually bounced. It seems to me that mailman should replace the To:listname-owner with the actual address of the list owner.

Below is the (Bounce message (approval message (message to approve))) encapsulated messages that have me mostly puzzled.

Any help?

Thanks.

--Brett

       From: 

mailman-bounces@ihavechangedthedomain.org To: stan-test-owner@ihavechangedthedomain.org Subject: Uncaught bounce notification Date: Tue, 25 May 2004 16:08:15 -0400

The attached message was received as a bounce, but either the bounce format was not recognized, or no member addresses could be extracted from it. This mailing list has been configured to send all unrecognized bounce messages to the list administrator(s).

For more information see: https://www1.ihavechangedthedomain.org/mailman/admin/stan-test/bounce

---

---

 From: 

stan-test-owner@ihavechangedthedomain.org To: stan-test-owner@ihavechangedthedomain.org Subject: Stan-test post from net@hand.co requires approval Date: Tue, 25 May 2004 15:50:43 -0400

As list administrator, your authorization is requested for the following mailing list posting:

List:    Stan-test@ihavechangedthedomain.org
From:    net@hand.co
Subject: test post
Reason:  Post by non-member to a members-only list

At your convenience, visit:

https://www1.ihavechangedthedomain.org/mailman/admindb/stan-test
    

to approve or deny the request. ---------------------------- ________________________________________________________________

 From: 

Net@hand.co To: stan-test@ihavechangedthedomain.org Subject: test post Date: Tue, 25 May 2004 15:40:46 -0400

Received: from odin.ihavechangedthedomain.org ([132.151.1.176] helo=ihavechangedthedomain.org) by megatron.ihavechangedthedomain.org with esmtp (Exim 4.32) id 1BShoW-0001yC-Fe for stan-test@megatron.ihavechangedthedomain.org; Tue, 25 May 2004 15:42:16 -0400 Received: from ihavechangedthedomain-mx (ihavechangedthedomain-mx.ihavechangedthedomain.org [132.151.6.1]) by ihavechangedthedomain.org (8.9.1a/8.9.1a) with ESMTP id PAA12488 for <stan-test@ihavechangedthedomain.org>; Tue, 25 May 2004 15:42:08 -0400 (EDT) Received: from ihavechangedthedomain-mx.ihavechangedthedomain.org ([132.151.6.1] helo=ihavechangedthedomain-mx) by ihavechangedthedomain-mx with esmtp (Exim 4.32) id 1BShoO-0006kN-O7 for stan-test@ihavechangedthedomain.org; Tue, 25 May 2004 15:42:08 -0400 Received: from exim by ihavechangedthedomain-mx with spam-scanned (Exim 4.12) id 1BShnk-0006gY-00 for stan-test@ihavechangedthedomain.org; Tue, 25 May 2004 15:41:29 -0400 Received: from responder.superspeedweb.net ([69.51.16.240]) by ihavechangedthedomain-mx with esmtp (Exim 4.12) id 1BShnD-0006c8-00 for stan-test@ihavechangedthedomain.org; Tue, 25 May 2004 15:40:55 -0400 X-Received: (responder i4PJeYk16689 for <stan-test@ihavechangedthedomain.org>); Tue, 25 May 2004 15:40:34 -0400 Received: (qmail 23578 invoked by uid 509); 25 May 2004 19:40:46 -0000 Message-ID: <20040525194046.23577.qmail@foreigner.superspeedweb.com> From: Net@hand.co To: stan-test@ihavechangedthedomain.org Subject: test post Date: Tue, 25 May 2004 15:40:46 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean X-MailScanner-From: net@hand.co X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ihavechangedthedomain-mx.ihavechangedthedomain.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL, NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: 7bit

test post --------------------------- ________________________________________________________________

 From: 

stan-test-request@ihavechangedthedomain.org Subject: confirm 3380c3ae38f7bbe478512ccb6c598779466e63e7

Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Subject: confirm 3380c3ae38f7bbe478512ccb6c598779466e63e7 Sender: stan-test-request@ihavechangedthedomain.org From: stan-test-request@ihavechangedthedomain.org Content-Transfer-Encoding: 7bit

If you reply to this message, keeping the Subject: header intact, Mailman will discard the held message. Do this if the message is spam. If you reply to this message and include an Approved: header with the list password in it, the message will be approved for posting to the list. The Approved: header can also appear in the first line of the body of the reply.

---

Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/