[Mailman-Users] Automatic bounce processing; listname-bounces vs. listname-bounces+XXXX
John Wesley Simpson Hibbs
john at swajime.com
Sun Jan 4 01:30:10 CET 2009
On Fri, 2009-01-02 at 08:36 -0800, Mark Sapiro wrote:
> John Wesley Simpson Hibbs wrote:
> >Our mailing lists had been processing bounces correctly for quite some
> >For some reason though, this has stopped functioning properly.
> Did you just upgrade to Mailman 2.1.11?
No... we are still on 2.1.5
> Is it only password reminders that you are seeing as unrecognized
No... I've appended one that was not a password reminder to the end of this post.
> There are two things going on now. The password reminder wasn't VERP'd
> because this is controlled by VERP_PASSWORD_REMINDERS which is a
> separate setting in mm_cfg.py from those that control VERPing of list
I just now appended (per your advise) the following to mm_cfg.py:
VERP_PASSWORD_REMINDERS = Yes
VERP_PERSONALIZED_DELIVERIES = Yes
VERP_CONFIRMATIONS = Yes
I then did "service mailman restart" and sent a test message through.
Still no +VERP in the list-bounces at .
This is rather annoying, especially since I went to a lot of trouble
getting qmail to deliver the list-bounces+VERP to mailman in the first
place, and things were working for quite a while...
Any more suggestions?
> However, upon looking closer, I see that this probably isn't what's
> going on here, because the forward to the site list owner as above is
> not wrapped in an "unrecognized bounce" message.
> I tried running that message through the current recognizers, and it is
> recognized, so now it looks to me as if:
> 1) you have an older Mailman that doesn't recognize that particular
> bounce, and
> 2) You have not set "VERP_PASSWORD_REMINDERS = Yes" in mm_cfg.py.
> Actually, It is a good thing you saw this unrecognized bounce. Had it
> been recognized, it would have been ignored as the user probably isn't
> a member of the site list.
> What happens in these cases is a list member sets delivery off for some
> reason and then forgets about the list. Then the address dies and the
> only mail to the address is the monthly password reminder which even
> if it bounces and is recognized, never removes the dead address from
> the list of which it is a member.
>Subject: Uncaught bounce notification
>From: mailman-bounces at example.net
>To: list-owner at example.net
>Date: Sat, 20 Dec 2008 16:12:01 -0600
>Sender: mailman-bounces at example.net
>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:
>Delivered-To: 9-list-bounces at example.net
>Date: 20 Dec 2008 22:11:56 -0000
>From: MAILER-DAEMON at subscriber.example.net
>To: list-bounces at example.net
>Subject: failure notice
>We're sorry. There's a problem with the e-mail address(es) you're
>to send to. Please verify the address(es) and try again. If you
>to have problems, please contact Customer Support at (nnn) nnn-nnnn.
><somebody at subscriber.example.net>:
>child status 100...The e-mail message could not be delivered because
>the user's mailfolder is full.
>--- Below this line is a copy of the message.
>Return-Path: <list-bounces at example.net>
>Return-Path: <poster at poster.example.net>
>Delivered-To: 9-list at radiolists.net
>Date: Sat, 20 Dec 2008 17:11:34 -0500
>From: "Poster" <poster at poster.example.net>
>To: LIST <list at example.net>
>Subject: [LIST] _________
>X-BeenThere: list at example.net
>Reply-To: LIST <list at example.net>
>List-Id: LIST <list.example.net>
>Sender: list-bounces at example.net
>Errors-To: list-bounces at example.net
More information about the Mailman-Users