Bug 181333

Summary:	Unread messages in folders with subfolders not counted in the "unread"-column
Product:	[Unmaintained] kmail	Reporter:	kgw
Component:	new folder tree	Assignee:	Szymon Stefanek <pragma>
Status:	RESOLVED FIXED
Severity:	normal	CC:	andygoossens, jtamate, lrm.regs-15.07, mail, miga_miga
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description kgw 2009-01-19 19:33:45 UTC

Version:           4.2 SVN as of 2009-01-18 (using Devel)
Installed from:    Compiled sources

I have quite a lot of pop3 message folders into which messages get sorted by an array of filters I built up over the years. If this sorting procedure puts a message in a folder that itself has a sub folder then the folder is marked as having unread messages (bold font) but the column "unread", where for any leaf folder the count of unread messages is kept current, stays empty. I would expect either the total count of unread messages (including sub folders) or the number of messages in the folder directly to be displayed there.

Comment 1 Leonardo M 2009-02-02 15:32:36 UTC

Kmail 1.11.0 (KDE 4.2.00)

Folder          Unread
----------------------
Inbox              8
  subfolder1       10
  subfolder2       20
Outbox
Sent
Trash
etc

If subfolder1 and subfolder2 have unread emails, they are shown under the Unread column. This is OK.
If Inbox has unread emails (such as 8), the number "8" does not appear under the Unread column. This is NOT OK. However, the word Inbox does change to Bold.

Comment 2 Andy Goossens 2009-02-09 23:48:48 UTC

Same issue here.

Comment 3 Jaime Torres 2009-02-13 19:30:04 UTC

Confirmed in 1.11.90 (kde 4.2.62).

Comment 4 Michael 2009-03-02 19:03:41 UTC

Same problem here with KMail 1.11.0 (KDE 4.2 on Gentoo)

Comment 5 Michael 2009-03-07 11:03:45 UTC

Problem still exists in KMail 1.11.1 (KDE 4.2.1)

Comment 6 kgw 2009-07-01 20:48:27 UTC

Just checked in SVN as of 2009-07-01, the behavior now is absolutely correct.

Comment 7 Björn Ruberg 2010-02-06 01:01:43 UTC

*** Bug 183193 has been marked as a duplicate of this bug. ***