Patrick Ulbrich

Ok, I see. You specified folder names so IMAP Idle is not enabled (not supported). The reconnection issue you got shouldn't happen anyway. Please let me know if it happens...

Ok, I guess the best solution would be to ask networkmanager via dbus for the connection state and fallback to the current solutoin (urllib2) where networkmanager is not available.

Mailnag (master branch) now uses NetworkManager to test connectivity when available and falls back to a ping-test if not. This behaviour can be overriden in the config file. The connectivity_test...

You can start either mailnagd or mailnag-config directly from the checkout folder (If you run mailnag-config, mailnagd is also autostarted at the next boot from there). If you run mailnagd...

Yes, Mailnag could be a little bit more verbose. Though if you run ./mailnagd in the checkout folder, you can be assured it will not use bits of another (e.g....

While it's technically possible to immediately check for mails on a reconnect, I'm reluctant to implement it for the following reasons: - It will work with the NetworkManager connectivity test...

Case a) is covered by the current implementation already btw.

Ok, your goal is obviously to get instant notifications. The problem is you can't have them with polling connections and adding workarounds like polling on connection change don't feel like...

I'm sorry, I won't change the current behaviour due to the reasons stated above. If the solutions I proposed are not acceptable for you, you could also decrease the polling...

@tristan-k: What Mailnag version are you using? Do you have IMAP IDLE enabled? Did you specify folder names in mailnag-config? According to the log you posted, Mailnag was shut down...