Re: [Evolution] filter processing stops after 1st filter executes

On Thu, 2012-07-05 at 18:06 +0000, Paul's unattended mail wrote:
The logs show that the first filter execution ends with something like
"stop processing filters" -- even though I have no such instruction in
my filter.  I even examined the XML of the filter to verify that there
is no "stop" instruction.

the code [1] suggests it's intentional, once you use a move,
the filtering is stopped automatically.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]