[ mailman-Bugs-890732 ] poor date parsing trips archiving

SourceForge.net noreply at sourceforge.net
Fri Feb 20 12:28:52 EST 2004


Bugs item #890732, was opened at 2004-02-04 20:45
Message generated for change (Comment added) made by thoover
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=890732&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Denys Duchier (duchier)
Assigned to: Nobody/Anonymous (nobody)
Summary: poor date parsing trips archiving

Initial Comment:
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. 

----------------------------------------------------------------------

Comment By: Tom Hoover (thoover)
Date: 2004-02-20 17:28

Message:
Logged In: YES 
user_id=23321

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.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=890732&group_id=103



More information about the Mailman-coders mailing list