Cisco Cisco Email Security Appliance C170 Guia Do Utilizador
24-37
Cisco AsyncOS 9.1 for Email User Guide
Chapter 24 Configuring Routing and Delivery Features
Directing Bounced Email
•
By default, the system generates a bounce message and sends it to the original sender for each hard
bounced recipient. (The message is sent to the address defined in the Envelope Sender address of
the message envelope. Envelope From is also commonly referred to as the Envelope Sender.) You
can disable this feature and instead rely on log files for information about hard bounces. (See the
“Logging” chapter.)
bounced recipient. (The message is sent to the address defined in the Envelope Sender address of
the message envelope. Envelope From is also commonly referred to as the Envelope Sender.) You
can disable this feature and instead rely on log files for information about hard bounces. (See the
“Logging” chapter.)
•
Soft bounces become hard bounces after the maximum time in queue or the maximum number of
retries, whichever comes first.
retries, whichever comes first.
Bounce Profile Parameters
When configuring a bounce profile, the following parameters control how conversational bounces are
handled per message:
handled per message:
Table 24-5
Bounce Profile Parameters
Maximum number of
retries
retries
The number of times the system should try to reconnect to the recipient host to
re-deliver the soft bounced message before treating it as a hard bounced
message. The default is 100 retries.
re-deliver the soft bounced message before treating it as a hard bounced
message. The default is 100 retries.
Maximum number of
seconds in queue
seconds in queue
The amount of time the system should spend trying connect to the recipient host
to re-deliver the soft bounced message before treating it as a hard bounced
message. The default is 259,200 seconds (72 hours).
to re-deliver the soft bounced message before treating it as a hard bounced
message. The default is 259,200 seconds (72 hours).
Initial number of
seconds to wait before
retrying a message
seconds to wait before
retrying a message
The amount of time the system should wait before the first attempt to re-deliver
the soft bounced message. The default is 60 seconds. Set the initial retry time to
a high value to reduce the frequency of soft bounce attempts. Conversely, to
increase the frequency, lower the value.
the soft bounced message. The default is 60 seconds. Set the initial retry time to
a high value to reduce the frequency of soft bounce attempts. Conversely, to
increase the frequency, lower the value.
Maximum number of
seconds to wait before
retrying a message
seconds to wait before
retrying a message
The maximum amount of time the system should wait before trying to re-deliver
the soft bounced message. The default is 3,600 seconds (1 hour). This is not the
interval between each subsequent try; rather, it is another parameter that can be
used to control the number of retries. The initial retry interval is limited on the
high end by the maximum retry interval. If the calculated retry interval period
exceeds the maximum retry interval then the maximum retry interval is used
instead.
the soft bounced message. The default is 3,600 seconds (1 hour). This is not the
interval between each subsequent try; rather, it is another parameter that can be
used to control the number of retries. The initial retry interval is limited on the
high end by the maximum retry interval. If the calculated retry interval period
exceeds the maximum retry interval then the maximum retry interval is used
instead.
Hard bounce message
generation format
generation format
Specify whether hard bounce message generation is enabled or disabled. If it is
enabled, you can choose the format of the message. By default, bounce messages
generated use the DSN format (RFC 1894). You can select a custom notification
template to use for bounce messages. For more information, see the “Text
Resources” chapter.
enabled, you can choose the format of the message. By default, bounce messages
generated use the DSN format (RFC 1894). You can select a custom notification
template to use for bounce messages. For more information, see the “Text
Resources” chapter.
You can also choose whether or not to parse the DSN status field from the bounce
response. If you choose “Yes,” AsyncOS searches the bounce response for a
DSN status code (RFC 3436) and uses the code in the Status field of the delivery
status notification.
response. If you choose “Yes,” AsyncOS searches the bounce response for a
DSN status code (RFC 3436) and uses the code in the Status field of the delivery
status notification.
Send delay warning
messages
messages
Specify whether or not to send delay warnings. If enabled, specify the minimum
interval between messages as well as the maximum number of retries to send.
interval between messages as well as the maximum number of retries to send.
You can select a custom notification template to use for warning messages. For
more information, see the “Text Resources” chapter.
more information, see the “Text Resources” chapter.
Specify Recipient for
Bounces
Bounces
You can bounce messages to an alternate address rather than the default of the
Envelope Sender address.
Envelope Sender address.