Closed Bug 182109 Opened 22 years ago Closed 21 years ago

Mail filters ignore 'Junk Status' parameters.

Categories

(MailNews Core :: Filters, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: myrddine, Assigned: sspitzer)

References

(Blocks 1 open bug)

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Crazy Browser 1.0.5; .NET CLR 1.0.3705)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021126

Mail filters that trigger based on the Junk Status of an email do not fire.


Result: Mail filter does not fire, junk email is not moved.

Reproducible: Always

Steps to Reproduce:
- Create a mail filter with one filter rule: Junk Status - is - Junk

- Action: Move Email to Deleted

- Pick one email in your Inbox and manually change its junk status to Junk.

- Return to filters and force it to 'run now' on the selected folder.
Actual Results:  
Junk mail is not moved to the Deleted folder.

Expected Results:  
Junk mail should have been moved to the Deleted folder by the manually executed 
filter.
Just in case I was not clear, 'new' incoming mail does not get filtered either. 
Other mail filters are properly firing.
using build 2002120408 on windows 2000 professional

manually running such a filter on a selected folder behaves as expected [moves
the messages with status junk to my 'incoming_junk' folder]

still, the filter works only when run manually. incoming mail with status 'junk'
is not moved to the 'incoming_junk' folder
Blocks: 11035
Status: UNCONFIRMED → NEW
Ever confirmed: true
I downloaded the current nightly and ran some more extensive tests, after
reading George Lefter's comment. With the current nightly build (2002121008) I
created and ran many mail filters on a single email in my inbox that I had
marked as Junk by clicking the Junk column. These are the results:

Fail: Junk Status is Junk -> Move to Trash on Local Folders
Fail: Subject begins with 'Correction' -> Move to Trash on Local Folders
Pass: Subject begins with 'Correction' -> Set Priority to Lowest
Pass: Junk Status is Junk -> Set Priority to Low
Fail: Subject begins with 'Correction' -> Move to Trash on Local Folders
Fail: Junk Status is Junk -> Move to Trash on Local Folders
Fail: Junk Status is Junk -> Move to Trash on myrddin@iosys.net
Fail: Subject begins with 'Correction' -> Set Priority to High

So the working seems erratic. I do not understand why it is working sometimes
and not others. Perhaps certain actions on my part that I may not recognize the
significance of are affecting the results. Other filters, based primarily on the
address the email is from or to and using move actions, have been working
flawlessly.
The previous comment was the result a bug that I could not find reported
elsewhere, which I now reported in bug 185104 (The 'Run Now' button in the
Filter window behaves erratically for me. The 'Run Filters on Selected Folder'
action works fine.)

As George Lefter reported, mail is filtered just fine based on the status of the
Junk Status parameter when manually running the filters after the fact. Mail is
still not filtered as it enteres, probably due to the delayed application of the
Junk Status property. Mail is marked as junk or not after filters are run on the
incoming mail. It may be necessary to delay applying filters that use the Junk
Status property until after the Bayesian filter has been applied.
for the short term, I think we have to hide junk status (and has attachment)
from the filter UI, but leave it in search.
Assignee: naving → sspitzer
also happens with linux build (build id: 2003020508).
changing hardware -> all, os -> all.
OS: Windows XP → All
Hardware: PC → All
Is it the case that the junk mail filter is running *aftder* the incoming mail
filter?  Is this an order of execution problem?
I've hidden "junk status" (and has attachment) from filters, because it doesn't
work, so this is now invalid.

see bug #185937 and http://bugzilla.mozilla.org/show_bug.cgi?id=183104#c3
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
I'm sorry, I think this is still a mistake.  This is one of the key pieces of
information that people will want to filter on.  Creating a whole new filtering
infrastructure to filter junk seems redundant.  Why not process the mail through
the junk filter prior to the mail filters as I suggested previously?

Anyway, thanks very much for your time and effort on this project.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.