Lindsay Haisley <[email protected]>
Date: Tue, 11 Aug 2009 13:02:55 -0500
To: [email protected]
Cc: Slim Richey <[email protected]>
>I have a list (several lists, actually) running on Mailman 2.1.11 and it
>looks as if bounce processing is broken. On the list in question, the
>following are set:
>
>bounce_processing = Yes
>bounce_score_threshold = 1.0
>bounce_info_stale_after = 1
>bounce_you_are_disabled_warnings = 0
>bounce_you_are_disabled_warnings_interval = 7
>
>/var/lib/mailman/logs/bounce shows many entry lines of this form, in
>sets of 3 as shown below:
>
>Aug 11 12:35:24 2009 (19017) listname: [email protected] bounce score: 1.0
>Aug 11 12:35:24 2009 (19017) listname: [email protected] disabling due to
>bounce score 1.0 >= 1.0
>Aug 11 12:35:24 2009 (19017) listname: [email protected] deleted after
>exhausting notices
>
>However, looking at the subscription roster or grepping for
>[email protected] using list_members indicates that the user is still
>subscribed, with no nomail flag set, and no notice is sent to the list
>owner.
This is a bug introduced in 2.1.11 and fixed in 2.1.12.
You should be seeing errors in Mailman's error log too.
The attached Bouncer_patch.txt will fix it.
--
Mark Sapiro <[email protected]> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
=== modified file 'Mailman/Bouncer.py'
--- Mailman/Bouncer.py 2008-06-20 19:47:28 +0000
+++ Mailman/Bouncer.py 2009-02-16 16:53:20 +0000
@@ -1,4 +1,4 @@
-# Copyright (C) 1998-2008 by the Free Software Foundation, Inc.
+# Copyright (C) 1998-2009 by the Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
@@ -163,8 +163,10 @@
# We've set/changed bounce info above. We now need to tell the
# MemberAdaptor to set/update it. We do it here in case the
# MemberAdaptor stores bounce info externally to the list object to
- # be sure updated information is stored.
- self.setBounceInfo(member, info)
+ # be sure updated information is stored, but we have to be sure the
+ # member wasn't removed.
+ if self.isMember(member):
+ self.setBounceInfo(member, info)
def disableBouncingMember(self, member, info, msg):
# Initialize their confirmation cookie. If we do it when we get the
------------------------------------------------------
Mailman-Users mailing list
[email protected]
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
