Re: [trojita] Reconnecting after server errors

2014-06-07 Thread Jan Kundrát
On Wednesday, 4 June 2014 23:58:25 CEST, Steve Dodd wrote: Maybe the back off is the way to go then - unfortunately AIUI imap errors aren't nicely coded in the same way that SMTP errors are, so there's no chance to be smart and behave differently in response to different situations... I would

Re: [trojita] Reconnecting after server errors

2014-06-04 Thread Steve Dodd
On Wednesday, 4 June 2014 11:47:32 BST, Jan Kundrát wrote: What I'm especially worried is a situation where the remote server is just stubborn and refuses to work anymore, rejecting our connection attempts all the time. If Trojita just reocnnected, then we would be wasting the energy for nothi

Re: [trojita] Reconnecting after server errors

2014-06-04 Thread Jan Kundrát
On Monday, 2 June 2014 14:31:37 CEST, Steve Dodd wrote: My original issue though was with Gmail randomly closing the connection with "system error", in which case a reconnect would be nice.. I don't think we can automatically detect whether it is a good thing to reconnect or not. What I'm e

Re: [trojita] Reconnecting after server errors

2014-06-02 Thread Steve Dodd
On Monday, 2 June 2014 12:17:02 BST, Karan Luthra wrote: 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

Re: [trojita] Reconnecting after server errors

2014-06-02 Thread Karan Luthra
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 in

Re: [trojita] Reconnecting after server errors

2014-06-02 Thread Steve Dodd
OK, running with the patch, I had another problem today. This time I was running against dovecot locally, and it detected index corruption or some such: 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