IronPort - advanced configuration guide

HTML Convert Action
6-62
Cisco IronPort AsyncOS 7.6 for Email Advanced Configuration Guide
Chapter 6 Using Message Filters to Enforce Email Policies
The following example shows a URL removed from a message and replaced with the text, ‘URL
REMOVED’:
URL_Replaced: if true {
edit-body-text("(?i)(?:https?|ftp)://[^\\s\">]+", "URL REMOVED");
}
The following example shows a social security number removed from the body of a message and
replaced with the text, “XXX-XX-XXXX’:
ssn: if true {
edit-body-text("(?!000)(?:[0-6]\\d{2}|7(?:[0-6]\\d|7[012]))([
-]?)(?!00)\\d\\d\\1(?!0000)\\d{4}",
"XXX-XX-XXXX");
}
Note You cannot use smart identifiers with the edit-body-text() filter at this time.
While RFC 2822 defines a text format for email messages, there are extensions (such as MIME) to
provide the transport of other content within an RFC 2822 message. AsyncOS can now use the
html-convert() message filter to convert HTML to plain text using the following syntax:
Convert_HTML_Filter:
if (true)
{
html-convert();
}
The Cisco IronPort message filters make a determination on whether a given MIME part is considered a
message “body” or a message “attachment”. The html-convert() filter only works on the message body
parts. For more information about message bodies and attachments, see Message Bodies vs. Message
Attachments, page 6-5.
Depending on the format, the html-convert() filter uses different methods to strip the HTML from
within the documents.
OL-25137-01