Matthias Andree wrote:
Clint Sharp <clint(_at_)typhoon(_dot_)org> writes:
IMAP unique IDs are not globally unique, unlike POP3 UIDs. Also the
Unique IDs are not consistent between sessions (they are usually just
the message number in the mailbox which will change with an expunge).
The tuple (IMAP UIDVALIDITY value, Folder, UID) is unique
however. That's why there is a UID in addition to the message number.
If someone has interest I'd be willing to code a version of the patch
which will implement two UIDL methods, somewhat like POP3's does, which
for non-broken IMAP implementations will use IMAP
UID+UIDVALIDITY+Mailbox to determine the unique UID. Call it
imap_fastuidl :). However, it's not necessary in my implementation as I
have plenty of bandwidth between my fetchmail client and the IMAP
server, so I don't really need it. I don't see a way to auto-detect
this (unlike the POP3), so turning on the MD5 header-checksum method or
fastuidl method would require a configuration setting. There would then
also need to be discussion as to which one is the default (using
fastuidl would not be guaranteed to work on all IMAP servers, so I would
recommend against that being the default).
Anyone interested in this?
Clint