OfflineIMAP crashes after resuming when IDLE is active

[John Wiegley]

>>>>> Julien Valroff <julien at debian.org> writes:

>> Hi, I was not involved in the IDLE code and I haven't looked deeply into
>> its workings. But a traceback would certainly help to see at which place it
>> crashes and where we might want to protect against closed connections.

> Sleeping for 2:00
> Exception in thread Thread-10:
> Traceback (most recent call last):
>   File "/usr/lib/python2.6/threading.py", line 532, in __bootstrap_inner
>     self.run()
>   File "/usr/lib/python2.6/threading.py", line 484, in run
>     self.__target(*self.__args, **self.__kwargs)
>   File "/usr/lib/pymodules/python2.6/offlineimap/imapserver.py", line 480, in idle
>     imapobj.noop()
>   File "/usr/lib/pymodules/python2.6/offlineimap/imaplib2.py", line 876, in noop
>     return self._simple_command('NOOP', **kw)
>   File "/usr/lib/pymodules/python2.6/offlineimap/imaplib2.py", line 1549, in _simple_command
>     return self._command_complete(self._command(name, *args), kw)
>   File "/usr/lib/pymodules/python2.6/offlineimap/imaplib2.py", line 1310, in _command_complete
>     typ, dat = rqb.get_response('command: %s => %%s' % rqb.name)
>   File "/usr/lib/pymodules/python2.6/offlineimap/imaplib2.py", line 172, in get_response
>     raise typ(exc_fmt % str(val))
> abort: command: NOOP => no response after 60.0 secs

I've seen this a lot too.  I changed my keepalive to 30 and that has seemed to
cure it so far.

John