Cisco Cisco Email Security Appliance C170 Guia Do Utilizador

Concurrent Connections: number of simultaneous connections to remote hosts the appliance will 
attempt to open.

Maximum Messages Per Connection: number of messages your appliance will send to a destination 
domain before the appliance initiates a new connection.

Recipients: number of recipients the appliance will send to a given remote host in a given time 
period.

Limits: how to apply the limits you have specified on a per-destination and per MGA hostname 
basis.

Whether TLS connections to remote hosts will be accepted, allowed, or required (see 

).

Whether to send an alert when TLS negotiation fails when delivering a message to a remote host that 
requires a TLS connection. This is a global setting, not a per-domain setting.

Assign a TLS certificate to use for all outbound TLS connections to remote hosts.

Whether or not to perform address tagging via Cisco Bounce Verification (see 

).

Which bounce profile should be used by the appliance for a given remote host (the default bounce 
profile is set via the Network > Bounce Profiles page).

You can also control the default settings for unspecified domains.

Unless you specify the output interface via the 

deliveryconfig

 command or via a message filter 

(

alt-src-host

), or through the use of a virtual gateway, the output interface is selected by the AsyncOS 

routing table. Basically, selecting “auto” means to let AsyncOS decide.

In greater detail: local addresses are identified by applying the interface netmask to the interface IP 
address. Both of these are set via the Network > Interfaces page or by the 

interfaceconfig

 command 

(or during system setup). If the address space overlaps, the most specific netmask is used. If a destination 
is local, packets are sent via the appropriate local interface.

If the destination is not local, packets are sent to the default router (set via the Network > Routing page 
or with the 

setgateway

 command). The IP address of the default router is local. The output interface is 

determined by the rule for selecting the output interface for local addresses. For example, AsyncOS 
chooses the most specific IP address and netmask that include the default router's IP address.

The routing table is configured via the Network > Routing page (or via the 

routeconfig

 command). A 

matching entry in the routing table takes precedence over the default route. A more specific route take 
precedence over a less specific route.