"ValueError: day of year out of range" on Dec 31?

Bug #266294 reported by Quinncom
2
Affects Status Importance Assigned to Milestone
GNU Mailman
Invalid
Medium
Unassigned

Bug Description

I haven't checked closely but I'm guessing the
following error is because

[root@one /var/mailman]# /etc/init.d/mailman stop
Traceback (most recent call last):
  File "/var/mailman/bin/qrunner", line 270, in ?
    main()
  File "/var/mailman/bin/qrunner", line 230, in main
    qrunner.run()
  File "/var/mailman/Mailman/Queue/Runner.py", line 82,
in run
    self._cleanup()
  File "/var/mailman/Mailman/Queue/BounceRunner.py",
line 139, in _cleanup
    self._register_bounces()
  File "/var/mailman/Mailman/Queue/BounceRunner.py",
line 129, in _register_bounces
    mlist.registerBounce(addr, msg, day=day)
  File "/var/mailman/Mailman/Bouncer.py", line 131, in
registerBounce
[root@one /var/mailman]# time.strftime('%d-%b-%Y',
day + (0,)*6))
ValueError: day of year out of range

[root@one /var/mailman]# date
Sat Dec 31 23:39:23 CST 2005

[root@one /var/mailman]# bin/version
Using Mailman version: 2.1.4

[http://sourceforge.net/tracker/index.php?func=detail&aid=1394696&group_id=103&atid=100103]

Revision history for this message
Tokio Kikuchi (tkikuchi) wrote :

time.strftime('%d-%b-%Y',day + (0,)*6)) caused error in
Python 2.4 and this was fixed in Mailman 2.1.6.

Please upgrade your mailman to the latest version.

Revision history for this message
N8wilson (n8wilson) wrote :

I got a similar/same error on Jan 10th - Mailman seems to
run for a while and spontaneaously do this - or maybe when
it gets a bounced message. I disabled bounce-detection in
hopes of it not occurring.
-------

[root@gttx nwilson]# Traceback (most recent call last):
  File "/usr/lib/mailman/bin/qrunner", line 270, in ?
    main()
  File "/usr/lib/mailman/bin/qrunner", line 230, in main
    qrunner.run()
  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 87,
in run
    self._cleanup()
  File "/usr/lib/mailman/Mailman/Queue/OutgoingRunner.py",
line 134, in _cleanup
    BounceMixin._cleanup(self)
  File "/usr/lib/mailman/Mailman/Queue/BounceRunner.py",
line 132, in _cleanup
    self._register_bounces()
  File "/usr/lib/mailman/Mailman/Queue/BounceRunner.py",
line 120, in _register_bounces
    mlist.registerBounce(addr, msg, day=day)
  File "/usr/lib/mailman/Mailman/Bouncer.py", line 131, in
registerBounce
    time.strftime('%d-%b-%Y', day + (0,)*6))
ValueError: day of year out of range
Traceback (most recent call last):
  File "/usr/lib/mailman/bin/qrunner", line 270, in ?
    main()
  File "/usr/lib/mailman/bin/qrunner", line 230, in main
    qrunner.run()
  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 87,
in run
    self._cleanup()
  File "/usr/lib/mailman/Mailman/Queue/BounceRunner.py",
line 220, in _cleanup
    BounceMixin._cleanup(self)
  File "/usr/lib/mailman/Mailman/Queue/BounceRunner.py",
line 132, in _cleanup
    self._register_bounces()
  File "/usr/lib/mailman/Mailman/Queue/BounceRunner.py",
line 120, in _register_bounces
    mlist.registerBounce(addr, msg, day=day)
  File "/usr/lib/mailman/Mailman/Bouncer.py", line 131, in
registerBounce
    time.strftime('%d-%b-%Y', day + (0,)*6))
ValueError: day of year out of range
[root@gttx nwilson]# exit
exit
[nwilson@gttx ~]$ date
Tue Jan 10 22:35:01 EST 2006
You have new mail in /var/spool/mail/nwilson
[nwilson@gttx ~]$ /usr/lib/mailman/bin/version
Using Mailman version: 2.1.5
[nwilson@gttx ~]$

Revision history for this message
Mark Sapiro (msapiro) wrote :

As Tokio says, this is a known incompatability between
Mailman 2.1.5 and earlier and Python 2.4 and later. It has
nothing to do with specific dates. It occurs whenever a
second or subsequent bounce is received for the same user in
the same day.

It is fixed by upgrading to Mailman 2.1.6 or later or by
changing
time.strftime('%d-%b-%Y', day + (0,)*6))
in line 131 of Mailman/Bouncer.py to
time.strftime('%d-%b-%Y', day + (0,0,0,0,1,0)))

See
<http://mail.python.org/pipermail/mailman-users/2005-March/043640.html>

And yes, disabling bounce processing will avoid the error.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.