Summary: | On startup, all folders synced, even if they are set to never sync | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Szokovacs Robert <szo> |
Component: | IMAP resource | Assignee: | Christian Mollekopf <chrigi_1> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | dev+kde, kdepim-bugs, mollekopf, montel, vkrause |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Szokovacs Robert
2012-06-04 19:13:36 UTC
How do you set "never sync" ? folder properties/retrieval/automatically synchronize after: never. Actually, the folders with lots of messages have "use options from parent..." checked, and the parent (empty, only subfolders) has the setting described above. I seem to have the same problem. After the upgrade on my Gentoo 64 bit from KDE 4.10 to 4.11 I had to set up all my Akonadi stuff from scratch because it was borked (i.e. the setup is now as clean and uncustomised as can be). Originally I set one of the IMAPs to sync every 60 minutes, but then decided to switch automatic sync off altogether for that account because it has lots of (distracting) mailing list traffic. Yet, even without opening KMail, the resource requests to open the KDE wallet, and I get notifications about new mail. I just sent a test mail to the account and was notified within 10 seconds. Could that be IMAP idle what I’m describing? From my POV, if sync is switched off, then the resource should be completely passive. The IMAP resource has a new maintainer, reassigning to him. I'm not entirely sure, but it might be kmail that is triggering those syncs. This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months. 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. |