jameszee13 at gmail.com
Fri Jan 15 11:32:28 GMT 2016
Looks like I was wrong. I recall enabling IMAP IDLE a few days ago and
this likely coincides with when the deadlock began occurring.
I've disabled IMAP IDLE for now, but would be happy to help
troubleshoot with any interested developers if there's a desire to get
to the bottom of this.
On Fri, Jan 15, 2016 at 6:18 AM, James <jameszee13 at gmail.com> wrote:
> Been using offlineimap for years and love it. Thanks to those that
> have spent their time writing this awesome tool.
> It seems that in the last day or so something has happened that has
> resulted in offlineimap ceasing to function when checking email. After
> the 5min configured window (autorefresh = 5), offlineimap will attempt
> to sync with the mail server.
> *** Processing Account work
> INFO:OfflineImap:*** Processing account work
> Then nothing.
> I have to force the process to stop (CTRL + \), and based on the
> output it appears that the process is deadlocked. Several of the
> threads and the Sync Runner stop at line 340 of the python threading
> library, function waiter.acquire().
> Unsure where to start troubleshooting this. This was working fine
> until about 48hrs ago and haven't changed anything on my system.
> Any thoughts appreciated.
More information about the OfflineIMAP-project