Clint Sharp wrote:
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?
I'm interested. I use the courier imapd server on my server and the box
with the current patch implementation uses Communigate Pro. I'm willing
test those two
out when you have an updated patch available. This could be the start
of a compatibility
list for the UID+UIDVALIDITY+Mailbox uid feature.
I also have plenty of bandwidth between the client and server but I'd
prefer to minimize the amount used as a courtesy to the
other people who also use that server.