27.11.2012 Views

IronPort - advanced configuration guide

IronPort - advanced configuration guide

IronPort - advanced configuration guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

6-20<br />

Cisco <strong>IronPort</strong> AsyncOS 7.6 for Email Advanced Configuration Guide<br />

Chapter 6 Using Message Filters to Enforce Email Policies<br />

You can also use smart identifiers in content filters and as a part of content dictionaries.<br />

Note You cannot combine a smart identifier key word with a normal regular expression or another key word.<br />

For example the pattern *credit|*ssn would not be valid.<br />

Note To minimize on false positives using the *SSN smart identifier, it may be helpful to use the *ssn smart<br />

identifier along with other filter criteria. One example filter that can be used is the “only-body-contains”<br />

filter condition. This will only evaluate the expression to be true if the search string is present in all of<br />

the message body mime parts. For example, you could create the following filter:<br />

SSN-nohtml: if only-body-contains(“*ssn”) { duplicate-quarantine(“Policy”);}<br />

Examples of Message Filter Rules<br />

True Rule<br />

Valid Rule<br />

notify("legaldept@example.com");<br />

}<br />

.<br />

The following section shows examples of message filter rules in use.<br />

The true rule matches all messages. For example, the following rule changes the IP interface to external<br />

for all messages it tests.<br />

externalFilter:<br />

if (true)<br />

{<br />

}<br />

alt-src-host('external');<br />

The valid rule returns false if the message contains unparsable/invalid MIME parts and true otherwise.<br />

For example, the following rule drops all unparsable messages it tests.<br />

not-valid-mime:<br />

if not valid<br />

{<br />

OL-25137-01

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!