Bug 148010

Summary: kmail screws up imap folder and uploads a bunch of message data
Product: [Applications] kmail Reporter: Aaron Williams <aaronw>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Severity: normal    
Priority: NOR    
Version: 1.9.7   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Aaron Williams 2007-07-19 09:02:22 UTC
Version:           1.9.7 (using KDE 3.5.7 "release 56.1" , openSUSE )
Compiler:          Target: x86_64-suse-linux
OS:                Linux (x86_64) release

It seems every time I start up KMail and click on one of my Imap accounts it uploads a ton of messages and tends to screw up all the email dates when sorting. It also causes duplicate messages to appear on the Imap server.

I have seen this with several KDE installations with earlier versions as well and with different IMAP servers.

I am seeing this with both Cyrus and Exchange.  If this Imap problem could be fixed, I'd dump Thunderbird in an instant.
Comment 1 Aaron Williams 2007-07-19 09:16:43 UTC
On further inspection, it looks like it is downloading emails and uploading them back after deleting the original.  This seems to cause problems with sorting, especially with pine, though I have seen it also affect Thunderbird. Kmail also is screwed up from then on with the sorting order, with older emails appearing as the latest when they are often several weeks old.

Also note that I alternate between imap mail clients and sometimes have more than one active at a time.
Comment 2 Thomas McGuire 2007-07-19 17:42:34 UTC
Are you using filters?
If so, this is probably the same as bug 125084.
Comment 3 Aaron Williams 2007-07-19 18:26:23 UTC
I am running Sieve on the Cyrus mail server but I also have what looks like are the default filters, Bogofilter Check, Spam handling, Classify as spam and Classify as NOT spam.  I guess I can disable the filters since the mail is filtered by the server which catches most of it.
Comment 4 Thomas McGuire 2007-07-19 21:41:45 UTC
Ah yes, that is either bug 125084 or bug 134802.

*** This bug has been marked as a duplicate of 125084 ***