[Mailman-Users] Interference from Cpanel mailman?
msapiro at value.net
Fri Jan 28 05:39:12 CET 2005
Glen Low wrote:
>I subscribe to the list and get a confirm message. I reply to the
>confirm message and the thelist-request mailbox receives it, and
>eventually I can see fetchmail delivering it to mailman, and the
>interface reports that I am subscribed, plus I get the "welcome to the
>list" message -- however -- I also got a Mail delivery failed message
>back, presumably from the (installed on my webhost?) Cpanel version of
>Mailman. I can't see how it would have intercepted the message.
>BTW, my instance of mailman is at www.pixelglow.com/lists/listinfo,
>whereas the Cpanel version is at www.pixelglow.com/mailman/listinfo.
>Perhaps I haven't created all the mailboxes at the web host that I need?
>Is the Cpanel mailman trying to intercept a mail going to one of the
>mailman-xxx mailboxes that I haven't created?
Probably not, but I suggest you add at a minimum
Monthly password reminders are sent from the mailman list so bounces
will go to mailman-bounces and then notifications will go to
mailman-owner. You might get away without mailman-admin as that is
just a historic synonym for mailman-bounces.
>Here's a partial listing of the spurious email, names changed to
>protect the innocent :-) ...
> From Mailer-Daemon at ESC13.midphase.com Thu Jan 27 23:36:09 2005
>Envelope-to: xxx.yyy at pixelglow.com
>Delivery-date: Thu, 27 Jan 2005 09:20:11 -0600
>Received: from mailnull by ESC13.midphase.com with local (Exim 4.43)
> id 1CuBRL-0006jn-OB
> for xxx.yyy at pixelglow.com; Thu, 27 Jan 2005 09:20:11 -0600
>X-Failed-Recipients: thelist-request at pixelglow.com
>From: Mail Delivery System <Mailer-Daemon at ESC13.midphase.com>
>To: xxx.yyy at pixelglow.com
>Subject: Mail delivery failed: returning message to sender
>Message-Id: <E1CuBRL-0006jn-OB at ESC13.midphase.com>
>Date: Thu, 27 Jan 2005 09:20:11 -0600
>This message was created automatically by mail delivery software.
>A message that you sent could not be delivered to one or more of its
>recipients. This is a permanent error. The following address(es) failed:
> pipe to |/usr/local/cpanel/3rdparty/mailman/mail/mailman request
> generated by thelist-request at pixelglow.com
> local delivery failed
>The following text was generated during the delivery attempt:
>------ pipe to |/usr/local/cpanel/3rdparty/mailman/mail/mailman request
> generated by thelist-request at pixelglow.com ------
>mailcmd script, list not found: thelist_pixelglow.com
>------ This is a copy of the message, including all the headers. ------
>Return-path: <xxx.yyy at pixelglow.com>
>Received: from [22.214.171.124] (helo=tibor.swiftdsl.com.au)
> by ESC13.midphase.com with esmtp (Exim 4.43)
> id 1CuBRK-0000NB-Ut
> for thelist-request at pixelglow.com; Thu, 27 Jan 2005 09:20:11 -0600
>Received: (qmail 25165 invoked from network); 27 Jan 2005 15:24:07 -0000
>Received: from unknown (HELO [126.96.36.199]) ([188.8.131.52])
> (envelope-sender <xxx.yyy at pixelglow.com>)
> by tibor.swiftdsl.com.au (qmail-ldap-1.03) with SMTP
> for <thelist-request at pixelglow.com>; 27 Jan 2005 15:24:07
>Mime-Version: 1.0 (Apple Message framework v619)
>In-Reply-To: <mailman.0.1106838849.4362.thelist at pixelglow.com>
>References: <mailman.0.1106838849.4362.thelist at pixelglow.com>
>Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>Message-Id: <E2E93E1C-7076-11D9-A360-000D9337BC48 at pixelglow.com>
>From: Glen Low <xxx.yyy at pixelglow.com>
>Subject: Re: confirm 0baaec9e8c3fbe754367e0add1846eed8d097681
>Date: Thu, 27 Jan 2005 23:19:49 +0800
>To: thelist-request at pixelglow.com
>X-Mailer: Apple Mail (2.619)
>It's all very puzzling since the thelist-request obviously got through
It puzzles me too, but it looks like the MTA that generated it is at
ESC13.midphase.com and is Exim 4.43.
I don't know if this is coming into play here, but Exim can be
configured to automatically recognize Mailman addresses and do the
piping without explicit aliases. If this is the cPanel web host (also
running Mailman) that you refer to, that's likely what's happening
here. There is an Exim configuration document at
http://www.exim.org/howto/mailman21.html which you might look at to
see if there might be a way to let Exim do its Mailman thing in
general and not do it for your lists.
Mark Sapiro <msapiro at value.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users