GNOME Bugzilla – Bug 621890
Problems with automatic reconnect.
Last modified: 2014-01-15 17:50:59 UTC
If I hit cancel while waiting for a connection to an imapx server, the connection is aborted. However, a second connection attempt is made again immediately -- and _that_ one fails too, because camel_read() returns -EINTR because camel_operation_cancel_check(NULL) returns TRUE. All subsequent connection attempts will fail, because nothing ever clears the cancelled status. There are other issues in this area too -- if the server responds with a BYE message or there is some other fatal error, surely we shouldn't just be retrying over and over again? The account should be marked offline (if we had separate offline status per-account), or perhaps a dialog should pop up asking if the user wants to disable this account, go offline, or try again?
This was reproduced with a slow custom command (openssl s_client -connect somebox:993). For some reason openssl was doing something related to Kerberos which makes it take a while. You could perhaps reproduce with a command doing 'sleep 60 ; netcat %h %p'
I suppose this is obsolete, 2.30 is way too old. I'm opening a new bug report for 3.10, bug #722280, thus feel free to join the group there.