Cisco Cisco Email Security Appliance C170 Guia Do Utilizador
26-39
User Guide for AsyncOS 10.0 for Cisco Email Security Appliances
Chapter 26 Configuring Routing and Delivery Features
Directing Bounced Email
Hard Bounces and the status Command
When hard bounce message generation is enabled, the following counters in the
status
and
status
detail
commands increment each time the appliance generates a hard bounce message for delivery:
For more information, see the “Monitoring and Managing via the CLI” chapter. When hard bounce
message generation is disabled, none of these counters increments when a recipient hard bounces.
message generation is disabled, none of these counters increments when a recipient hard bounces.
Note
The Envelope Sender address of the message envelope is different than the From: in the message headers.
AsyncOS can be configured to send hard bounce messages to an email address different than the
Envelope Sender address.
AsyncOS can be configured to send hard bounce messages to an email address different than the
Envelope Sender address.
Conversational Bounces and SMTP Routes Message Filter actions
Mappings for SMTP Routes and message filter actions are not applied to the routing of SMTP bounce
messages generated by the appliance as a result of a conversational bounce. When an appliance receives
a conversational bounce message, it generates an SMTP bounce message back to the Envelope Sender
of the original message. In this case, the appliance is actually generating the message, so any SMTP
Routes that apply to an injected message for relaying do not apply.
messages generated by the appliance as a result of a conversational bounce. When an appliance receives
a conversational bounce message, it generates an SMTP bounce message back to the Envelope Sender
of the original message. In this case, the appliance is actually generating the message, so any SMTP
Routes that apply to an injected message for relaying do not apply.
Example Bounce Profiles
Consider these two examples using different bounce profile parameters:
In Example 1, the first recipient delivery attempt is made at t=0, immediately after the message is
injected into the appliance. With the default initial retry time of 60 seconds, the first retry attempt is
made approximately one minute later at t=60. The retry interval is calculated and it is determined to use
injected into the appliance. With the default initial retry time of 60 seconds, the first retry attempt is
made approximately one minute later at t=60. The retry interval is calculated and it is determined to use
Counters: Reset Uptime Lifetime
Receiving
Messages Received 0 0 0
Recipients Received 0 0 0
Gen. Bounce Recipients 0 0 0
Table 26-6
Example 1: Bounce Profile Parameters
Parameter
Value
Max number of retries
2
Max number of seconds in queue
259,200 seconds (72 hours)
Initial number of seconds before retrying
60 seconds
Max number of seconds to wait before retrying
60 seconds