IronPort - advanced configuration guide

6-42
}
notify("admin@example.com");
Cisco IronPort AsyncOS 7.6 for Email Advanced Configuration Guide
Chapter 6 Using Message Filters to Enforce Email Policies
The following example adds a header if the message has an X.509 certificate:
AnyX509: if signed-certificate ("issuer") {
}
The following example adds a header if the message’s certificate does not have a signer:
Message Filter Actions
The purpose of message filters is to perform actions on selected messages.
The two types of actions are:
Final actions — such as deliver, drop, and bounce — end the processing of a message, and permit
no further processing through subsequent filters.
Non-final actions perform an action which permits the message to be processed further.
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.
Filter Actions Summary Table
insert-header("X-Test", "X.509 present");
NoSigner: if not signed-certificate ("signer") {
}
insert-header("X-Test", "Old X.509?");
Message filters can apply the following actions shown in Table 6-5 to an email message.
Table 6-5 Message Filter Actions
Action Syntax Description
Alter source host alt-src-host Change the source hostname and IP interface (Virtual
Gateway address) to send the message. See Alter Source
Host (Virtual Gateway address) Action, page 6-58.
Alter recipient alt-rcpt-to Change a recipient of the message. See Alter Recipient
Action, page 6-57.
Alter mailhost alt-mailhost Change the destination mail host for the message. See
Alter Delivery Host Action, page 6-57.
OL-25137-01