Open Bug 1215817 Opened 9 years ago Updated 2 years ago

New mail sound played and notification shown again when POP Inbox is visited that previously received new mail. Caused by "after junk" filters.

Categories

(Thunderbird :: Mail Window Front End, defect)

defect

Tracking

(Not tracked)

People

(Reporter: jorgk-bmo, Unassigned)

References

Details

I use four POP accounts.

In the morning, I receive new mail and that gets stored into the four inboxes. A sound is played and a notification is shown in the systray area of Windows.

When I *later* visit an inbox that has previously received new e-mail, I get the sound played again and another systray notification shown.

The expected behaviour is that sound and notification are only played once when the e-mail is received/downloaded, but not again when another inbox is visited that previously received new mail.

TB has become noisier and more confusing, since it keeps notifying of new e-mail where there is no new e-mail.

I have the impression that this behaviour has changed from previous versions. Or maybe I'm going crazy? I just sent two messages to two accounts which got delivered to two inboxes in TB 38, and there the problem already happens. I've never noticed it before.
OK. I found the cause, I'm not going crazy.

This is caused by "after junk" filters. I've recently changed all my "before junk" filters (type="17") to "after junk" filters (type="48") due to bug 1211261. That's when the trouble started.
Summary: New mail notification has become overzealous → New mail sound played and notification show again when POP Inbox is visited that previously received new mail. Caused by "after junk" filters.
Summary: New mail sound played and notification show again when POP Inbox is visited that previously received new mail. Caused by "after junk" filters. → New mail sound played and notification shown again when POP Inbox is visited that previously received new mail. Caused by "after junk" filters.
See Also: → 1211261
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.