Cisco Cisco Email Security Appliance C160 Betriebsanweisung

A common implementation of the domain map feature is to accept incoming mail for more than one 
legacy domain. For example, if your company has acquired another company, you could construct a 
domain map on the appliance to accept messages for the acquired domain and rewrite the Envelope 
Recipients to your company’s current domain. 

You can configure up to 20,000 separate, unique domain mappings.

In the following example, the 

domainmap

 subcommand of the 

listenerconfig

 command is used to 

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

oldcompanyname.com

 is mapped to the domain 

example.com

. The mapping is then printed for 

confirmation. Contrast this example with the configuration of placing both domains in the listener’s 
RAT: the domain map feature will actually rewrite the Envelope Recipient of 

joe@oldcomapanyname.com

 

to 

joe@example.com

, whereas placing the domain 

oldcompanyname.com

 in the listener’s RAT will simply 

accept the message for 

joe@oldcompanyname.com

 and route it without rewriting the Envelope Recipient. 

Also, contrast this example with the alias table feature. Alias tables must resolve to an explicit address; 
they cannot be constructed to map “any username

@domain

” to 

“the same username

@newdomain

.”

Only complete address for the 
right side

Complete address or 
fully-qualified domain name. 

mail3.example.com> listenerconfig

Currently configured listeners:

1. Inboundmail (on PublicNet, 192.168.2.1) SMTP TCP Port 25 Public

2. Outboundmail (on PrivateNet, 192.168.1.1) SMTP TCP Port 25 Private

Choose the operation you want to perform:

- NEW - Create a new listener.

- EDIT - Modify a listener.

- DELETE - Remove a listener.