I'm not really sure what happens with message timestamps. I think it read's
the message's fstat.st_mtime and compares it to a date inside the message?
Sometimes it reports that there is a mismatch and sometimes not.
Apparently no problem with this guy's mailbox:
[r...@hawkmail1 tmp]# reconstruct -G -r user.bretzger
user.bretzger
user.bretzger.DELETED
user.bretzger.OUTBOX
But maybe there is:
[r...@hawkmail1 tmp]# reconstruct -r user
user: Mailbox does not exist (null) (hmmm well ok, I guess this does
not exist errmsg is legit)
user.bretzger timestamp mismatch 2768
user.bretzger timestamp mismatch 2769
user.bretzger timestamp mismatch 2771
user.bretzger timestamp mismatch 2836
user.bretzger
user.bretzger.DELETED
user.bretzger.OUTBOX
.
.
.
<control-c after a few more mailboxes are shown>
It seems like st_mtime is sometimes 1 second ahead of the date of the first
Received: header. Possibly because lmtpunix was operating right on the cusp of
a second-hand tick was writing out the message. Who knows.. boo.
Ok so heres the timestamp and contents of one mismatched message. I'm
expecting reconstruct to either fix the st_mtime, or to report the mismatch no
matter which way I run it.
[r...@hawkmail1 bretzger]# ls --full-time 2836.
-rw------- 10 cyrus cyrus 12844 2008-09-18 13:29:38.000000000 -0400 2836.
First four lines of 2836.:
Return-Path: <emeritus-xxx...@mail.monmouth.edu>
Received: from hawkmail.monmouth.edu ([unix socket])
by hawkmail.monmouth.edu (Cyrus v2.2.12-Invoca-RPM-2.2.12-9.RHEL4)
with LMTPA;
Thu, 18 Sep 2008 13:29:37 -0400
X-Sieve: CMU Sieve 2.2
Received: from mail.monmouth.edu (mail.monmouth.edu [192.100.64.12])
by hawkmail.monmouth.edu (8.13.1/8.13.1) with ESMTP id m8IHTYbV032125;
Thu, 18 Sep 2008 13:29:34 -0400
Date: Thu, 18 Sep 2008 13:29:25 -0400
.
.
.
