IronPort - advanced configuration guide

Chapter 2 Configuring Routing and Delivery Features
Bounce Profile Parameters
OL-25137-01
When configuring a bounce profile, the following parameters control how conversational bounces are
handled per message:
Table 2-5 Bounce Profile Parameters
Maximum number of
retries
Maximum number of
seconds in queue
Initial number of
seconds to wait before
retrying a message
Maximum number of
seconds to wait before
retrying a message
Hard bounce message
generation format
Send delay warning
messages
Specify Recipient for
Bounces
Use DomainKeys
signing for bounce and
delay messages
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.
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).
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 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.
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 of the Cisco IronPort AsyncOS for Email Configuration
Guide.
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.
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.
You can select a custom notification template to use for warning messages. For
more information, see the “Text Resources” chapter of the Cisco IronPort
AsyncOS for Email Configuration Guide.
You can bounce messages to an alternate address rather than the default of the
Envelope Sender address.
You can select a DomainKeys profile to use for signing bounce and delay
messages. For information on DomainKeys, see DomainKeys and DKIM
Authentication: Overview, page 5-2.
Global Settings
Configure these settings via the Edit Global Settings link on the Bounce Profiles page or by editing the default
bounce profile via the bounceconfig command in the CLI.
Cisco IronPort AsyncOS 7.6 for Email Advanced Configuration Guide
2-37