Hello. I'm a long time user of Pegasus as a simple POP3 client on a single computer. Now on v. 4.31. I just discovered a content control issue that is either a bug or an implementation I don't understand. I created two active content control definitions (because I want each to produce a different action. No error in the syntax checker for each.) Call one A and one B. If I set each ones action to simply colorize the display line for new mail (my diagnostic for checking whether a rule set is triggered), each works fine, no matter their order. (Tested by downloading a spam that will trigger one definition but not the other.) Now I change the action for A to "move an offending mail to xxx folder." The ordering is A before B. If a new piece of mail fits the A criteria, the action fires. However, if a new piece of mail fits only the B criteria, the B action does not fire.
IOW, just changing the *action* for the first definition from a simple color indication to a moving of the file prevents processing by the second definition. Now I know the helpfile indicates that processing will stop when a move action *occurs.* But it doesn't say that processing will stop when that definition is not met. Why does it stop?
In case it matters, the test in the A definition is a single instance of an "if body contains" 'literal string' match. The test in the B definition is a long set of conditions, including multiple regular expression matches. .
Hope I've explained it clearly. Is this a bug, or am I missing something? Thanks for any help,
Ron
<p>Hello.&nbsp; I'm a long time user of Pegasus as a simple POP3 client on a single computer.&nbsp; Now on v. 4.31.&nbsp; I just discovered a content control issue that is either a bug or an implementation I don't understand.&nbsp; I created two active content control definitions (because I want each to produce a different action.&nbsp; No error in the syntax checker for each.)&nbsp; Call one A and one B.&nbsp; If I set each ones action to simply colorize the display line for new mail (my diagnostic for checking whether a rule set is triggered), each works fine, no matter their order.&nbsp; (Tested by downloading a spam that will trigger one definition but not the other.)&nbsp; Now I change the action for A to "move an offending mail to xxx folder."&nbsp; The ordering is A before B.&nbsp; If a new piece of mail fits the A criteria, the action fires.&nbsp; However, if a new piece of mail fits only the B criteria, the B action does not fire.&nbsp; </p><p>IOW, just changing the *action* for the first definition from a simple color indication to a moving of the file prevents processing by the second definition.&nbsp; Now I know the helpfile indicates that processing will stop when a move action *occurs.*&nbsp; But it doesn't say that processing will stop when that definition is not met.&nbsp; Why does it stop?</p><p>In case it matters, the test in the A definition is a single instance of an "if body contains" 'literal string' match.&nbsp; The test in the B definition is a long set of conditions, including multiple regular expression matches.&nbsp; . &nbsp;
</p><p>Hope I've explained it clearly. Is this a bug, or am I missing something?&nbsp; Thanks for any help,</p><p>&nbsp;Ron
</p>
