On Tue, 20 Jan 2004, Scott Parish wrote: >Btw, if you'd like to access that account the password that i kept on >XXXing out is "blahness" (without quotes)
Thanks. First things first: 1) Binc IMAP on your host prints this: 1 login [EMAIL PROTECTED] blahness 1 OK LOGIN completed 1 OK LOGIN completed That is - two LOGIN responses. Binc IMAP only prints one :-). Deliberately, anyway. But when I log out, x logout * BYE Binc IMAP shutting down x OK LOGOUT completed 1 select INBOX * 2 EXISTS * OK [UIDVALIDITY 1074575509] * OK [UIDNEXT 4] 4 is the next UID * FLAGS (\Answered \Flagged \Deleted \Recent \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)] Limited 1 OK SELECT completed Binc doesn't quit after the LOGOUT - it's still accepting commands in authenticated state. This is not the way Binc is designed to work ;-). Have you made any modifications to the source code? Could you show how your checkpassword replacement is implemented? Have you tested the system with the standard checkpassword and seen that it works well? 2) Too few messages are shown in the mailboxes. Please do a "find <path> -type f" where <path> is the path to [EMAIL PROTECTED]'s mailbox. We'll see then if there are actually messages in the mailbox or not. Binc IMAP may be using a completely different location for its mailboxes. This depends on where the checkpassword program takes it. When logging in and authenticating, check the pid of bincimapd, then look up /proc/<pid>/cwd and see where it points to. Then you'll be absolutely sure of what's going on. 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."
