Closed Bug 266115 Opened 20 years ago Closed 20 years ago

Message filters don't override junk filters.

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: spiderninja, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: 

A message which should be successfully filtered can still be labelled junk and
moved.

Reproducible: Always
Steps to Reproduce:
1. Set up a filter based on a from address
2. Send a message that will be recognised as junk from this address


Actual Results:  
Message got filtered to the correct folder and then thrown in the junk folder

Expected Results:  
left it in the folder the filter specified
If you don't want the message to be checked for junk status, add the filter
action to mark the message as non-junk. Then it won't be analyzed. You can have
multiple filter actions, so you are in control of this. Address book
whitelisting can also reduce the number of messages that are analyzed for junk
status.
But really, the filters are tight enough that filtered mail should be assumed to
be not junk. Unless there's a really sound reason for junk-mail-filtering
folders other than INBOX.

Maybe it's not a bug, but it is a usability problem.
If your filters preclude the message being junk, add the filter action to mark
the message as non-junk. It's just a matter of checking a check box when
defining a filter - not sure how much easier we could make it, other than
assuming that all filters are like yours, which I don't think is a reasonable
default. Many of my filters match the criteria but also match junk mail (e.g.,
some mailing lists get junk mail)...we would also like to add the ability to
preclude user-specified folders from having new messages analyzed as junk. I
think that would also accomplish what you want. There is an RFE bug open on
that, so I'm marking this as WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.