Yes, S in that position should stop all transaction filtering:

To understand the difference between the 'X' and 'S' actions, you need to be aware that transaction filtering is done in several "passes", each pass testing a different state of the SMTP transaction. The 'X' action only exits from the current pass, meaning that future passes will still take place. The 'S' action, however, exits from the current pass and suppresses all further transaction filtering on the message altogether.

Hi all

I am a bit confused about the 'S' command in the transaction rules.
The rules explanation says: "The
 'S' action, however, exits from the current pass and suppresses all
 further transaction filtering on the message altogether."

I designed a filter wanting to target a specific sending smtp server, and took the following approach:

H, "*theserver*", S-N
R, "an address", R, "554 go away"


I expected this to work as follows: if the helo does not contain 'theserver' , the 'S' action would trigger, and all subsquent filters would be omitted
for this message.
But the 'R' rule is allways triggered.

What am I missing?

Henk

Transaction level filtering does unfortunately not allow combining all kinds of rules. Depending on what you want to accomplish here are some examples that should work.

 
If you want to stop all mail from 'theserver':

 H, "*theserver*", R, "554 go away"

If you want to allow all mail from 'theserver' and stop everything else sent to 'an address':

H, "*theserver*", S

R, "an address", R, "554 go away"

 /Rolf

HI Rolf

Isn't your example exactly the same as mine?
Using:

H, "*theserver*", S-N    ( only difference is the N )

I expected the filtering to stop for that message, in this case skip the R filter. That doesn't happen.
It skips filtering the helo, but still filters other transactions in the same message.