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.

Chapter 2 Configuring Routing and Delivery Features<br />

OL-25137-01<br />

Note The processing of the domain map feature happens immediately before the RAT and right after Default<br />

Domain is evaluated. Refer to “Understanding the Email Pipeline” in the Cisco <strong>IronPort</strong> AsyncOS for<br />

Email Configuration Guide.<br />

A common implementation of the domain map feature is to accept incoming mail for more than one<br />

legacy domain. For example, if your company has acquired another company, you could construct a<br />

domain map on the Cisco <strong>IronPort</strong> appliance to accept messages for the acquired domain and rewrite the<br />

Envelope Recipients to your company’s current domain.<br />

Note You can configure up to 20,000 separate, unique domain mappings.<br />

Table 2-4 Domain Map Table Example Syntax<br />

Left Side Right Side Comments<br />

username@example.com username2@example.net Only complete address for the<br />

right side<br />

user@.example.com user2@example.net<br />

@example.com user@example.net<br />

or<br />

@example.net<br />

@.example.com user@example.net<br />

In the following example, the domainmap subcommand of the listenerconfig command is used to<br />

create a domain map for the public listener “InboundMail.” Mail for the domain and any subdomain of<br />

oldcompanyname.com is mapped to the domain example.com. The mapping is then printed for<br />

confirmation. Contrast this example with the <strong>configuration</strong> of placing both domains in the listener’s<br />

RAT: the domain map feature will actually rewrite the Envelope Recipient of joe@oldcomapanyname.com<br />

to joe@example.com, whereas placing the domain oldcompanyname.com in the listener’s RAT will simply<br />

accept the message for joe@oldcompanyname.com and route it without rewriting the Envelope Recipient.<br />

Also, contrast this example with the alias table feature. Alias tables must resolve to an explicit address;<br />

they cannot be constructed to map “any username@domain” to<br />

“the same username@newdomain.”<br />

mail3.example.com> listenerconfig<br />

Currently configured listeners:<br />

or<br />

@example.net<br />

1. Inboundmail (on PublicNet, 192.168.2.1) SMTP TCP Port 25 Public<br />

2. Outboundmail (on PrivateNet, 192.168.1.1) SMTP TCP Port 25 Private<br />

Choose the operation you want to perform:<br />

Complete address or<br />

fully-qualified domain name.<br />

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

2-29

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

Saved successfully!

Ooh no, something went wrong!