Cisco Cisco Email Security Appliance C650 Guía Del Usuario
23-44
Cisco AsyncOS 8.5.5 for Email Security User Guide
Chapter 23 Configuring Routing and Delivery Features
Controlling Email Delivery Using Destination Controls
You can specify whether the appliance sends an alert if the TLS negotiation fails when delivering
messages to a domain that requires a TLS connection. The alert message contains name of the destination
domain for the failed TLS negotiation. The appliance sends the alert message to all recipients set to
receive Warning severity level alerts for System alert types. You can manage alert recipients via the
System Administration > Alerts page in the GUI (or via the
messages to a domain that requires a TLS connection. The alert message contains name of the destination
domain for the failed TLS negotiation. The appliance sends the alert message to all recipients set to
receive Warning severity level alerts for System alert types. You can manage alert recipients via the
System Administration > Alerts page in the GUI (or via the
alertconfig
command in the CLI).
To enable TLS connection alerts, click Edit Global Settings on the Destination Controls page or
destconfig -> setup
subcommand. This is a global setting, not a per-domain setting. For information
on the messages that the appliance attempted to deliver, use the Monitor > Message Tracking page or the
mail logs.
mail logs.
You must specify a certificate to use for all outgoing TLS connections. Use the Edit Global Settings on
the Destination Controls page or
the Destination Controls page or
destconfig -> setup
subcommand to specify the certificate. For
information on obtaining a certificate, see
.
For more information on alerts, see the “System Administration” chapter.
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.