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 5 Configuring the Gateway to Receive Email<br />

Sender Verification Exception Table<br />

OL-25136-01<br />

The sender verification exception table is a list of domains or email addresses that will either be<br />

automatically allowed or rejected during the SMTP conversation. You can also specify an optional<br />

SMTP code and reject response for rejected domains. There is only one sender verification exception<br />

table per Cisco <strong>IronPort</strong> appliance and it is enabled per mail flow policy.<br />

The sender verification exception table can be used to list obviously fake but correctly formatted<br />

domains or email addresses from which you want to reject mail. For example, the correctly formatted<br />

MAIL FROM: pres@whitehouse.gov could be listed in the sender verification exception table and set<br />

to be automatically rejected. You can also list domains that you want to automatically allow, such as<br />

internal or test domains. This is similar to envelope recipient (SMTP RCPT TO command) processing<br />

which occurs in the Recipient Access Table (RAT).<br />

The sender verification exception table is defined in the GUI via the Mail Policies > Exception Table<br />

page (or the CLI, via the exceptionconfig command) and then is enabled on a per-policy basis via the<br />

GUI (see Implementing Sender Verification for the ACCEPTED Mail Flow Policy, page 5-46) or the CLI<br />

(see the Cisco <strong>IronPort</strong> <strong>AsyncOS</strong> CLI Reference <strong>Guide</strong>.<br />

Entries in the sender verification exception table have the following syntax:<br />

Figure 5-27 Exception Table Listing<br />

See Creating the Sender Verification Exception Table via the GUI, page 5-47 for more information about<br />

modifying the exception table.<br />

Implementing Sender Verification — Example Settings<br />

This section provides an example of a typical conservative implementation of host and envelope sender<br />

verification.<br />

For this example, when implementing host sender verification, mail from connecting hosts for which<br />

reverse DNS lookup does not match is throttled via the existing SUSPECTLIST sender group and<br />

THROTTLED mail flow policy.<br />

A new sender group (UNVERIFIED) and a new mail flow policy (THROTTLEMORE) are created. Mail<br />

from connecting hosts which are not verified will be throttled (using the UNVERIFIED sender group<br />

and the more aggressive THROTTLEMORE mail flow policy) prior to the SMTP conversation.<br />

Envelope sender verification is enabled for the ACCEPTED mail flow policy.<br />

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

5-43

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

Saved successfully!

Ooh no, something went wrong!