16749 - [FEATURE] Allow multiple filters to fire on a message

Status: CLOSED WORKSFORME

(MailNews Core :: Networking, defect, P3)

Description

[alex.seggie]

With a filter you can set the priority of a message OR you can move the
message to a new folder. Netscape does not allow you to do both.

You check the parameters on each filter until you find one that applies
and then you stop looking.  This is wrong. You should stop looking only
if the filter moves or deletes the message. If the filter sets the priority
(or any action like that) then you should do the requested action and then
CONTINUE looking for other filters which can be applied.

Comment 1

[laurel]

The last I heard, the decision was that we would only allow one filter action in
seamonkey.  Changing priority is one action, moving to another folder is one
action, deleting is one action, etc.

Changed the bug summary to add a clearer reference to a request for multiple
filter actions.

Comment 2

[Phil Peterson]

*** This bug has been marked as a duplicate of 13145 ***

Comment 3

[laurel]

Marking verified as duplicate.

Comment 4

[alex.seggie]

I disagree that this is a duplicate of 13145 which asks for
several actions in one mail filter.  I am asking that multiple filters
be allowed to activate.  With multiple actions there is only one triggering
condition. With multiple filters the conditions can be all the same (duplicating
the abilities of 13145) or they can all be different. What I want, is to be able
to set priority based on "body" content and then move to another folder based
on the sender. This will be difficult given 13145.  Request 16749 is also easier
to impliment than 13145. Just change ONE branch instruction. You need to go back
to the filter-to-do search loop instead of exiting after a filter sets the
priority or read status. Request 16749 requires UI redesign.

Comment 5

[alex.seggie]

Slight correction of the numbers:
Request 13145 requires UI redesign.
Request 16749 requires changed branch instruction.

Comment 6

[leger]

Clearing DUPLICATE resolution due to reopen of this bug.

Comment 7

[David :Bienvenu]

I'm confused - this works today. We only stop evaluating filters after a move,
so if you order your filters correctly, you should get the desired behaviour.
I've tried it myself and seen it work.

Comment 8

[alex.seggie]

I will try your test case if you give me the details.
I just re-tested with the following (one line is one filter) five filters.
The test failed.

If subject contains aa then priority:=lowest
If subject contains ee then priority:=low
If subject contains ii then priority:=high
If subject contains uu  then priority:=highest
If subject contains aa or ee or ii or uu move to test folder

I then changed all "subjects" to "body" and retested.  Failed

By failure I mean a subject of "aa ee ii uu" should cause all 4 filters
to activate (and to log the activation). Any message that contains any
of the four letter pairs should activate the move after the priority is set.
None of my test messages activated the move.

Hope this helps.

Comment 9

[Phil Peterson]

Fix up subject, M16. Scott, are we really promising this, or should this be a
[HELP WANTED] bug?

Comment 10

[laurel]

Bienvenu confirmed in an email to me Oct27 that this will be in 5.0.

Comment 11

[David :Bienvenu]

no body filters were working on 11/27, if I remember correctly. I believe this
works today, and am reassigning to me.

Comment 12

[alex.seggie]

Would you mind attaching a description of your test case please?
Are you testing under 4.7 or a later version?  I still see failures.

Thanks,

Alex

Comment 13

[David :Bienvenu]

5.0 - this is not a bug system for 4.x

Comment 14

[alex.seggie]

THAT explains everything. The window doesn't make that clear.
Looking forward to getting the fix.
Thank you for looking into the problem.

Alex