Bug 171563

Summary:	Imap mails disapearing and apearing again upon Check Mail
Product:	[Unmaintained] kmail	Reporter:	Pascal d'Hermilly <pascal>
Component:	IMAP	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	aldo-public, bjoern, kde, ruchir.brahmbhatt
Priority:	NOR	Keywords:	triaged
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Pascal d'Hermilly 2008-09-24 01:07:25 UTC

Version:            (using KDE 4.1.1)
OS:                Linux
Installed from:    Ubuntu Packages

In my Imap inbox folder where there are some new emails, when I click Check Mail, the mails disapear one after another. At the same time kmail is showing status for "Downloading message data" for each mail that is disapearing. When all the new mails are gone, it shows a lot of "Uploading message data" status messages and then all the mails appear again.

But why?

Comment 1 Aldoo 2008-09-24 16:26:32 UTC

Are you using an antispam filter ?
I have this problem too with antispam filters on IMAP.
My belief is that the filter downloads the message, adds the antispam header, deletes the original mail on the server, and then uploads the updated one.
I find it quite confusing too.

Comment 2 Gary Pendergast 2008-11-04 02:17:50 UTC

Yes, I'm seeing this problem as well, I fixed it by turning off the spam filter.

It would be a lot better if the spam filter rules were only applied to new messages that hadn't already been filtered.

Comment 3 Ruchir Brahmbhatt 2009-04-12 13:08:06 UTC

I can reproduce this on 1.11.2.

Comment 4 Pascal d'Hermilly 2009-06-15 23:33:36 UTC

Still does this in 1.11.90
Any way to debug this or should I just wait for the akonadi implementation of the imap protocol?

Comment 5 Pascal d'Hermilly 2009-06-15 23:39:56 UTC

After having used kmail, thunderbird had to reload the whole inbox and all the tags I'd made was removed.

Comment 6 Björn Ruberg 2009-12-12 01:15:34 UTC

This a duplicate of #125084 in my opinion. This bug has been fixed later in the 4.2 line.

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