Bug 292565 - KMail/akonadi doesn't sync current (IMAP) folder
Summary: KMail/akonadi doesn't sync current (IMAP) folder
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.8
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-27 09:58 UTC by Heinz Ulrich Stille
Modified: 2017-01-07 22:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Heinz Ulrich Stille 2012-01-27 09:58:04 UTC
Version:           4.8
OS:                Linux

KMail seems to be syncing folder by folder, but doesn't bother to update the folder currently open; "update folder"/F5 has no effect. I tried 4.8.0 today - after three hours it's still busy with other folders.

Might be connected with the fact that the account in question has about 130 subfolders with 45000 messages and 25 GB...
Switching from IMAP to dIMAP didn't seem to make any difference (apart from initial download), so the problem probably is administrative overhead, not data volume.

Reproducible: Always

Steps to Reproduce:
Just fire up KMail ...

Actual Results:  
KMail and Akonadi report syncing one folder after another. A complete sync seems to take days.

Expected Results:  
The folder currently open should be updated at once.

Client: KMail 4.8.0 / Fedora Rawhide 17, Server: Fedora 14 / cyrus imapd 2.3.18
Protocol: IMAP or dIMAP
Connection: doesn't seem to matter whether I'm on the server's LAN or external 2MBit connection.
Comment 1 Laurent Montel 2012-01-27 13:09:26 UTC
25Go ?!
Comment 2 Heinz Ulrich Stille 2012-01-27 13:23:00 UTC
That's what du --apparent-size tells me. No surprise since lots of messages have large (tens of megabytes) attachments - mostly photos.
Comment 3 Denis Kurz 2016-09-24 18:11:02 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 4 Denis Kurz 2017-01-07 22:43:02 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.