274023 - Not more than four filter expressions?

Status: RESOLVED EXPIRED

(MailNews Core :: Filters, defect)

Description

[Hadmut Danisch]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041007 Debian/1.7.3-5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041007 Debian/1.7.3-5

Hi,

I have some incoming filters defined for my IMAP mailbox.
One of them is to move all mailing list messages from a 
vendor from inbox to a particular imap folder. Worked 
pretty well as long as I had up to four expressions
(subject starts with...) Now I'v added a fifth
and suddenly mozilla moves _every_ mail into that
folder and filter log shows that the filter was applied 
to every mail in inbox.

The condition from msgFilterRules.dat:

condition="OR (subject,begins with,Microsoft Windows Platform News) OR (subject,
begins with,Microsoft Windows-Newsletter) OR (subject,begins with,Insider Update
 for) OR (subject,begins with,Microsoft Office-Newsletter) OR (subject,begins wi
th,TechNet NewsFlash)"

Maybe the condition is too long for any buffer?


regards
Hadmut


Reproducible: Always
Steps to Reproduce:
1. Produce a mailbox folder with some mails
2. Generate a filter which moves mails into a different folder, 
   add five "Subject starts with" entries of the kind as given in the 
   Details section.
3. Apply filter to mailbox - All messages are moved regardless of their
   subject.

Actual Results:  
All messages were moved.

Expected Results:  
Only those messages that match the expression should have been moved.

Comment 1

[Josh Triplett]

WFM using Mozilla BuildID 2005011102 (nightly), on Debian GNU/Linux unstable.

Created a filter with five "Subject starts with" conditions.  Filter condition
in msgFilterRules.dat was longer than the one posted by the bug reporter. 
Filter worked as expected.

Reporter: Could you try this in a recent nightly build? You can download one at
http://www.mozilla.org/developer/#builds .

Comment 2

[Hadmut Danisch]

Hi,

I'm currently not in my office and can't check this before monday.

regards
Hadmut

Comment 3

[Hadmut Danisch]

Hi,

I apologize for the delay, I was unexpectedly busy the last days.

The bug still exists in 1.7.5 (debian). 

I just downloaded that nightly build (Thursday, Jan 20th), 
and that seems to work properly. I made a test and it sorted mails
with the given filter as expected.

regards
Hadmut

Comment 4

[Hadmut Danisch]

...and it also seems to work as expected with 
  thunderbird 1.0

regards
Hadmut

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 7

[Josh Triplett]

Per the reporter, this should really get marked "RESOLVED FIXED", not "RESOLVED EXPIRED".

Comment 8

[Josh Triplett]

(In reply to comment #7)
> Per the reporter, this should really get marked "RESOLVED FIXED", not "RESOLVED
> EXPIRED".

Correction: "RESOLVED WORKSFORME".