IronPort - advanced configuration guide

Chapter 2 Configuring Routing and Delivery Features
OL-25137-01
After creating the required IP interfaces, you have two options for setting up the Virtual Gateway
addresses and defining which email campaign will be sent from each IP interface or interface group:
Step 1 You can use the altsrchost command to map email from specific sender IP addresses or Envelope
Sender address information to a host IP interface (Virtual Gateway address) or interface group for
delivery.
Step 2 Using message filters, you can set up specific filters to deliver flagged messages using a specific host IP
interface (Virtual Gateway address) or interface group. See Alter Source Host (Virtual Gateway address)
Action, page 6-58. (This method is more flexible and powerful than the one above.)
For more information about creating IP interfaces, see the “Accessing the Appliance” appendix in the
Cisco IronPort AsyncOS for Email Configuration Guide.
So far, we have been using an Email Gateway configuration with the following interfaces defined as
shown in Figure 2-15.
Figure 2-15 Example Public and Private Interfaces
In the following example, the IP Interfaces page confirms that these two interfaces (PrivateNet and
PublicNet) have been configured, in addition to the Management interface.
Figure 2-16 IP Interfaces Page
IP interface: PublicNet 192.168.2.1
Ethernet interface: Data 2
Ethernet interface: Data 1
IP interface: PrivateNet 192.168.1.1)
Next, the Add IP Interface page is used to create a new interface named PublicNet2 on the Data2 Ethernet
interface. The IP address of 192.168.2.2 is used, and the hostname of mail4.example.com is specified.
The services for FTP (port 21), Telnet (port 23), and SSH (port 22) are then enabled.
Cisco IronPort AsyncOS 7.6 for Email Advanced Configuration Guide
IronPort Email
Security appliance
2-61