27.11.2012 Views

IronPort - Configuration Guide - AsyncOS 7.6.1

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

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

Chapter 6 Email Security Manager<br />

Policy Matching<br />

First Match Wins<br />

OL-25136-01<br />

You manage these tables using the Mail Policies > Incoming Mail Policies or Outgoing Mail Policies<br />

pages in the GUI, or the policyconfig command in the CLI. You can assign individual mail policies to<br />

delegated administrators whose responsibilities include managing your mail system. See the “Common<br />

Administrative Tasks” chapter in Cisco <strong>IronPort</strong> <strong>AsyncOS</strong> for Email Daily Management <strong>Guide</strong> for more<br />

information.<br />

Note DLP scanning can only be performed on outgoing messages.<br />

Examples of Policy Matching<br />

As incoming messages are received by listeners on the system, each message recipient matches a policy<br />

in one of the tables, regardless of the number of listeners configured on the system. Matches are based<br />

on either the recipient’s address or the sender’s address:<br />

Recipient address matches the Envelope Recipient address<br />

When matching recipient addresses, the recipient addresses entered are the final addresses after<br />

processing by preceding parts of the email pipeline. For example, if enabled, the default domain,<br />

LDAP routing or masquerading, alias table, domain map, and message filters features can rewrite<br />

the Envelope Recipient address and may affect whether the message matches a policy in the Email<br />

Security Manager (Anti-Spam, Anti-Virus, Content Filters, and Outbreak Filters).<br />

Sender address matches:<br />

– Envelope Sender (RFC821 MAIL FROM address)<br />

– Address found in the RFC822 From: header<br />

– Address found in the RFC822 Reply-To: header<br />

Addresses may be matched on either a full email address, user, domain, or partial domain, and addresses<br />

may also match LDAP group membership.<br />

Each recipient is evaluated for each policy in the appropriate table (incoming or outgoing) in a top-down<br />

fashion.<br />

For each recipient of a message, the first matching policy wins. If a recipient does not match any specific<br />

policy, the recipient will automatically match the default policy of the table.<br />

If a match is made based on a sender address (or on the special “Listener” rule created by an upgrade —<br />

see below), all remaining recipients of a message will match that policy. (This is because there can be<br />

only one sender or one listener per message.)<br />

The following examples help show how the policy tables are matched in a top-down fashion.<br />

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

6-3

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

Saved successfully!

Ooh no, something went wrong!