Hello, I'm just starting to investigate bincimap; since Courier-IMAP has introduced a blatant change to UIDL formats for POP3, this seems like a reasonable time to see about bailing out!
I've got a couple of questions which I couldn't find answered in the FAQ: 1. bincimap uses a 'checkpassword' interface, and looking at DJB's definition, it seems it just passes a username and password down a pipe. Does this mean that bincimap doesn't support SASL authentication? The documentation talks about disabling cleartext password mechanisms for non-TLS connections, which seems to imply that some non-cleartext mechanism must be available. 2. In the definition of IMAPdir, it says "One entry in an IMAPdir folder is a candidate for a mailbox". As an example, a file called "work" is shown as an mbox file, which maps to IMAP folder "work" So, how does this mechanism distinguish between mbox files, and metadata files like 'bincimap-subscribed', 'bincimap-uidvalidity' etc? Thanks, Brian.
