Kris Kelley writes:

Just to be thorough:  Due to a different problem, we had some message
files generated between 25 October and 28 October end up with incorrect
timestamps.  This resulted in the INTERNALDATE for these messages being
incorrect, even though the message headers had correct timestamps in all
the relevant places.
No.

                     Could that have somehow aggravated this UID
problem?  I'm ready to file this one under MS stupidity, but I want to
make sure there aren't any other influences I have control over that
might be factors.
See what the Maildir/courierimapuiddb file says (make sure you check the right folder's courierimapuiddb file). That's where messages' UIDs are saved. If you do not see any dupes there, OE definitely pulled it out of its ass.



-------------------------------------------------------
This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to