Cisco Cisco Email Security Appliance C160 Mode D'Emploi

Non-final message filter actions are cumulative. If a message matches multiple filters where 
each filter specifies a different action, then all actions are accumulated and enforced. However, 
if a message matches multiple filters specifying the same action, the prior actions are overridden 
and the final filter action is enforced.

The intuitive meaning of a filter specification is:

 if the message matches the rule, then apply the actions in sequence. If the 

else

 clause is present, the 

actions within the 

else

 clause are executed in the event the message does not match the rule. 

The name of the filter you specify makes it easier to manage filters when you are activating, deactivating, 
or deleting them.

Message filters use the following syntax:

Note that you can omit any alternative actions:

You can combine several filters in sequence within a single text file, one following the other.

You must enclose the values in filters in either single or double quotation marks. Single or double 
quotation marks must be equally paired on each side of the value; for example, the expressions 

notify('customercare@example.com')

 and 

notify("customercare@example.com")

 are both legal, but 

the expression 

notify("customercare@example.com')

 causes a syntax error.

Lines beginning with a ‘

#

’ character are considered comments and are ignored; however, they are not 

preserved by AsyncOS as can be verified by viewing a filter via 

filters -> detail

.

expedite:

filter name

if (recv-listener == 'InboundMail' or recv-int == 'notmain')

rule specification

{

    alt-src-host('outbound1');

skip-filters(); 

}

action specification

else

{

    alt-src-host('outbound2');

}

optional alternative action 
specification

filter name

if ((not (recv-listener == 'InboundMail')) and

rule specification

{

    alt-src-host('outbound2');

skip-filters(); 

action specification