382520 - filter will apply if status = starred/replied condition is met even if other conditions are not met

Status: NEW

(MailNews Core :: Filters, defect)

Description

[John Hagtharp]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20070417 Fedora/2.0.0.3-4.fc7 Firefox/2.0.0.3
Build Identifier: version 2.0.0.0 (20070419)

The first filter on my list checks for "Status is Starred" AND "from contains ....." and moves the email to another folder.

This filter will always apply if the message is starred regardless of who sent the email. Simply changing the status check to "status is read" will bring about the correct behavior where the filter only applies if the from address matches.

These filters are not active and are being run via "run now" from the message filters dialog.

I'm using an IMAP server.

Reproducible: Always

Steps to Reproduce:
1. Create the filter as per above (not active) 
2. "Star" a message in the inbox.
3. Go to the message filters dialog, highlight the filter (actually all filters in my case) and click the "Run Now" button. 
Actual Results:  
Regardless of the from address on the messages, the filter applies to all starred messages.

Expected Results:  
The filter should only apply when the status is starred AND the from address matches.

Comment 1

[Magnus Melin [:mkmelin]]

Confirmed on Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.4pre) Gecko/20070530 Thunderbird/2.0.0.4pre ID:2007053003

Comment 2

[Francis Davey]

I observe this same bug in the following way:

I have a filter which has "Match all of the following" set. There are two conditions:

1. Status is replied
2. From contains LawWorks

This filter matches all messages with replied to set, regardless of what From contains. If I reverse the order of the conditions (so that "Status is..." follows", I do not observe this behaviour and the filter only matches what it should.

This has been happening for a while unobserved by me (I just kept losing emails) but I have tested it by creating a new filter with the same behaviour. It therefore happens both on "Run now" and on download from a POP server.

I am afraid I do not have the resources to try a new build just now so this is confirmed for:

version 2.0.0.9 (20071031)

I accept that my bug is not completely identical (it is a variant) but it appears to be a problem with "Status is...." test.

Comment 3

[Francis Davey]

Sorry, I should have added that I am running this under Windows XP.

Comment 4

[Magnus Melin [:mkmelin]]

Moving to filers, problem still there on trunk btw.