Cisco Cisco Email Security Appliance C170 Guia Do Utilizador
Chapter 2 Configuring Routing and Delivery Features
2-104
Cisco IronPort AsyncOS 7.1 for Email Advanced Configuration Guide
OL-22164-02
Directing Bounced Email
Bounced email is an inevitable part of any email delivery. Your IronPort appliance
is able to process bounced email in a number of highly configurable ways.
is able to process bounced email in a number of highly configurable ways.
Please note, this section describes how to control how your IronPort appliance
generates outgoing bounces (based on incoming mail). To control how your
IronPort appliance controls incoming bounces (based on outgoing mail) use
IronPort Bounce Verification (see
generates outgoing bounces (based on incoming mail). To control how your
IronPort appliance controls incoming bounces (based on outgoing mail) use
IronPort Bounce Verification (see
).
Handling Undeliverable Email
The IronPort AsyncOS operating system classifies undeliverable email, or
“bounced messages,” into the following categories:
“bounced messages,” into the following categories:
“Conversational” bounces:
The remote domain bounces the message during the initial SMTP conversation.
The remote domain bounces the message during the initial SMTP conversation.
Soft
bounces
bounces
A message that is temporarily undeliverable. For example, a user’s
mailbox may be full. These messages can be retried at a later time.
(e.g. An SMTP 4XX error code.)
mailbox may be full. These messages can be retried at a later time.
(e.g. An SMTP 4XX error code.)
Hard
bounces
bounces
A message that is permanently undeliverable. For example, the
user no longer exists for that domain. These messages will not be
retried. (e.g. An SMTP 5XX error code.)
user no longer exists for that domain. These messages will not be
retried. (e.g. An SMTP 5XX error code.)
“Delayed” (or “Non-conversational”) bounces:
The remote domain accepts the message for delivery, only to bounce it at a later
time.
The remote domain accepts the message for delivery, only to bounce it at a later
time.
Soft
bounces
bounces
A message that is temporarily undeliverable. For example, a user’s
mailbox may be full. These messages can be retried at a later time.
(e.g. An SMTP 4XX error code.)
mailbox may be full. These messages can be retried at a later time.
(e.g. An SMTP 4XX error code.)
Hard
bounces
bounces
A message that is permanently undeliverable. For example, the
user no longer exists for that domain. These messages will not be
retried. (e.g. An SMTP 5XX error code.)
user no longer exists for that domain. These messages will not be
retried. (e.g. An SMTP 5XX error code.)
You use the Bounce Profiles page on the Network menu in the GUI (or the
bounceconfig
command) to configure how IronPort AsyncOS handles hard and
soft conversational bounces for each listener you create. You create bounce
profiles and then apply profiles to each listener via the Network > Listeners page
profiles and then apply profiles to each listener via the Network > Listeners page