Bug 64201

Summary: bounce processing broken
Product: [Retired] Red Hat Raw Hide Reporter: Matt Selsky <selsky>
Component: mailmanAssignee: John Dennis <jdennis>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0CC: ferulisses
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-06-06 09:53:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Matt Selsky 2002-04-29 00:55:54 UTC 
From Bugzilla Helper:

Description of problem:
mailman has the ability to auto-process bounce messages and then remove people 
from a mailing list or just stop attempting to deliver mail until mail deliver 
is reenabled.  Setting users to "no deliver" doesn't seem to work, but removing 
users does work.

How reproducible:
Always

Steps to Reproduce:
1. Set up a list.
2. Add a non-existant mail address to the list.
3. In the "Bounce Options" section of the admin page, set "Action when critical 
or excessive bounces are detected" to "Disable and notify me".
4. Send enough messages to the list so that it is considered excessive.  Watch 
the mailman logs to see when an excessive number has been reached.
	
Actual Results:  Nothing.  The fact that there had been an excessive number of 
failures was recorded in the logs, but the user was not shown as disabled on 
the "List members" page.  Also mailman continued to try to send mail to this 
person.

Expected Results:  Mailman should disable delivery of mail to this problem user 
and notify the list administrator.

Additional info:

I also tried setting the bounce action to "remove and notify me" and that *did* 
work.
Comment 1 John Dennis 2003-03-13 23:08:03 UTC 
I've recently picked up ownership of the mailman package and I'm going through
old bug reports. The current version is 2.1.1. I'm wondering if you've upgraded
and if you are still seeing this problem.
Comment 2 Matt Selsky 2003-07-22 09:15:31 UTC 
I don't have access to the machine that I reported the problem about anymore. 
Feel free to close.