Bug 139051

Summary: updating message status on imap server is very slow
Product: [Applications] kmail Reporter: Dragan Espenschied <drx>
Component: IMAPAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: bjoern, jtate+kde
Priority: NOR    
Version: 1.9.5   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Dragan Espenschied 2006-12-20 16:38:07 UTC 
Version:           1.9.5 (using KDE 3.5.5, Kubuntu (edgy) 4:3.5.5-0ubuntu3)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.17-10-generic

Hi,

i am using "offline IMAP". Before reading the new message list when an account is checked, Kmail updates the message status on the server. This can take a looong time, i have more than 5000 messages in my inbox. It also updates the message status when i did not change any message state, so nothing read, nothing answered etc ...

So i assume Kmail is uploading the status of all messages to the server, whether they have been changed or not.

I suggest to only update the status of messages that have been modified since the last synch.

Best greetings,
drx
Comment 1 Joseph Tate 2008-12-16 20:32:30 UTC 
I note that with an inbox of about 1500 messages, it's nearly instantaneous upon application startup to sync mail.  However after running for a few hours, it gets much slower.  After a day or so, it takes nearly 2 minutes per folder.  Folders that have received more churn over the course of the application life seem to go slower.

I wonder if sync'ing is causing a replay of everything that happened locally, and the list of actions just needs to be reset once synchronization is complete rather than grow without bound.  It also appears that the memory usage goes up over time.

This is still happening in my build of Kmail 4.1.2.  I see it in KDE 3.5.10 too.
Comment 2 Björn Ruberg 2010-01-01 23:13:50 UTC 
In KDE 4.3 I have accounts with thousands of mails but the up- and download always is very fast. Can you confirm that?
Comment 3 Joseph Tate 2010-01-02 05:38:40 UTC 
Agreed.  Seems to be fixed.