On Monday, June 2, 2014 2:17:28 PM IST, Steve Dodd wrote:
OK, running with the patch, I had another problem today.
Thanks for testing the patch, Steve. This is appreciated.
09:36:02.059 <<< * 35 FETCH (UID 54)␍␊
09:36:02.059 <<< * BYE Internal error occurred. Refer to server
log for more information. [2014-06-02 09:36:02]␍␊
09:36:02.063 Imap::Mailbox::KeepMailboxOpenTask attached to
INBOX Failed: The connection is being killed for unspecified
reason
09:36:02.063 Imap::Mailbox::FetchMsgPartTask INBOX: parts
BINARY.PEEK[2] for UIDs 54 Failed: The connection is being
killed for unspecified reason
09:36:02.063 *** Connection closed.
This is an error with the IMAP server AFAIK, as opposed to a network error.
Trojitá didn't reconnect - it still dumped me in offline mode...
Firstly to clear, this is expected behavior. Trojitá (after the patch in
question) ensures that a user gets automatically reconnected incase of a
network error (any issues with the connection from the client to the
server). An Imap error (an error with the server) isn't handled this way,
and only an error message is thrown at the user.
Reconnect attempts after an Imap error can be good if it is a transient
error (something like a server reboot) but in the other case you may bump
into the same error very soon and not realise maybe something is needed to
be fixed on the server side. Do you have more information on what this
internal error with the server was?
Honestly, the auto-reconnect functionality can easily be extended to cover
Imap errors, but I am not sure if that would indeed be good to have. I
would like to hear what others have to say about this. :)
Cheers!
--
Karan Luthra
