User Guide
24-43
AsyncOS 9.1.2 for Cisco Email Security Appliances User Guide
Chapter 24 Configuring Routing and Delivery Features
Controlling Email Delivery Using Destination Controls
• TLS, page 24-43
• Bounce Verification, page 24-43
• Bounce Profile, page 24-43
Rate Limiting
• 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.
TLS
• Whether TLS connections to remote hosts will be accepted, allowed, or required (see Controlling
TLS, page 24-46).
• 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.
Bounce Verification
• Whether or not to perform address tagging via Bounce Verification (see Bounce Verification,
page 24-51).
Bounce Profile
• 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.
Related Topics
• Determining Which Interface is Used for Mail Delivery, page 24-43
• Default Delivery Limits, page 24-44
• Working with Destination Controls, page 24-44
Determining Which Interface is Used for Mail Delivery
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.