Bug 339438

Summary:	Imap folder varies message count and refills periodically
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Michael Tils <nospam>
Component:	IMAP resource	Assignee:	Christian Mollekopf <chrigi_1>
Status:	RESOLVED WORKSFORME
Severity:	grave	CC:	kdepim-bugs, vkrause
Priority:	NOR	Keywords:	investigated, triaged
Version:	1.13.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Michael Tils 2014-09-26 18:54:13 UTC

I have a strange error after dragging (moving) files to dophin:

A few days ago I became a lot of replies because i sent a newsletter. Then I tooked about 80 of them and dragged them into a local folder via dolphin.
After that akonadi told the wrong message count (86) for this inbox. A few minutes later it counted 800 new mails in that folder. Then again 86 an so on. In periods of about 2 Minutes.
I tried to delete this IMAP account and readded it, nothing changed. Another day I deleted it, readded it with a different name, same problem.
After about 4 days I moved a few messages via an webmailer to different folders (about 400). Now the numbers of kmail are different. It jumps randomly between 40 and 400 mails. And my notification plasmoid permanantly shows the "new" amount of mail.

It is also very difficult to read mails because of the constant refill of this account.

Tried to see something via kdebugdialog but no luck.

I can imagine that this is a strange bug without something useful like a debug trace or so but if someone can tell me what you need I will attach it.

The problem happens only in one of my 8 imap accounts.

Thanks in advance

Reproducible: Always

Steps to Reproduce:
1. Drag/move a lot of messages from kmail to a local folder

Actual Results:
Kmail shows wrong message count and permanently refills the folder

Expected Results:
Not refilling the folder

I have KDE 4.14 on OpenSUSE 13.1 (x64) with akonadi 1.13.0-1.1 installed by rpm from KDE Current Repository

Comment 1 Denis Kurz 2017-06-23 20:02:33 UTC

This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.

Comment 2 Michael Tils 2017-06-23 20:17:40 UTC

From my point of view you can close it. With the newer versions of akonadi I didn't see the problem again

Comment 3 Andrew Crouthamel 2018-09-19 14:41:02 UTC

This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.