Cisco Cisco Email Security Appliance C170 Guia Do Utilizador
25-47
User Guide for AsyncOS 9.7 for Cisco Email Security Appliances
Chapter 25 Configuring Routing and Delivery Features
Controlling Email Delivery Using Destination Controls
Controlling Bounce Verification Tagging
You can specify whether or not mail sent is tagged for bounce verification. You can specify this for the
default, as well as specific destinations. Cisco suggests enabling bounce verification for the default, and
then creating new destinations for specific exclusions. See
default, as well as specific destinations. Cisco suggests enabling bounce verification for the default, and
then creating new destinations for specific exclusions. See
for more
information.
Controlling Bounces
In addition to controlling the number of connections and recipients will deliver to a remote host, you can
also specify a bounce profile to be used for that domain. If specified, the bounce profile appears in the
fifth column of the
also specify a bounce profile to be used for that domain. If specified, the bounce profile appears in the
fifth column of the
destconfig
command. If you do not specify a bounce profile, the default bounce
profile will be used. For more information, see
Adding a New Destination Control Entry
Procedure
Step 1
Click Add Destination:
Step 2
Configure the entry.
Step 3
Submit and commit your changes.
Importing and Exporting Destination Control Configurations
If you are managing multiple domains, you can create a single configuration file to define Destination
Control entries for all of the domains and import it onto the appliance. The format of the configuration
file is similar to a Windows INI configuration file. The parameters for a domain are grouped in a section
with the domain name as the section name. For example, use the section name
Control entries for all of the domains and import it onto the appliance. The format of the configuration
file is similar to a Windows INI configuration file. The parameters for a domain are grouped in a section
with the domain name as the section name. For example, use the section name
[example.com]
to group
the parameters for the domain example.com. Any parameter that is not defined will be inherited from
the default Destination Control entry. You can define the parameters for the default Destination Control
entry by including a
the default Destination Control entry. You can define the parameters for the default Destination Control
entry by including a
[DEFAULT]
section in the configuration file.
Importing the configuration file overwrites all of appliance’s Destination Control entries, except for the
default entry unless the configuration file includes the
default entry unless the configuration file includes the
[DEFAULT]
section. All other existing Destination
Control entries will be deleted.