Bug 277676 - IDLE IMAP silently stops working after a while
Summary: IDLE IMAP silently stops working after a while
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 2.1.1
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-13 07:04 UTC by Médéric Boquien
Modified: 2017-01-07 22:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Médéric Boquien 2011-07-13 07:04:31 UTC 
Version:           2.1.1
OS:                Linux

I use IDLE IMAP to check my mails on several IMAP accounts. I have noticed that after a few hours i stop getting emails on some accounts (not always the same). Restarting kmail fixes the problem.

Reproducible: Didn't try

Steps to Reproduce:
Star kmail, wait a few hours.

Actual Results:  
Sometimes i stop receiving IMAP emails after a few hours.

Expected Results:  
I keep receiving emails no matter how long kmail has been running.
Comment 1 simon 2011-11-04 10:39:51 UTC 
i can confirm this with latest git ( server side suscriptions enabled  and check every X minutes disabled)
Comment 2 hello 2013-03-30 22:26:13 UTC 
also with kde 4.10.1 the imap idle functionality vanished after a few days.
Comment 3 hello 2013-03-30 22:34:15 UTC 
enable and disable "periodically check" made it work again.
Comment 4 hello 2013-04-01 19:31:46 UTC 
but after resuming from suspend i need to check mails manually once, to get those i received in between and to get imap idle working again.
Comment 5 Denis Kurz 2016-09-24 18:17:37 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 6 Denis Kurz 2017-01-07 22:33:42 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.