Cisco Cisco Email Security Appliance C170 Guia Do Utilizador

Submit and commit your changes.

You can use the 

bvconfig

 and 

destconfig

 commands in the CLI to configure bounce verification. These 

commands are discussed in the CLI Reference Guide for AsyncOS for Cisco Email Security Appliances.

Bounce verification works in a cluster configuration as long as both appliances use the same "bounce 
key." When you use the same key, either systems should be able to accept a legitimate bounce back. The 
modified header tag/key is not specific to each appliance. 

The 

deliveryconfig

 command sets parameters to be used when delivering email from the appliance. 

The appliance accepts email using multiple mail protocols: SMTP and QMQP. However, all outgoing 
email is delivered using SMTP, which is why the 

deliveryconfig

 command does not require that the 

protocol be specified.

Several of the features or commands described in this section will affect, or be affected by routing 
precedence. Please see the “Assigning Network and IP Addresses” appendix for more information.

By default, the system uses an IP interface or IP interface group for email delivery. Any currently 
configured IP interface or IP interface group can be set. If no specific interface is identified, AsyncOS 
will use the hostname associated with the default delivery interface in the 

SMTP HELO

 command when 

communicating with recipient hosts. To configure IP interfaces, use the 

interfaceconfig

 command. 

These are the rules for using Auto selection of email delivery interfaces:

If the remote email server is on the same subnet as one of the configured interfaces, then traffic will 
go out on the matching interface.

When set to auto-select, static routes you have configured using 

routeconfig

 take effect. 

Otherwise, the interface that is on the same subnet as the default gateway will be used. If all of the 
IP addresses have an equivalent route to the destination, then the system uses the most efficient 
interface available.