IronPort - advanced configuration guide

Chapter 2 Configuring Routing and Delivery Features
Example Text File with Valid Mappings for the altsrchost Command
OL-25137-01
# Comments to describe the file
@example.com DemoInterface
paul@ PublicInterface
joe@ PublicInterface
192.168.1.5, DemoInterface
steve@example.com PublicNet
The import and export subcommands operate on a line-by-line basis and map either the sender IP
address or the Envelope Sender address line to the interface name. The key must be the first block of
non-space characters followed by the interface name in the second block of non-space characters,
separated by a comma (,) or space ( ). Comment lines start with a number sign (#) and will be ignored.
Adding an altsrchost Mapping through the CLI
In the following example, the altsrchost table is printed to show that there are no existing mappings.
Two entries are then created:
Mail from the groupware server host named @exchange.example.com is mapped to the PublicNet
interface.
Mail from the sender IP address of 192.168.35.35 (for example, the marketing campaign messaging
system) is mapped to the PublicNe2t interface.
Finally, the altsrchost mappings are printed to confirm and the changes are committed.
mail3.example.com> altsrchost
There are currently no mappings configured.
Choose the operation you want to perform:
- NEW - Create a new mapping.
- IMPORT - Load new mappings from a file.
[]> new
Enter the Envelope From address or client IP address for which you want to set up a
Virtual Gateway mapping. Partial addresses such as "@example.com" or "user@" are
allowed.
[]> @exchange.example.com
Cisco IronPort AsyncOS 7.6 for Email Advanced Configuration Guide
2-65