On 03/08/2016 04:42 AM, Sebastian Hagedorn wrote:
>
> Here are the culprits. They are now easy to find, because they are all
> new in the archive :-) (which is public, btw:
> <https://lists.uni-koeln.de/pipermail/linux-users/2016-March/thread.html>)
>
...
>
> Then there are a few broken spam messages:
>
> ----------------------
>
>> From [email protected] Mon Nov 7 14:13:18 2005
...
> Date: 18 ãöîáø 2000
>
>> From [email protected] Mon Nov 7 14:08:09 2005
...
> Date: Sun, 30 Jun 0102 17:30:47 -0600
>
>> From [email protected] Mon Nov 7 14:11:54 2005
...
> Date: Fri, 4 Feb 100 00:51:42 +0100 (MET)
I'm still having difficulty duplicating what you saw.
For the above three messages, the first one just gets detected as an
invalid date and archived under the current date by the current bin/arch.
The other two throw "ValueError: year out of range" at
File "/var/MM/21/Mailman/Archiver/HyperArch.py", line 984, in
dateToVolName
return time.strftime("%Y-%B",datetuple)
which is a problem, but not the one you saw. I would like to see
messages that cause this error
File "/usr/lib/mailman/Mailman/Archiver/HyperArch.py", line 601, in
_set_date
self.fromdate = time.ctime(int(self.date))
ValueError: timestamp out of range for platform time_t
that you reported. Can you find those bad messages in the .mbox input
file you used and send them to me?
--
Mark Sapiro <[email protected]> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
_______________________________________________
Mailman-Developers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
