Some bounces cause traceback after upgrading to Python 2.4
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Mailman |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Howdy,
I'm running Mailman 2.1.5 and upgraded from Python 2.3.4 to
Python 2.4 yesterday, and restarted all Mailman processes. Since
then I've gotten 9 tracebacks in the error log as below, with ~130
bounces processed successfully during that time. I've never seen
this error before with Mailman that I can remember.
Dec 03 07:48:21 2004 qrunner(47971): Traceback (most recent call
last):
Dec 03 07:48:21 2004 qrunner(47971): File "/home/mailman-2.1/
bin/qrunner", line 270, in ?
Dec 03 07:48:21 2004 qrunner(47971): main()
Dec 03 07:48:21 2004 qrunner(47971): File "/home/mailman-2.1/
bin/qrunner", line 230, in main
Dec 03 07:48:21 2004 qrunner(47971): qrunner.run()
Dec 03 07:48:21 2004 qrunner(47971): File "/home/mailman-2.1/
Mailman/
Dec 03 07:48:21 2004 qrunner(47971): self._cleanup()
Dec 03 07:48:21 2004 qrunner(47971): File "/home/mailman-2.1/
Mailman/
Dec 03 07:48:21 2004 qrunner(47971):
BounceMixin.
Dec 03 07:48:21 2004 qrunner(47971): File "/home/mailman-2.1/
Mailman/
Dec 03 07:48:21 2004 qrunner(47971):
self._register_
Dec 03 07:48:21 2004 qrunner(47971): File "/home/mailman-2.1/
Mailman/
Dec 03 07:48:21 2004 qrunner(47971):
mlist.registerB
Dec 03 07:48:21 2004 qrunner(47971): File "/home/mailman-2.1/
Mailman/
Dec 03 07:48:21 2004 qrunner(47971): time.strftime('%d-
%b-%Y', day + (0,)*6))
Dec 03 07:48:21 2004 qrunner(47971): ValueError : day of year
out of range
Do I need to do something with Mailman after updating to Python
2.4, or is this a bug?
Thanks,
Bryan
[http://
FWIW, I haven't seen any more of these tracebacks since Dec 3. It's
possible there were some bounces in the qfiles directory from Python
2.3, though I thought I'd checked for that. Or perhaps some bounce
messages generated by Python 2.3 came back in that made 2.4 unhappy.
In any case, this appears to just have been a transient thing. Feel free
to
keep this bug open, as a Python 2.4 testing datapoint perhaps, or close it
as you see fit.