search

OfflineIMAP / offlineimap

Read/sync your IMAP mailboxes (python2) [LEGACY: move to offlineimap3]
http://www.offlineimap.org
Other
1.78k stars 361 forks source link

Attempting NOOP on dropped connection #69

Open sven-strothoff opened 10 years ago

sven-strothoff commented 10 years ago

I am running OfflineIMAP 6.5.5 on OS X. I have launchd configured to start OfflineIMAP in the background. I sync a single IMAP mailbox to a local MailDir. OfflineIMAP is working fine for some time, but then no more mails arrive. If I take a look at the logs the last entries are always (except the thread numbers of course):

Thread-655:
 Attempting NOOP on dropped connection imap.zoho.com
Thread-657:
 Attempting NOOP on dropped connection imap.zoho.com
Thread-656:
 Attempting NOOP on dropped connection imap.zoho.com

I suspect that it happens when the computer was entering sleep state or the internet connection dropped. Even though OfflineIMAP is still running it never recovers from the connection loss and I have to kill it and start it again.

At first I was using IDLE, but after I read that it is still experimental I thought it might be he culprit here, but the behaviour is still the same after dialling IDLE.

I found some discussion of the NOOP message on some mailing list archive, but that was several years old, so I am not sure if it was ever resolved or if this is a new issue.

If you tell me what you need I am happy to add additional information or debug logs. I would gladly help in resolving this issue, however I have no idea where to start looking on my own…

quite commented 10 years ago

Also see #56

darnir commented 9 years ago

I am experiencing the same issue on ArchLinux with offlineimap 6.5.6 The socktimeout variable that helped in #56 does not fix this issue.

In fact, I haven't put my machine to sleep at all, and internet connectivity hasn't broken either. But very often I see the above error, after which all synchronization stops. My offlineimap has been displaying this error for the last 45 minutes now, with no updates.

Will test against offlineimap-git and update with findings

darnir commented 9 years ago

A little more digging showed PEBKAC. I had a very high value for keepalive assuming that $keepalive is the amount of time for which a connection will be kept open, not the interval at which KA messages are sent.

Fixing the keepalive value, fixed the issue for me.

nicolas33 commented 9 years ago

We might still want to close offlineimap after n NOOP rather than looping indefinitely.

quite commented 9 years ago

Yeah. I'm living with a cronjob uses netstat to see if the connection to my imap server is alive, and a -9 if it's not. But that's OK too. : )

sc68cal commented 8 years ago

I'm highly mobile with my laptop, moving between WiFi networks (commute between home and office) - and I had offlineimap running via launchd and basically just pkill -9 -f offlineimap whenever it misbehaves.

The log message:

 *** Finished account 'personal' in 0:02
 Next refresh in 5.0 minutes
 Next refresh in 4.0 minutes
 Next refresh in 3.0 minutes
 Next refresh in 2.0 minutes
 Next refresh in 1.0 minutes
 *** Processing account personal
Thread-59:
 Attempting NOOP on dropped connection atlas.coreitpro.com
andreas-bulling commented 7 years ago

I am using the current version (7.0.14) on OSX and have the same problem. Playing around with different values for socktimeout, holdconnectionopen and keepalive didn't help (not even sure if these parameters are related at all to this issue).

andreas-bulling commented 7 years ago

Switching to mbsync (http://isync.sourceforge.net/mbsync.html) solved all problems.

chris001 commented 7 years ago

Switch keepalive to a smaller value such as 60 or 30 fixes the issue of not sending keepalives. For the case of the internet connection dropped or imap connection dropped - this needs to be detected and handled - restart the sync procedure, reconnect to imap.