Hello, all

I run c-client to an uw-imap server, and the mailboxes are in mbx format. I have been getting mailbox lock error messages, and these are totally disastrous, because the call fatal().

Here is an extract from my log files:
5/29/2005 8:41:26 PM: MailStream: INBOX Checkmail
5/29/2005 8:41:26 PM: Debug: 00000021 NOOP
5/29/2005 8:41:27 PM: Debug: * 1 EXPUNGE
5/29/2005 8:41:27 PM: mm_expunged: 1
.....
5/29/2005 8:42:37 PM: MailStream: INBOX Checkmail
5/29/2005 8:42:37 PM: Fatal - Lock when already locked, mbx={mail.tt-express.com:143/imap/tls/user="....."}INBOX

The CheckMail always does a mail_ping() first, and then if that fails, a mail_open(). All callbacks to mm_log and mm_dlog are printed in the log file, an extraction of which you see above. It looks as though either the mail_ping() failed (no "Debug" traceback) and an extra mail_open was issued even though the mailbox was open, or the mail_ping() itself caused the error. As you can see, it's been barely a minute since the last successful ping.

Is anyone able to enlighten me with respect to this error? It is particularly nasty since it calls fatal(), which kills everything. I can't have that happenning. Why would it call fatal in the first place instead of just returning an error? How can I make sure that the sequence I follow never hits this error? I don't want to change any c-client code, so I can't to do anything direct about the call to fatal(). That would really be my last resort.

Thanks very much for any ideas you might have.

Mike



_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw

Reply via email to