Hi, Cory! :-) On Wed, 18 Jun 2003, Cory Wright wrote: >Hi, >I am trying to migrate from Courier-IMAP to BINC, but I am running into >a few problems. In particular, I am seeing the following error *most* >of the time when I try to login via BINC: >In mutt I the following error: > 'unable to open "INBOX", uidvalidity bounced' >This happens most of the time, but not every time. What does "uidvalidity >bounced" mean? Is there some misconfiguration on my end? My bincimap.conf >file is almost the default, with only the pem file changed:
The logs should have also reported which message had the faulty uid value (noted). This happens if you have one or more message(s) in your folder that has a future timestamp (time(NULL) part of the file name). It often happens when sysadmins upgrade or move a depository to a machine whose clock is set wrong, a message gets delivered, and then the clock is adjusted back to normal. I did this myself (the clock was set to 7/3 when it should have been 3/7) and the result was that I had to shut down the mail system and run a perl script on all users' mailboxes. :-/ When Binc scans the depository with no cache file, it numbers the messages in the order that they were received. If a "new" message arrives with an "older" delivery time than one of the existing messages, then the IMAP invariant of strictly ascending UID values with regards to delivery time is broken, and Binc has to delete the cache file and renumber the messages. When doing this, UIDVALIDITY must bounce (increase by one). So the first thing I'd check is wether this is the case in your mailbox. Also, does this happen with all your mailboxes, or just with one? Andy :-) -- Andreas Aardal Hanssen | http://www.andreas.hanssen.name/gpg Author of Binc IMAP | Nil desperandum
