On Thu, 18 Sep 2003, Helmut Michel wrote: >Yes, you are right. The failure was on my side. During testing i simply >moved a message from cur/ back to new/ not realizing that it's ID is >stored in the bincimap-cache file. So with really new mails (or deleting >the cache file) all works as expected.
In this case, what would happen is that the message would first appear to be expunged, then it would reappear with a new UID but the same sequence number. With the patch I posted, the arrival of this message (as you moved it from cur to new) should be detected correctly. But - it's not safe to move a message from cur to new, but if you do, you need to strip away the flags section ":2,..." because if not, Binc will skip it. Messages in new/ can not start with a dot '.', and they can not contain a colon ':' or a slash '/'. Andy :-) -- Andreas Aardal Hanssen | http://www.andreas.hanssen.name/gpg Author of Binc IMAP | "It is better not to do something http://www.bincimap.org/ | than to do it poorly."
