Bug 312484

Summary:	KMail message list is empty though the "unread counter" is correct
Product:	[Applications] kmail2	Reporter:	Unknown <null>
Component:	message list	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	aroth, mathias.tausig, mollekopf, null, roman.karlstetter
Priority:	NOR
Version:	4.9.4
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	Only 2 letters are visible but I have 30+ in the inbox

Description Unknown 2013-01-02 09:59:19 UTC

After I periodically start and stop Akonadi (because of an other bug) this morning I saw that KMail only shows 2 messages in the inbox, though I have at least 30 in them.

I'll attach a screenshot to demonstrate it better. Interestingly, the unread counter is right.

Reproducible: Didn't try

Comment 1 Unknown 2013-01-02 10:00:01 UTC

Created attachment 76136 [details]
Only 2 letters are visible but I have 30+ in the inbox

Comment 2 Unknown 2013-01-02 10:04:45 UTC

Ps.: it's interesting that in akonadiconsole's Browser tab I can see all of the letters and their payload correctly.

Comment 3 Roman K. 2013-04-06 14:48:32 UTC

I have a similar issue. For some messages, new unread messages do not appear in the list of messages. This happens for all my IMAP accounts (haven't tested anything else) and it happens for mails in the inbox and those in subfolders. 
Mails that arrive after these "invisible mails" get displayed normally. 
After restarting kmail all mails (including the ones that were invisible) can be seen again.

Comment 4 Unknown 2013-04-11 07:36:31 UTC

We had a very similar situation with the mailfiltering.
See the thread (in the kde-pim mailing list)
  "mailfilter does not see all incoming messages"
from wolfgang@rohdewald.de at Wed, 13 Feb 2013 10:34:46

It was a dispatch problem at the very input of the messages, solved by Andras Mantia at 
the KDEPIM-sprint in Berlin.

Comment 5 Roman K. 2013-04-11 16:27:50 UTC

Ok, this means the fix should be in KDE 4.10.3 or KDE 4.11. Am I right?

Comment 6 Christian Mollekopf 2013-05-07 16:09:09 UTC


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