Open Bug 537224 Opened 15 years ago Updated 2 years ago

"Run Filters on Folder" stops executing after applying some filters

Categories

(MailNews Core :: Filters, defect)

Product:
MailNews Core
Component:
Filters
Version:
1.9.1 Branch
Type:
defect

Tracking

(Not tracked)

People

(Reporter: thoskk, Unassigned)

References

Details

(Whiteboard: [SmBugEvent][filterfails]) 

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.6) Gecko/20091206 SeaMonkey/2.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.6) Gecko/20091206 SeaMonkey/2.0.1

When "Run Filters on Folder" is executed, it does not apply all filters in the list. It only executes a few, but then it stops. 
If you want to filter all mail in the specific folder, you either have to run it a several times, which does not always work. Or you have to manually select all messages in folder and execute "Run Filters on Message", which is what "Run Filters on Folder" should do. 

Reproducible: Always

Steps to Reproduce:
1. Open mail folder
2. set some filters
3. run filters on folder
Actual Results:  
Function stops after a few filters. 

Expected Results:  
All filters should be applied on all messages in folder. 

A workaround is to manually select all messages and execute "Run Filters on Message". Maybe that's a way to easily fix the bug.
Version: unspecified → SeaMonkey 2.0 Branch
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.10pre) Gecko/20100412 SeaMonkey/2.0.5pre - Build ID: 20100412001916

I'm seeing this sporadically on Linux. Retrying usually works for me. Autocompact (even when set to "ask me") seems to contribute to the problem, especially when the popup appears halfway through filtering.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: x86 → All
Related to bug 139215 ?
Just for feedback.: 
Problem still exists on (actual) Build 'Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.14) Gecko/20100930 SeaMonkey/2.0.9'.
It'd be nice to know if this still happens on SeaMonkey 2.1 or later, but it's maybe a little early to ask since Sm2.1 final hasn't yet been officially released.

Tentatively moving to MailNews_Core::Filters.
Component: General → Filters
Product: SeaMonkey → MailNews Core
QA Contact: general → filters
Whiteboard: [SmBugEvent]
Version: SeaMonkey 2.0 Branch → 1.9.1 Branch
Seems to be fixed for SeaMonkey version 2.0(.14).
Sorry, false alarm. The bug is back.
Didn't change anything. Just closed and re-opened seamonkey. Now the filter stops again after filtering one or several messages.
I'm running TB 7.0 Beta and have had this problem for years.  I'm running on Windows 7, with an IMAP backend. 

I filter some messages into a folder on the server side (using procmail).  When I visit that folder in TB, and want to run filters on it, it runs through them and runs some of the filters that mark messages as deleted.  I then need to manually compact the folder, run the filter set again, and then it does some filters that copy messages to another (local) folder, and then delete those messages (and manually compact the folder).  This process I need to repeat about 3 or 4 times in order to actually get all the filters processing all the messages.  

I take it that this isn't quite how it's supposed to work?
Filtering still buggy on Seamonkey 7.01.
Sorry, that's supposed to be Thunderbird 7.01 ... confused of all the PCs I'm working with.
Depends on: 697522
To bug opener: Are you talking about same problm as bug 419368?
Seems to be different to me. I only have one filter containing 'copy to' (as a final action in that filter) which applies only twice a month. 
The filtering problem already occured before I set up that filter rule.
Whiteboard: [SmBugEvent] → [SmBugEvent][filterfails]
(In reply to Thomas Oskk from comment #11)
> Seems to be different to me. 
> I only have one filter containing 'copy to' (as a final action in that filter)

Does "as a final action in that filter" mean other actions than "Copy to" are specified in the filter rule?
If yes, is "Delete" or "Move to" or "Stop Filter Execution" requested in the filter rule as "non-final action" for you?
How about "Delete" action in other message filter rules?

If you use "Delete" or "Stop Filter Execution", same problem as bug 695671?
Is this still happening in recent versions?
Yes, it's still valid for Seamonkey 2.11 (Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120715 SeaMonkey/2.11)
(In reply to WADA from comment #12)
> (In reply to Thomas Oskk from comment #11)
> > Seems to be different to me. 
> > I only have one filter containing 'copy to' (as a final action in that filter)
> 
> Does "as a final action in that filter" mean other actions than "Copy to"
> are specified in the filter rule?
> If yes, is "Delete" or "Move to" or "Stop Filter Execution" requested in the
> filter rule as "non-final action" for you?
> How about "Delete" action in other message filter rules?
> 
> If you use "Delete" or "Stop Filter Execution", same problem as bug 695671?

Sorry, must have missed your reply.
From what I can tell, it does not matter which action, or how many actions are defined in a filter rule, except those rules that do not include moving or copying messages.
And, of course, there are no such actions that would make further actions obsolete (e.g. "delete" or "stop execution"). That would not make much sense, if I understood the logics right.
I could not duplicate this - but then the STR are not really clearly spelled out.

Could you please define as clearly as possible a filter that shows this problem?

Also, please define exactly what does not work. So, for example, it is not clear to me if the issue is that filters completely apply on a subset of messages (and miss some messages), or if not all of the filter actions are getting applied.

There are multiple lists involved here:

1) a list of messages
2) a list of filters in a folder
3) a list of actions in a single filter

Please specify the the failure precisely enough so that I can tell which of these is being incompletely applied. Also, can you specify conditions where this always happens, or is it somewhat random?

"it does not apply all filters in the list" from comment 0 implies that 2) fails, so some filters in the list of filters apply to all messages, and other filters do not apply to any messages.

Also, does it happen only with a move? Moves are the most difficult filter to make work correctly. In reading the bug, it sounds like it also happens with copy. Can you give an example filter definition that has a copy and no move where this occurs?
I believe we will address this in bug 695671.

STR:

1) in a folder with many messages, one of which contains a subject "test", create two filters:

- IF Subject Contains test THEN StopExecution
- For all messages, add star

2) Run Filters On Folder

Expected: all messages except those with test in the subject will get a star
Actual: no messages get a star
Depends on: 695671
(In reply to Kent James (:rkent) from comment #17)
> STR:
> 1) in a folder with many messages, one of which contains a subject "test",
> create two filters:
> - IF Subject Contains test THEN StopExecution
> - For all messages, add star
> 2) Run Filters On Folder
> Expected: all messages except those with test in the subject will get a star
> Actual: no messages get a star

If this bug is related to StopExecution, what is difference among bug 537224(this bug) and bug 537501 and bug 552936?
Why such defference occurs?
(bug 537501 comment #23 : StopExecution seems ignored in some cases, but seems works is some cases... 2 COPY is relevant?)
(bug 552936 : StopExecution seems to work, so subsequesnt rule is not applied...) 

Following is comment by Thomas Oskk(bug opener) in Comment #15. 
> And, of course, there are no such actions that would make further actions obsolete (e.g. "delete" or "stop execution"). 
Kent James, how could you know this bug is problem which is relevant to StopExecution?
Severity: minor → S3
You need to log in before you can comment on or make changes to this bug.