Cisco Cisco Email Security Appliance C650 Guía Del Usuario
Chapter 2 Configuring Routing and Delivery Features
2-52
Cisco IronPort AsyncOS 7.5 for Email Advanced Configuration Guide
OL-25137-01
For more information, see “Monitoring and Managing via the CLI” in the Cisco
IronPort AsyncOS for Email Daily Management Guide. When hard bounce
message generation is disabled, none of these counters increments when a
recipient hard bounces.
IronPort AsyncOS for Email Daily Management Guide. When hard bounce
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. IronPort AsyncOS can be configured to send hard bounce
messages to an email address different than the Envelope Sender address.
in the message headers. IronPort 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 IronPort 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.
routing of SMTP bounce messages generated by the appliance as a result of a
conversational bounce. When an IronPort 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 Cisco IronPort 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 the
the message is injected into the Cisco IronPort 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 the
Table 2-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
retrying
60 seconds