It can happen the login is successful but the mailbox has disappeared. This error passes undetected by Claws Mail, which happily displays message list without warning. A log excerpt to show the problem (hostname mangled): [11:56:24] IMAP4< * OK aaa.bbb.ccc.es Cyrus IMAP4 v2.2.3 server ready * IMAP connection is un-authenticated [11:56:27] IMAP4> 1 CAPABILITY [11:56:27] IMAP4< * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE IDLE [11:56:27] IMAP4< 1 OK Completed [11:56:27] IMAP4> Logging mones to aaa.bbb.ccc.es using LOGIN [11:56:27] IMAP4< User logged in [11:56:27] IMAP4< Login to aaa.bbb.ccc.es successful [11:56:27] IMAP4> 3 LIST "" "" [11:56:27] IMAP4< * LIST (\Noselect) "." "" [11:56:27] IMAP4< 3 OK Completed (0.000 secs 0 calls) [11:56:27] IMAP4> 4 STATUS INBOX (MESSAGES UIDNEXT UIDVALIDITY UNSEEN) [11:56:27] IMAP4< 4 NO Mailbox does not exist ** IMAP error: STATUS error [11:56:27] IMAP4> 5 SELECT INBOX [11:56:27] IMAP4< 5 NO Mailbox does not exist ** IMAP error: SELECT error ** can't select folder: INBOX HTH and thanks in advance,
The error seems to be there and caught; you probably have a warning icon in the statusbar or a popup message depending on your preference in Preferences/Receiving ?
That would be nice, but no warning icon neither dialog appears, it simply says "Done." in the status bar like when everything goes okay, hence the bug. The error is correctly detected and shown in the log, as you point out, but such fatal messages (you cannot do much with a non existing mailbox) should be more noticeable to the user. Is it maybe a limitation of how fatality of an IMAP error is determined?
*** Bug 2908 has been marked as a duplicate of this bug. ***