Michael Kabotwrote: >Configuration >- CentOS 5 64 bit >- Mailman 2.1.9 >- Qmail with Plesk 8.3 mods > >I have an interesting bounce issue occurring. >- Email is sent to a Mailman List >- List sends to each address >- One of the addresses bounces >- The bounce message ends with the right FROM and TO headers, but the wrong >RETURN-PATH and ERRORS-TO headers. > >Is this a Mailman or Qmail issue? > >Here is the bounce message > >------------------ >Return-Path: <[EMAIL PROTECTED]> >Received: (qmail 28263 invoked from network); 2 Jul 2008 14:46:36 -0400 >Received: from localhost (HELO [MAIL.RIGHTDOMAIN.COM]) (127.0.0.1) > by localhost with SMTP; 2 Jul 2008 14:46:36 -0400
It looks like below here up to my next comment are the actual bounce notice headers with Return-Path: <> indicating a null envelope from which should be the case for a normal bounce. The headers above here look like Mailman received this bounce and resent it to a list owner. When sending to a list owner, Mailman sets the envelope from the site list (mailman) -bounces address. Is [WRONGDOMAIN.COM] the domain of the site list? >Return-Path: <> >Delivered-To: [EMAIL PROTECTED] >Received: (qmail 28252 invoked for bounce); 2 Jul 2008 14:46:34 -0400 >Date: 2 Jul 2008 14:46:34 -0400 >From: [EMAIL PROTECTED] >To: [EMAIL PROTECTED] >Subject: failure notice And the header below may have also been added by Mailman in resending. >Errors-To: [EMAIL PROTECTED] > >Hi. This is the qmail-send program at [MAIL.RIGHTDOMAIN.COM]. >I'm afraid I wasn't able to deliver your message to the following addresses. >This is a permanent error; I've given up. Sorry it didn't work out. > >[BADEMAIL ADDRESS]: >[REMOTEIP] does not like recipient. >Remote host said: 550-5.1.1 The email account that you tried to reach does >not exist. Please >550-5.1.1 try double-checking the recipient's email address for typos >550-5.1.1 or unnecessary spaces. Learn more at >550 5.1.1 http://mail.google.com/support/bin/answer.py?answer=6596 >23si5229629hsd.10 >Giving up on [REMOTEIP]. > >--- Below this line is a copy of the message. > >Return-Path: [EMAIL PROTECTED] >Received: (qmail 28243 invoked from network); 2 Jul 2008 14:46:34 -0400 >Received: from localhost (HELO [MAIL.RIGHTDOMAIN.COM]) (127.0.0.1) > by localhost with SMTP; 2 Jul 2008 14:46:34 -0400 >Return-Path: [SENDEREMAIL] >Delivered-To: [EMAIL PROTECTED] >Received: (qmail 28072 invoked from network); 2 Jul 2008 14:46:32 -0400 >Received: [OMMITTED] >Received: [OMMITTED] >Message-ID: [OMMITTED] >Date: Wed, 02 Jul 2008 14:46:27 -0400 >From: [OMMITTED] >User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) >MIME-Version: 1.0 >To: [EMAIL PROTECTED] >Content-Type: text/plain; charset=ISO-8859-1; format=flowed >Content-Transfer-Encoding: 7bit >Subject: [members] whiter water trip update >X-BeenThere: [EMAIL PROTECTED] >X-Mailman-Version: 2.1.9 >Precedence: list >Errors-To: [EMAIL PROTECTED] > >[ORIGINAL MESSAGE] > >------------------ The thing that's strange in all the above is that Mailman (at least standard GNU Mailman) doesn't redirect bounces like this. It sends a totally new message to the list owner with the original bounce attached. Also, assuming [BADEMAIL ADDRESS]: in the notice was enclosed in <> as in <[EMAIL PROTECTED]>:, it would not have been an unrecognized bounce in 2.1.9. Is this Mailman 2.1.9 installed from our distribution, or is it a Plesk or other package? -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
