Cisco Cisco Email Security Appliance C160 Mode D'Emploi

For C370, C670, X1070, C380, C680, C390, and C690 appliances: Cisco recommends using one of 
the physical Ethernet ports to connect directly to the Internet for the purposes of receiving inbound email 
through public listeners, and using another physical Ethernet port to connect directly to your internal 
network for the purposes of relaying outbound email through private listeners.

For C170 and C190 appliances: Typically, the System Setup Wizard will configure only one physical 
Ethernet port with one listener for both receiving inbound email and relaying outbound email.

See 

. 

The following information is required:

The IP address assigned by your network administrator. This can be an IPv4 address, an IPv6 
address, or both.

For IPv4 addresses: the netmask of the interface. AsyncOS only accepts a netmask in CIDR format. 
For example, 

/24

 for the 

255.255.255.0

 subnet.

For IPv6 addresses: the prefix in CIDR format. For example 

/64

 for a 64-bit prefix.

(optional) A fully-qualified hostname for the IP address.

IP addresses within the same subnet cannot be configured on separate physical Ethernet interfaces. See 

 for more detailed information on Network and IP 

Address configuration.

When configuring your interfaces to accept mail, you define:

the domain for which to accept mail

destination (SMTP Route) for each domain, this is optional

Mark the checkbox for Accept Incoming Mail to configure the interface to accept mail. Enter the name 
of the domain for which to accept mail.

Enter the Destination. This is the SMTP Route or name of the machine(s) where you would like to route 
email for the domains specified.

This is the first SMTP Routes entry. The SMTP Routes table allows you to redirect all email for each 
domain (also known as a Recipient Access Table (RAT) entry) you enter to a specific mail exchange 
(MX) host. In typical installations, the SMTP Routes table defines the specific groupware (for example, 
Microsoft Exchange) server or the “next hop” in the email delivery for your infrastructure. 

For example, you can define a route that specifies that mail accepted for the domain 

example.com

 and 

all of its subdomains 

.example.com

 is routed the to the groupware server 

exchange.example.com

.

You can enter multiple domains and destinations. Click Add Row to add another domain. Click the trash 
can icon to remove a row.

Configuring SMTP Routes in this step is optional. If no SMTP routes are defined, the system will use 
DNS to lookup and determine the delivery host for the incoming mail received by the listener. (See 

You must add at least one domain to the Recipient Access Table. Enter a domain —

example.com

, for 

example. To ensure that mail destined for any subdomain of 

example.net

 will match in the Recipient 

Access Table, enter 

.example.net

 as well as the domain name. For more information, see