Comment 1 for bug 265829

After some investigation, the following (admittedly invalid) date headers
cause tracebacks similar to the above. After reformatting them I'm able to
generate the archive.

Date: 25 Aug 95 18.00
Date: Thursday, 30 October 1997 3:02pm PT
Date: Mon, 29 Nov 1999 Pacific Standard Time

Note that these messages *didn't* cause bin/arch|pipermail in mailman
2.0.x to fail, though it probably didn't parse them properly. Perhaps
trapping the error and/or skipping these messages might be more useful?

It also appears that bin/arch is throwing all messages with dates it can't
figure out (after the above were removed) into the current day. An example
can be seen at
http://lists.samurai.com/pipermail/bryans-list/2003-January/thread.html .
I'm unsure if there's any way to better handle this, but just wanted to
note it - I can create a separate bug report if it's important.

Thanks,

Bryan