Need new function "STOP EXECUTION - ALL" for Global Filters, which will stop and not execute ANY further filters (global nor account-specific)
Categories
(MailNews Core :: Filters, defect)
Tracking
(Not tracked)
People
(Reporter: RuCla, Unassigned)
References
Details
Attachments
(1 file)
(deleted),
application/x-zip-compressed
|
Details |
Comment 1•15 years ago
|
||
Comment 3•15 years ago
|
||
Comment 4•15 years ago
|
||
Comment 6•15 years ago
|
||
Comment 7•15 years ago
|
||
Comment 8•15 years ago
|
||
Reporter | ||
Comment 10•15 years ago
|
||
Reporter | ||
Comment 11•15 years ago
|
||
Reporter | ||
Comment 12•15 years ago
|
||
Comment 13•15 years ago
|
||
Comment 14•15 years ago
|
||
Reporter | ||
Comment 15•15 years ago
|
||
Reporter | ||
Comment 16•15 years ago
|
||
Comment 17•15 years ago
|
||
Updated•15 years ago
|
Reporter | ||
Comment 18•15 years ago
|
||
Comment 19•15 years ago
|
||
Reporter | ||
Comment 20•15 years ago
|
||
Comment 21•15 years ago
|
||
Reporter | ||
Comment 22•15 years ago
|
||
Comment 23•15 years ago
|
||
Reporter | ||
Comment 24•15 years ago
|
||
Comment 25•15 years ago
|
||
Comment 26•15 years ago
|
||
Reporter | ||
Comment 27•15 years ago
|
||
Comment 28•15 years ago
|
||
Reporter | ||
Comment 29•15 years ago
|
||
Comment 30•15 years ago
|
||
Comment 31•14 years ago
|
||
Comment 32•13 years ago
|
||
Comment 33•13 years ago
|
||
Updated•13 years ago
|
Comment 34•12 years ago
|
||
Comment 35•12 years ago
|
||
Comment 36•12 years ago
|
||
Comment 37•12 years ago
|
||
Comment 38•12 years ago
|
||
Comment 39•12 years ago
|
||
Comment 40•12 years ago
|
||
Comment 41•12 years ago
|
||
Comment 42•12 years ago
|
||
Comment 43•12 years ago
|
||
Comment 44•12 years ago
|
||
Comment 46•10 years ago
|
||
Comment 47•10 years ago
|
||
Comment 48•10 years ago
|
||
Comment 49•10 years ago
|
||
Comment 50•9 years ago
|
||
Comment 51•6 years ago
|
||
Comment 52•5 years ago
|
||
(In reply to Giulioski from comment #51)
Stop Filter Execution does not stop any other filter execution when moving an email from one folder to an other.
Giulioski, Aryx,
Does this still happen in version 60 or 68? And if so,
- please post your filter rules.
- Does it only happen with Global Inbox as suggested in comment 2 and comment 40
Comment 53•4 years ago
|
||
I have this issue and have had on many occasions in the past.
"Stop Filter Execution" doesn't actually stop the filter execution. Usually occurs when you have the following:
mail for <specific_account>@mydomain.com shoud go into a specific folder
mail for <everything_else>@mydomain.com should go in another folder.
You would expect a filter rule for the first + "stop filter execution" and a generic one for the rest would do the trick, but it doesn't. Mail for <specific_account>@mydomain.com starts bouncing between the two target folders, which shouldn't happen, because the second filter rule should never by reached.
Comment 54•4 years ago
|
||
Does "go" mean "move to folder" in your filters?
Comment 55•4 years ago
|
||
yes
Comment 56•4 years ago
|
||
Thomas, should we close this?
Danny Pernokis offers the following perspective...
The reporter's main issue (as I understand it) seems to be that subsequent filters executed even when a STOP FILTER was present in previous filters. All the other things look like red herrings and confounding issues like MOVEs and inconsistent settings.
The bug as described was actually quite easy to test -- and it works fine and as expected. Works for me the way it has for years -- if a STOP FILTER is present at the end of a filter, that's the end of processing for that mailbox account. If there is no STOP FILTER, then the next item(s) gets processed. (It seems the reporter -- at the time -- could not achieve that simple binary.)
For my test account, I added two filters at the very top of the filter list. One added a tag ("testing") and the second added a star. If the STOP is present in the first filter, only the tag appears. If the STOP is absent, the star appears too. (I ran these for a basic test, then re-ran for extended testing, below.)
However... There is a confounding issue that I reported somewhere a long time ago (and can't find in my emails): A filter in the LOCAL FOLDERS area runs prior to any account-specific filters, and even if it says STOP FILTERS, the account-specific filter(s) will run.
I first re-ran the above tests, but added a new filter to LOCAL FOLDERS that set an additional tag ("to be filed"), then STOP FILTER. The second tag appeared in both cases -- in other words, LOCAL FOLDERS ran regardless all STOP FILTERS. (This did not test priority, only that both local and specific filters ran regardless.)
I then ran the above series of tests again, checking and observing READ status to test priority. (This is the only status that can be toggled -- all others are "turn on" but none are "turn off" except READ).
- When I put MARK READ in Local and MARK UNREAD in Specific, then the message shows with tags and appears unread.
- When I put MARK UNREAD in Local and MARK READ in Specific, then the message shows with tags and appears read.
This proved that (i) LOCAL FOLDERS runs first; (ii) its STOP FILTERS does not apply to account-specific filters; and (iii) that the account-specific filters override what may have been done in any LOCAL filters.
In hindsight, this has to be the preferred behaviour, because (i) the LOCAL FOLDERS section is intended to be global in scope -- affects all inbound emails; and (ii) the STOP FILTERS would stop further execution of any remaining filters in LOCAL FOLDERS; then (iii) the account-specific filter(s) can kick in.
Hope that helps!
-dan-
Comment 57•4 years ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #56)
(i) the LOCAL FOLDERS section is intended to be global in scope -- affects all inbound emails;
It's only supposed to take care of mails under Local Folders and not for the ones manages non-globally (e.g. as part of separate accounts).
Comment 58•4 years ago
|
||
(In reply to Sebastian Hengst [:aryx] (needinfo on intermittent or backout) from comment #57)
It's only supposed to take care of mails under Local Folders and not for the ones manages non-globally (e.g. as part of separate accounts).
It makes sense that filtering should cascade from global to specific (ie- Local Folders, then specific folders). This is a highly useful capability. Without the cascade, one would have to set up multiple copies of filters to apply a given global functionality to multiple accounts -- which is a lot of work for those with multiple accounts and leads to plenty of errors, omissions, and inconsistencies.
Functionally, if STOP EXECUTION in Local Folders halted all further (downstream) filtering, then the account-specific filters would never trigger, while omitting STOP EX means multiple subsequent filters in Local Folders would execute in turn, when perhaps they shouldn't.
My previous analysis cited by Wayne Mery in Comment #56 exactly mirrors how filtering works at present, and I wouldn't want to see it change. Not only would everyone lose a powerful functionality, but changes to filtering would introduce "silent changes" to user functionality which would unknowingly cause all kinds of different mysterious unexpected behaviours.
Comment 59•4 years ago
|
||
Thinking further (after re-reading the Reporter's Comment #2), I will add an additional qualification to my Comment #58 -- that there should be an additional form of global STOP EXECUTION (for example, "STOP EXECUTION - ALL") that can run for Local Folders, then stop and NOT execute any further filters -- neither global nor account-specific/folder-specific. (But don't change current STOP EXECUTION functionality as this will impact current user practice.)
Comment 60•3 years ago
|
||
Dan, your Comment 59 sounds like a good approach. We could morph the bug to that.
Aryx, would that work in the general case? And if not, is there an alternative?
Updated•2 years ago
|
Comment 61•2 years ago
|
||
Danny, can you fix up the bug summary to match comment 59?
Comment 62•2 years ago
|
||
I don't have ability to edit the bug summary field myself, but this is what I suggest:
"Need STOP EXECUTION - ALL for Global Filters, which will stop and not execute any further filters (global nor account-specific)"
Updated•2 years ago
|
Description
•