[ mailman-Bugs-1126206 ] Bounce processing tracebacks

SourceForge.net noreply at sourceforge.net
Thu Feb 17 21:31:11 CET 2005

Bugs item #1126206, was opened at 2005-02-17 15:31
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 

Category: bounce detection
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Bryan Fullerton (fehwalker)
Assigned to: Nobody/Anonymous (nobody)
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.



You can respond by visiting: 

More information about the Mailman-coders mailing list