offlineimap stop working after update

[Nicolas Sebrecht]

On Mon, Jul 17, 2017 at 12:58:17PM +0200, Wojciech Żuk wrote:

>    I have these errors, when running offlineimap:
>    PLAIN authentication failed: command: AUTHENTICATE => socket error: <type
>    'exceptions.IOError'> - Too many read 0
>     LOGIN authentication failed: connection closed
>     ERROR: All authentication types failed:
>            PLAIN: command: AUTHENTICATE => socket error: <type
>    'exceptions.IOError'> - Too many read 0
>            LOGIN: connection closed
>    ERROR: Exceptions occurred during the run!
>    ERROR: All authentication types failed:
>            PLAIN: command: AUTHENTICATE => socket error: <type
>    'exceptions.IOError'> - Too many read 0
>            LOGIN: connection closed
>    Traceback:
>      File "/usr/share/offlineimap/offlineimap/accounts.py", line 278, in
>    syncrunner
>        self.__sync()
>      File "/usr/share/offlineimap/offlineimap/accounts.py", line 342, in
>    __sync
>        localrepos.getfolders()
>      File "/usr/share/offlineimap/offlineimap/repository/IMAP.py", line 452,
>    in getfolders
>        imapobj = self.imapserver.acquireconnection()
>      File "/usr/share/offlineimap/offlineimap/imapserver.py", line 540, in
>    acquireconnection
>        self.__authn_helper(imapobj)
>      File "/usr/share/offlineimap/offlineimap/imapserver.py", line 415, in
>    __authn_helper
>        "failed:\n\t%s"% msg, OfflineImapError.ERROR.REPO)
>    how to troubleshoot this?

Please, strip the non-significant quotes of the email while responding.

Too many read 0 is raised on network errors (disconnection). This might
happen on poor internet connection or if the sync is long and the server
decides to close the socket.

-- 
Nicolas Sebrecht