IronPort - advanced configuration guide

Chapter 6 Using Message Filters to Enforce Email Policies
OL-25137-01
Note The strip-headers and insert-header actions can be used in combination to rewrite any message
headers in the original message. In some case, it is valid to have multiple instances of the same header
(for example, Received:) where in other cases, multiple instances of the same header could confuse a
MUA (for example, multiple Subject: headers.)
Edit Header Text Action
Edit Body Text Action
When working with headers, remember that the current value of the header includes changes made
during processing (such as with filter actions that add, remove, or modify message headings). See
Message Header Rules and Evaluation, page 6-4 for more information.
The edit-header-text action allows you to rewrite specified header text using the regular expression
substitution function. The filter matches the regular expression within the header and replaces it with a
regular expression you specify.
For example, an email contains the following subject header:
Subject: SCAN Marketing Messages
The following filter removes the “SCAN” text, and leaves the text, “Marketing Messages”, in the header:
Remove_SCAN: if true
}
{
edit-header-text (‘Subject’, ‘^SCAN\\s*’,’’);
After the filter processes the message, it returns the following header:
Subject: Marketing Messages
The edit-body-text() message filter is similar to the Edit-Header-Text() filter, but it operates across
the body of the message instead of one of the headers.
The edit-body-text() message filter uses the following syntax where the first parameter is the regular
expression to search for and the second parameter is the replacement text:
Example: if true {
edit-body-text("parameter 1",
"parameter 2");
}
The edit-body-text() message filter only works on the message body parts. For more information
about whether a given MIME part is considered a message “body” or a message “attachment”, see
Message Bodies vs. Message Attachments, page 6-5.
Cisco IronPort AsyncOS 7.6 for Email Advanced Configuration Guide
6-61