27.11.2012 Views

IronPort - advanced configuration guide

IronPort - advanced configuration guide

IronPort - advanced configuration guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 2 Configuring Routing and Delivery Features<br />

OL-25137-01<br />

Figure 2-19 Four Virtual Gateway Addresses on One Ethernet Interface<br />

IP interface: PrivateNet (e.g. 192.168.1.1)<br />

Note that four separate IP interfaces can be used to deliver mail, where only one public listener is<br />

configured to accept messages from the Internet.<br />

Mapping Messages to IP Interfaces for Delivery<br />

The altsrchost command provides the simplest and most straightforward method to segment each<br />

Cisco <strong>IronPort</strong> appliance into multiple IP interfaces (Virtual Gateway addresses) from which to deliver<br />

email. However, users requiring more power and flexibility in mapping messages to particular Virtual<br />

Gateways should investigate the use of message filters. See Chapter 6, “Using Message Filters to<br />

Enforce Email Policies” for more information.<br />

The altsrchost command allows you to control which IP interface or interface group to use during<br />

email delivery based on one of the following:<br />

the sender’s IP address<br />

the Envelope Sender address<br />

SMTP<br />

Public<br />

listener:<br />

InboundMail<br />

IP interface:<br />

PublicNet<br />

192.168.2.1<br />

SMTP SMTP SMTP<br />

SMTP<br />

IP interface:<br />

PublicNet2<br />

192.168.2.2<br />

IP interface:<br />

PublicNet3<br />

192.168.2.3<br />

Ethernet interface: Data 2<br />

Ethernet interface: Data 1<br />

To specify which IP interface or interface group the system will deliver email from, you create mapping<br />

keys that pair either the sender’s IP address or the Envelope Sender address to an IP interface or interface<br />

group (specified by interface name or group name).<br />

Cisco <strong>IronPort</strong> AsyncOS will compare both the IP address and Envelope Sender address to the mapping<br />

keys. If either the IP address or Envelope Sender address matches one of the keys, the corresponding IP<br />

interface is used for the outbound delivery. If there is no match, the default outbound interface will be<br />

used.<br />

The system can match any of the following keys and take preference in the following order:<br />

Sender’s IP address The IP address of the sender must match exactly.<br />

Fully-formed Envelope<br />

Sender<br />

Example: 192.168.1.5<br />

The Envelope Sender must match the entire address exactly.<br />

Example: username@example.com<br />

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

IP interface:<br />

PublicNet4<br />

192.168.2.4<br />

2-63

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

Saved successfully!

Ooh no, something went wrong!