Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Stop Filter Execution

  • 3 odpowiedzi
  • 1 osoba ma ten problem
  • 2 wyświetlenia
  • Ostatnia odpowiedź od toes314

more options

Hi!

Although it may be that what I am seeking exists, I have looked for, but have not found, detailed information on filter actions within Thunderbird.

There was a discussion on this website in which someone seemingly indicated that the "Stop Filter Execution" action only stops the execution of the given filter, not other filters.

I am not sure of the scope that was intended for that comment. It would seem that while processing a particular piece of E-Mail, all that would be necessary to stop executing a particular filter, would be to not include an additional filter action. If I understand correctly, when the last filter action is complete in a given filter, that filter will not execute any more in connection with the current piece of E-Mail being processed. If instead, what was intended was that "Stop Filter Execution" will prevent that filter from being applied to any pieces of E-Mail to be processed within the current collection of E-Mail being retrieved, that would be nice to know.

I have a collection of filters, which if the filter's conditions are met, the filter will move the piece of E-Mail to a particular folder. In most cases, I don't want other filters which would normally be run after that filter, to be run against the piece of E-Mail which was moved.

So if there is a simple way to accomplish that, I would greatly appreciate knowing about it.

Hi! Although it may be that what I am seeking exists, I have looked for, but have not found, detailed information on filter actions within Thunderbird. There was a discussion on this website in which someone seemingly indicated that the "Stop Filter Execution" action only stops the execution of the given filter, not other filters. I am not sure of the scope that was intended for that comment. It would seem that while processing a particular piece of E-Mail, all that would be necessary to stop executing a particular filter, would be to not include an additional filter action. If I understand correctly, when the last filter action is complete in a given filter, that filter will not execute any more in connection with the current piece of E-Mail being processed. If instead, what was intended was that "Stop Filter Execution" will prevent that filter from being applied to any pieces of E-Mail to be processed within the current collection of E-Mail being retrieved, that would be nice to know. I have a collection of filters, which if the filter's conditions are met, the filter will move the piece of E-Mail to a particular folder. In most cases, I don't want other filters which would normally be run after that filter, to be run against the piece of E-Mail which was moved. So if there is a simple way to accomplish that, I would greatly appreciate knowing about it.

Zmodyfikowany przez toes314 w dniu

Wszystkie odpowiedzi (3)

more options

> I don't want other filters which would normally be run after that filter, to be run against the piece of E-Mail which was moved.

That is the intended purpose of the action Stop Filter Execution.

In your list of filter rules, as soon as a message meets the conditions of a filter rule that contains that action, then filtering of that message stops and all the rules below that filter rule will be skipped.

more options

I have a filter which is my first filter, and uses the "Stop Filter Execution" action as the last action. The first action, and only other action, is to move a message which matches the criteria, into a particular folder. I will see plenty of messages which match the filter, moved into the desired folder. However, some which match, are not moved into that folder. It is as if. other filters beyond that first filter, continue to run for a message which matches the first filter.

So, are there any concerns that the "Stop Filter Execution" action is not completely reliable?

I am using Thunderbird 102.7.1 (64-bit) on openSUSE Leap 15.4 Linux.

Any help would be greatly appreciated.

Further information: I have checked the filter log and in some cases, I can see one filter after another, both of which have "Stop Filter Execution" as their last action, being run against the same message ID, one after another. With each filter moving the message to a folder. ALSO, I do have installed a version of FiltaQuilla which is compatible with the version of Thunderbird which I am using, that being 102.7.1 ( 64 bit ).

Is there some possibility that FiltaQuilla could somehow interfere with other filtering?

Zmodyfikowany przez toes314 w dniu

more options

In my environment it appears that "Stop Filter Execution" works reliably IF the chosen condition type is "Match all messages".

Zmodyfikowany przez toes314 w dniu