Bug 212760 - "Act on new/unread mail in this folder" still included in global unread count
Summary: "Act on new/unread mail in this folder" still included in global unread count
Status: RESOLVED NOT A BUG
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.11.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-02 17:09 UTC by Nick Hoffman
Modified: 2009-11-03 16:37 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Hoffman 2009-11-02 17:09:14 UTC
Version:           1.11.2 (using 4.2.2 (KDE 4.2.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.27-14-generic

When the "Act on new/unread mail in this folder" mail folder option is unchecked, new and unread emails in the folder are still counted in the global unread email count.

I've tested this on different mail folders in one IMAP account.

I expected that unchecking this mail folder option would case emails in the desired mail folder not to be counted in the global unread email count.

For example, say there are 10 unread emails in the "INBOX" folder and 2 unread emails in the "foobar" folder. I right-click on the "foobar" folder, click "Properties", ensure that "Act on new/unread mail in this folder" is unchecked, and click "OK". The unread mail count on the KMail system tray icon lists "12", not "10".
Comment 1 Torgny Nyblom 2009-11-02 19:10:38 UTC
Could you try with a more resent KMail version (4.3.2 is latest and 4.3.3 is due soon).

(It works as expected using trunk)
Comment 2 Nick Hoffman 2009-11-03 05:41:30 UTC
(In reply to comment #1)
> Could you try with a more resent KMail version (4.3.2 is latest and 4.3.3 is
> due soon).
> 
> (It works as expected using trunk)

I just tried using v1.11.4 in KDE 4.2.4, and this bug doesn't exist.

I guess it's simply an old bug.

Thanks for the quick reply, Torgny.