tags 485611 moreinfo thanks Re: Toni Mueller 2008-06-10 <[EMAIL PROTECTED]> > I often happen to want to catch up with a mailing list, and thus > download an archive, which I then subsequently merge into the current > mailbox for that list. Unfortunately, most mails, as archived by > Mailman's Pipermail at least, have this date format (example): > > Wed Jan 10 12:35:12 2007 > > while most mails which arrive through my mail server have this date > format: > > Mon, 09 Jun 2008 17:05:20 +0200
Hi,
I suspect the problem is that mutt doesn't parse the first form at all, but
instead looks at the date stored in the From_ line in the mbox. Depending on
how the mbox was generated, this timestamp is more or less useful, or just
random.
Could you send a mbox file which exhibits the problem you have?
I've tried constructing an example here by 'e'diting your mail:
1 2,4K Jun 10 14:10 Toni Mueller #485611 mu Bug#485611: mutt: date
display ofte
2 2,4K Jun 10 14:17 Toni Mueller └=>
Original:
From [EMAIL PROTECTED] Tue Jun 10 14:17:18 2008
Date: Tue, 10 Jun 2008 14:10:43 +0200
Modified:
From [EMAIL PROTECTED] Tue Jun 10 14:17:18 2008
Date: Wed Jan 10 12:35:12 2007
Quoting RFC 2822:
3.3. Date and Time Specification
date-time = [ day-of-week "," ] date FWS time [CFWS]
^^^
While mbox(5) (as shipped by mutt) claims that the date part of From_
lines is also formatted as in section 3.3, this seems wrong, and
qmail's (*cough*) mbox(5) [1] says:
| date is the delivery date of the message. It always contains
| exactly 24 characters in asctime format.
[1] http://www.qmail.org/man/man5/mbox.html
Christoph
--
[EMAIL PROTECTED] | http://www.df7cb.de/
signature.asc
Description: Digital signature
