Bugs item #1421285, was opened at 2006-02-01 10:24
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1421285&group_id=103
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: bounce detection
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Matthias Andree (m-a)
Assigned to: Nobody/Anonymous (nobody)
Summary: 2.1.7 (VERP) mistakes delay notice for bounce
Initial Comment:
Greetings,
I just got the bounce action notice specified below.
I am running Mailman 2.1.7 with SF Patch #1405790 on
Python 2.3.4, SUSE Linux 9.2 i586, Postfix 2.2.9.
It appears as though Mailman 2.1.7 were not properly
detecting this apparently RFC-1894 compliant notice as
a "delayed" notice which is definitely a "soft bounce",
if it is supposed to contribute to the bounce score at
all.
I looked at Mailman 2.1.4 or so which appeared to make
efforts to not count "delayed"/deferral notices at all,
but that didn't work at the time for Postfix deferral
notices and was IIRC fixed later.
My setup is VERP enabled, uses VERP for almost
everything and uses monthly reminders for this list.
Jan 27 20:33:47 2006 (6794) leafnode-list:
admin@example.com has stale bounce info, resetting
Jan 27 21:57:08 2006 (6794) leafnode-list:
admin@example.com already scored a bounce for date
27-Jan-2006
Jan 30 18:16:47 2006 (6794) leafnode-list:
admin@example.com current bounce score: 2.0
Jan 30 19:40:06 2006 (6794) leafnode-list:
admin@example.com already scored a bounce for date
30-Jan-2006
Feb 01 03:01:40 2006 (6794) leafnode-list:
admin@example.com current bounce score: 3.0
Feb 01 03:01:41 2006 (6794) leafnode-list:
admin@example.com disabling due to bounce score 3.0 >= 3.0
Feb 01 03:31:41 2006 (6794) leafnode-list:
admin@example.com residual bounce received
I masked the list host by ... and the subscriber's
domain by example.com and the last two components of
the IPv4 address by X, without loss of accuracy I hope,
to protect the site from spammers.
Can anyone shed any light why Mailman 2.1.7 with said
patch considers the delay notice a "hard" bounce?
I don't have time to do debugging right now (end of the
month might work), but applying a patch will probably work.
-----------
This is a Mailman mailing list bounce action notice:
List: leafnode-list
Member: admin@example.com
Action: Subscription deaktiviert.
Reason: Excessive or fatal bounces.
The triggering bounce notice is attached below.
Questions? Contact the Mailman site administrator at
mailman@...
From: MAILER-DAEMON@... (Mail Delivery System)
Subject: Delayed Mail (still being retried)
To: leafnode-list-bounces+admin=example.com@...
Date: Wed, 1 Feb 2006 02:47:07 +0100 (CET)
This is the Postfix program at host ...
####################################################################
# THIS IS A WARNING ONLY. YOU DO NOT NEED TO RESEND
YOUR MESSAGE. #
####################################################################
Your message could not be delivered for 4.2 hours.
It will be retried until it is 7.0 days old.
For further assistance, please send mail to <postmaster>
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The Postfix program