[ mailman-Bugs-1126206 ] Bounce processing tracebacks

SourceForge.net noreply at sourceforge.net
Tue Feb 22 05:09:27 CET 2005

Bugs item #1126206, was opened at 2005-02-17 20:31
Message generated for change (Comment added) made by tkikuchi
You can respond by visiting: 

Category: bounce detection
Group: 2.1 beta
>Status: Closed
>Resolution: Postponed
Priority: 5
Submitted By: Bryan Fullerton (fehwalker)
Assigned to: Tokio Kikuchi (tkikuchi)
Summary: Bounce processing tracebacks

Initial Comment:

I was having some issues with bounces previously (some
were being held in qfiles/bounces until the Mailman
processes were restarted, then all of them would be
sent to the list owner as uncaught bounces). I believed
these were getting stuck because of the Mailman
2.1.5/python 2.4 "day of year out of range" issue,
which I've seen logged and which I know is fixed in
2.1.6, but maybe something else was breaking and not
being logged.

On upgrade to 2.1.6b4, all of the bounce messages stuck
in qfiles/bounce (1488 of them) were moved to
qfiles/shunt and the following traceback logged in
logs/error for each file:

Feb 17 15:12:22 2005 (31261) SHUNTING:
Feb 17 15:12:22 2005 (31261) Uncaught runner exception:
'str' object has no attribute 'get_sender'
Feb 17 15:12:22 2005 (31261) Traceback (most recent
call last):
  File "/usr/local/mailman/Mailman/Queue/Runner.py",
line 111, in _oneloop
    self._onefile(msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/Runner.py",
line 159, in _onefile
    sender = msg.get_sender()
AttributeError: 'str' object has no attribute 'get_sender'

Any idea what could cause this? Is this just an issue
with 2.1.5 -> 2.1.6 bounces or qfiles in general? The
'make install' did take a while doing something to my
qfiles at the end of the install process.



>Comment By: Tokio Kikuchi (tkikuchi)
Date: 2005-02-22 04:09

Logged In: YES 

Thank you for sending me the pck files. These files do
create your error but I also tried to reproduce the
situation without positive results. The error caused by
mailman2.1.5/Python2.4 combination leaves unprocessed
message in data directory and it is never processed again
because BounceRunner exits with error and new BounceRuuner
looks only for its PID marked pck file. You don't have to
re-process these error bounce messages because they are
stale after a few days (bounce score is incremented only
once a day). And, you will get more bounce messages to
process if the list is active.

I've already done install and de-install 2.1.5/2.1.6b4 three
times for tesing and think it's beyond the duty of an open
source developer. I mark this entry as 'postponed' (until a
few more similar reports emerge) and close this case.

I do believe you lose nothing if you simply remove


Comment By: Bryan Fullerton (fehwalker)
Date: 2005-02-22 01:02

Logged In: YES 

Emailed .pck files directly.


Comment By: Tokio Kikuchi (tkikuchi)
Date: 2005-02-21 00:25

Logged In: YES 

I guess this is one time error when you are upgrading from
2.1.5 to 2.1.6 under Python 2.4. If not, will you please
upload or send me a sample bouncing message?


You can respond by visiting: 

More information about the Mailman-coders mailing list