poor date parsing trips archiving

[Duchier]

With Mail 2.1.2, running the arch script produced some
bizarre output: messages whose date could not be
parsed were assumed to be of the current date.

I was able to cure the problem simply by updating
mailman/pythonlib/email/_parseaddr.py to the most
recent version from the python CVS.

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

[Thoover (thoover)]

I checked, and the _parseaddr.py on my system is identical
to the latest in CVS...I still have the problem. The arch
script won't parse dates in the format of:

Date: Sat, 17 Jan 2004 16:32:00 -0600

so it therefore converts the date to the current date:

Date: Fri Feb 20 09:43:05 2004

I wanted to change my local backup script to backup only the
*.mbox files (I would then recreate the html files using
'arch' in the event of a crash, etc), but for now I'm still
backing up everything.

[Duchier (duchier)]

thoover, you are mistaken - the version I fetched from the
python CVS parses such dates just fine. Also you said:
_parseaddr.py on your system - I am not sure what that means
- I was not refering to the version in your python installation -
that one is probably just fine - I was talking about the one in
the mailman installation - that's the one which is outdated.

Cheers,

[Thoover (thoover)]

I'd downloaded the latest version (1.7) of _parseaddr.py
from the python CVS, and compared it to the copy on my
system found at mailman/pythonlib/email/_parseaddr.py. They
both have an md5sum of:
   089bfb2cbae8f2e204f818d8c381d49e _parseaddr.py

Since I am obviously mistaken, could you please check the
md5sum of the file on your system, and let me know what it
is? Even better, could you give me the exact URL of the
correct file? (I downloaded mine from
http://cvs.sourceforge.net/viewcvs.py/python/python/dist/src/Lib/email/_parseaddr.py
(version 1.7, dated 6-13-03).

If this is the same file that you have, then there's
evidently another problem causing the 'arch' script to fail
to parse the dates correctly. (I am, however, running
Mailman 2.1.4...maybe another bug was introduced between
2.1.2 and 2.1.4?)

Thanks!