[Imap-uw] x-imapbase timestamp field being rewritten
Oscar del Rio
delrio at mie.utoronto.ca
Sat Jun 14 07:56:39 PDT 2008
Andrew Tamm wrote:
> For some reason, the X-IMAP field (in particular the first number, the
> time stamp) is being rewritten to the current time instead of its
> original value. This causes all the messages to have new UIDL values,
> and so the POP client thinks that these are new messages. The field in
> question is:
>
> X-IMAP: 1213219525 0000000002
> Does anyone have any idea why that number would be changing?
SPAM with bogus headers?
We used to have this problem when using Unix mailbox format.
Every once in a while a SPAM comes with bogus headers
(X-UID, X-IMAPbase, etc) and the POP3/IMAP server has to
reindex all messages.
POP3 clients will see every message as new;
IMAP clients will reload all headers - they don't see duplicates but
a delay in "refreshing" the Inbox.
The fix is to either switch to mix format and/or filter out incoming
emails with bogus headers
Our procmail filters remove the following headers
^(X-UID|X-IMAPbase|X-IMAP|X-Status|Status|X-Keywords)
More information about the Imap-uw
mailing list