Bug 212482 - Make system tray icon ignore messages in spam folders
Summary: Make system tray icon ignore messages in spam folders
Status: RESOLVED DUPLICATE of bug 92646
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-31 08:20 UTC by Mike Vaughn
Modified: 2009-10-31 17:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Vaughn 2009-10-31 08:20:38 UTC
Version:            (using KDE 4.3.2)
Installed from:    Ubuntu Packages

It would make the system tray icon a lot more useful if it could be configured to only show a message count for folders in a user-selected set of folders. For example, I have three GMail accounts set up on KMail, two of which get a new spam message on almost every check. I'd like to be able to tell KMail to only show the message count for my actual inbox folders on the system tray icon, while disregarding the messages in the spam and trash folders. This would probably best be implemented via a checkbox-based listview under Settings -> Configure KMail -> Appearance -> System Tray, where the user could select which folders' messages should be counted in the system tray icon.
Comment 1 Jonathan Marten 2009-10-31 12:39:58 UTC
There is a per-folder option for this:

Folder - Properties - General tab - Act on new/unread mail in this folder

Turning off this option for the spam/trash folder should ignore new mail in them and not include it in the system tray count.  If this does not appear to work then please add any additional information to this bug report.
Comment 2 Mike Vaughn 2009-10-31 13:18:32 UTC
Works perfect, thanks for the quick reply. Sorry for not poking around a bit more before filing a report.
Comment 3 Christophe Marin 2009-10-31 17:00:34 UTC

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