Hello, the connection breaks a couple of times per day. In the IMAP protocol log I see various errors like the following: 20:25:02.900 <<< y1303 OK STATUS completed.␍␊ 20:25:02.900 Model BAD response: y1283 BAD Command Error. 12 20:25:02.900 Imap::Mailbox::KeepMailboxOpenTask attached to adfasdfs Failed: The connection is being killed for unspecified reason 20:25:02.900 Imap::Mailbox::NumberOfMessagesTask attached to bleh Failed: The connection is being killed for unspecified reason 20:25:02.900 Imap::Mailbox::NumberOfMessagesTask attached to blah Failed: The connection is being killed for unspecified reason 20:25:02.900 Imap::Mailbox::NumberOfMessagesTask attached to blue Failed: The connection is being killed for unspecified reason [...] 20:25:02.900 *** Connection killed. 20:25:02.900 CantHappen The following command should have been handled elsewhere␍␊y1283 BAD Command Error. 12␊␊ Here is the IMAP server in use: Hostname: outlook.office365.com port: 993 Server: Microsoft.Exchange.Imap4.Imap4Server 15.20 name: Microsoft.Exchange.Imap4.Imap4Server version: 15.20 The following capabilities are currently advertised: IMAP4 IMAP4REV1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
The pop-up window when the error occurs shows: The IMAP server sent us a reply which we could not parse. This might either mean that there's a bug in Trojitá's code, or that the IMAP server you are connected to is broken. Please report this as a bug anyway. Here are the details: UnexpectedHere: UnexpectedHere y433 STATUS "Deleted Item* STATUS INBOX (MESSAGES 525 UNSEEN 0 RECENT 0) ^ here
That's a bug in Exchange I'm afraid. *** This bug has been marked as a duplicate of bug 417756 ***