Bug 355184 - IMAP agent syncs too often
Summary: IMAP agent syncs too often
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-11 12:14 UTC by SZÉKELYI Szabolcs
Modified: 2018-02-01 09:54 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SZÉKELYI Szabolcs 2015-11-11 12:14:51 UTC
According to akonadiconsole and kmail's status bar, my IMAP account is synced much more often than configured. The automatic check interval is set to 5 minutes, but the sync is triggered every 30 seconds or so. As it takes quite a long time, and my mailbox is practically unusable util it completes ("please wait"), this makes my mail hard to read conveniently. The sync is triggered even when automatic checking is turned off in the agent's settings.

Reproducible: Always

Steps to Reproduce:
1. Create an IMAP account that holds a few thousand messages.
2. Browse through your mail.

Actual Results:  
Sync is triggered randomly, about every 30 seconds on average.

Expected Results:  
The whole folder shoudln't be synced all the time, just the selected messages downloaded.

akonadi_control reports version 5.0.51, but it's not available above.
Comment 1 SZÉKELYI Szabolcs 2015-11-25 18:09:02 UTC
The full resync seems to be triggered when I move a message to trash.
Comment 2 Denis Kurz 2017-06-23 20:16:47 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 3 Denis Kurz 2018-02-01 09:54:12 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.