Open Bug 239108 Opened 20 years ago Updated 15 years ago

mail notification should indicate how many filtered messages reached which folder

Categories

(SeaMonkey :: MailNews: Message Display, enhancement)

x86
Windows 2000
enhancement
Not set
normal

Tracking

(Not tracked)

People

(Reporter: david, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040316
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040316

Not all messages are equally important. Mail notification only states how many
non-junk messages have been received per account. It does not take message
filter results into account. This means that the user may break from productive
work in another program, switch to Mozilla Mail, only to find that the mail was,
say, filtered into a 'Newsletters' folder. If notification waited until the
message filters had run for that account, then totalled how many messages ended
up in which folder, it could show the user that information. The user then knows
if it's worth checking their inbound mail, or leaving it be.

Reproducible: Always
Steps to Reproduce:
Basically Bug 91498
Sorry, but I don't see it relates to that bug -- this is a request for
additional functionality to let notifications give a potted summary of *each*
folder that has received e-mails after the message filters have done their work.
Product: Browser → Seamonkey
Assignee: sspitzer → mail
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
Please keep this bug/RFE open.  Better yet, someone please submit a patch!
To further clarify my interest in this bug/RFE, I do not use the message filters
in TB, but I do extensive pre-delivery filtering with procmail on the server
before it reaches my mailbox.  Of course, I am using IMAP, since POP does not
support multiple mailbox files/folders on the server.

So, when I get new mail, it could be in one of many folders, and the current
"new mail" notification is almost useless because then I have to go searching
for which mail folder has a new mail icon.  This bug/RFE would very much help
address this problem by quickly identifying which folders have new mail.

Ultimately, the best solution I have seen for this is the "cabinets" feature in
Mulberry, which had a grouping to display only those folders that contain new
mail.  I have implemented something similar in TB using the "Saved Search"
feature, but it is not a very elegant solution for this purpose.  It actually
works to display the new mail in all the folders I select in one place, but it
takes them out of context.  In other words, I can no longer seem them along with
the threads they belong to in their actual mailbox file/folder.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Another approach would be to have a simple control above the accounts/folders pane, toggling a 'show only those folders with unread messages' view. However that's still moving the issue to the main client window rather than addressing the notification popup.
Component: MailNews: Notification → MailNews: Message Display
QA Contact: stephend → search
Assignee: mail → nobody
QA Contact: search → message-display
You need to log in before you can comment on or make changes to this bug.