233930 - Still get notification for junk that's been filtered to a different folder

Status: RESOLVED DUPLICATE of bug 460279

Description

[Mike Cowperthwaite]

With the fix for bug 189289, junk that is auto-identified and moved to a junk 
folder does not trigger a biff notification.

However, if a message arrives and is filtered to a folder somewhere, it is not 
immediately processed as junk (bug 200788).  Therefore, the notification is not 
suppressed.

See this in Moz 1.6 Final and 1.7a.

Comment 1

[David :Bienvenu]

filters run before junk mail analysis - w/o rewriting the filter code, that's
the way that's going to be...

Comment 2

[Mike Cowperthwaite]

*** Bug 233933 has been marked as a duplicate of this bug. ***

Comment 3

[Mike Cowperthwaite]

xref bug 233929.

Also compare to bug 189970, which requests that folders be able to be configured 
to be ignored for junk controls -- which slightly counteracts this bug.


(In reply to comment #1)
> filters run before junk mail analysis - w/o rewriting the filter code, that's
> the way that's going to be...

I knew that, that's why this one is dependent on 200788.

Comment 4

[Andrea Schafferhans]

(In reply to comment #3)
> Also compare to bug 189970, which requests that folders be able to be configured 
> to be ignored for junk controls -- which slightly counteracts this bug.

So I suppose in summary the requirement is:
Allow the user to specify per folder whether he wants a) junk mail filtering and
b) new mail notifications.
When new mail arrives
1) filter it to specified folders
2) for each folder with new messages: 
   a) check for junk mail status (if desired, 
        and do whatever has been specified to do with junk)
   b) trigger new mail notification for non-junk (if desired)

Would it be possible to do something like this? 

After reading 200788 I realise that apparently junk mail filtering is something
that only happens on specific triggers, but I aggree with <a
href="show_bug.cgi?id=200788#c6">comment 6</a> of that bug, that I would expect
junk mail filtering to be (like any other filter) something that happens on all
incoming messages. 

Comment 5

[Tom Graham]

*** Bug 242972 has been marked as a duplicate of this bug. ***

Comment 6

[Tom Graham]

Confirming that this is still happening, with the 0.7 release of Thunderbird.
Essentially, mail coming in thats junk, gets marked as junk (and goes to trash),
yet a notification is still displayed in the tasktray. This is removed when you
place your mouse over it.

Comment 7

[Mike Cowperthwaite]

*** Bug 277287 has been marked as a duplicate of this bug. ***

Comment 8

[Galen Swint]

This is a major irritation for me. It makes notifications completely useless to notify every time a piece of junk is received - which can be as often as every five minutes.

Comment 9

[Mike Cowperthwaite]

Bug 329569 recently changed the behavior of junk processing for filtered messages: messages filtered to folders now get processed for junk immediately.
However, even if all the new messages are junk, you'll get a notification, so this bug's problem persists, in a slightly different form.

Comment 10

[Cees T.]

*** Bug 357903 has been marked as a duplicate of this bug. ***

Comment 11

[Cees T.]

*** Bug 357512 has been marked as a duplicate of this bug. ***

Comment 12

[Wayne Mery (:wsmwk)]

Mike, others, do you still see this?  On trunk?  On 2.x?

Comment 13

[Mike Cowperthwaite]

Yes, I just saw this with a recent trunk.

Comment 14

[Jef Driesen]

I have this problem with Thunderbird 2.0b2 (20070116) also. Mail gets automatically classified as junk and moved to the Junk folder, but the new mail notification alert is still shown. With version 1.5 I didn't get the notification.

Comment 15

[Jeff Blaine]

I'd like to chime in as well.  This drives me nutty.

Like so many others, I filter mail.  There are many things I filter that I do not want New Mail notification of (most specifically my spam I redirect to a Spam folder... same concept as Junk).  But it's more than that -- I do not need to hear a new mail notification for random mailing lists I subscribe to, etc.  Each person has his/her preference for what is worth being alerted to, but it's not a selectively configurable preference right now.

Comment 16

[(not reading, please use [e-mail] instead)]

sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.

Comment 17

[Colin Jones]

Me too - this is a very annoying feature just now - particularly with the much larger popup alert in TB2.  I don't need to see popup alerts, which by their nature are intrusive and designed to attract attention, when Thunderbird is already capable of determining that the email is almost certainly spam.  I only want to see them when it's something I'm likely to want to read.

I can look at Spam in the Junk folder at leisure whenever I like, but to get a popup every 10 minutes saying another has arrived is not useful - it just means I start to ignore them altogether, as more often than not it's informing me of more spam, rather than a real email.

The ability to customise this behaviour, either per folder, or in particular for mail already categorised as junk would be a big improvement.

Comment 18

[Ben Bucksch (:BenB)]

Bug 272125 asks to (optionally) not show the alert for any messages marked as Junk, no matter which folder they are in. I think that's very reasonable.

This bug has some overlap, but a part which would not be covered by bug 272125: Jeff asks in comment 15 to also ignore legit mail in a certain folder, from e.g. a mailing list filtered into a folder. I think that's also a reasonable request, which has nothing to do with Junk mail. Given that this bug here is focused on Junk mail (which would be convered by 272125), I filed a new bug 460279, to avoid confusion.

Comment 19

[Mike Cowperthwaite]

(In reply to comment #18)
> Given that this bug here is
> focused on Junk mail (which would be convered by 272125), I filed a new bug
> 460279, to avoid confusion.
> 
> *** This bug has been marked as a duplicate of bug 460279 ***

Which was subsequently duped to bug 11040.  I certainly agree that fixing 11040 would make this bug obsolete; it would not *fix* this bug, which is about a specific symptom.

Comment 20

[Ben Bucksch (:BenB)]

Bug 272125 and bug 233929 together would fix the symptoms described here, as I described in my last comment.

Comment 21

[Ben Bucksch (:BenB)]

I meant: Bug 272125 and bug 11040 together