Closed Bug 793248 Opened 13 years ago Closed 13 years ago

New mail alerts delivery should be customizable (at least) by folder

Categories

(Thunderbird :: Message Reader UI, defect)

15 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 224573

People

(Reporter: tlhackque, Unassigned)

Details

I was working with TB open, when I got a spate of popup-beep alerts for New Mail. Problem is, the new mail in question was delivered (directly by Procmail as directed by SpamAssassin) to the "dead sure it's junk mail" folder. Oops! I should be able to specify which folders cause alerts, and which ones don't. In this case, Spamassassin/Procmail on my e-mail host delivered to my "almost certainly spam" folder. Yet Thunderbird, not knowing better, beeped and waved. What I would like is a preference setting - either folders to alert on, or folders NOT to alert on - to control when TB alerts. It could be under folder properties, like "Include messages from this folder in Global Search results". Or under Options->General->When a new message arrives -> Customize. Under Outlook, no alerts are generated for IMAP incoming messages, unless a custom rule is written to generate them. That's more a technical limitation than a feature, but I do miss the control. With the rule-based approach, I could inhibit alerts for mailing list traffic that I read once a day, but ensure that I was alerted when new mail arrived from a family member. Something like that would be idea - but if it were simply binary on which folder(s) alert, the server's local delivery agent could help. A trivial simple option: Don't alert unless the message delivered to INBOX. That's the bare minimum to make me happy - at least on this issue. Thanks for your consideration!!
You should be able to disable the checking for new messages for each IMAP folder. That should help with the SPAM folder alerts.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.