Cisco Cisco Email Security Appliance C160 Mode D'Emploi
25-56
User Guide for AsyncOS 9.7 for Cisco Email Security Appliances
Chapter 25 Configuring Routing and Delivery Features
Set Email Delivery Parameters
Set Email Delivery Parameters
The
deliveryconfig
command sets parameters to be used when delivering email from the appliance.
The appliance accepts email using multiple mail protocols: SMTP and QMQP. However, all outgoing
email is delivered using SMTP, which is why the
email is delivered using SMTP, which is why the
deliveryconfig
command does not require that the
protocol be specified.
Note
Several of the features or commands described in this section will affect, or be affected by routing
precedence. Please see the “Assigning Network and IP Addresses” appendix for more information.
precedence. Please see the “Assigning Network and IP Addresses” appendix for more information.
Related Topics
•
•
•
•
Default Delivery IP Interface
By default, the system uses an IP interface or IP interface group for email delivery. Any currently
configured IP interface or IP interface group can be set. If no specific interface is identified, AsyncOS
will use the hostname associated with the default delivery interface in the
configured IP interface or IP interface group can be set. If no specific interface is identified, AsyncOS
will use the hostname associated with the default delivery interface in the
SMTP HELO
command when
communicating with recipient hosts. To configure IP interfaces, use the
interfaceconfig
command.
These are the rules for using Auto selection of email delivery interfaces:
•
If the remote email server is on the same subnet as one of the configured interfaces, then traffic will
go out on the matching interface.
go out on the matching interface.
•
When set to auto-select, static routes you have configured using
routeconfig
take effect.
•
Otherwise, the interface that is on the same subnet as the default gateway will be used. If all of the
IP addresses have an equivalent route to the destination, then the system uses the most efficient
interface available.
IP addresses have an equivalent route to the destination, then the system uses the most efficient
interface available.
Possible Delivery Feature
Caution
If you enable this feature, message delivery will not be reliable and may lead to loss of messages. Also,
your appliance will not be RFC 5321-compliant. For more information, see
your appliance will not be RFC 5321-compliant. For more information, see
.
When the Possible Delivery feature is enabled, AsyncOS treats any message that times-out after the body
of the message is delivered, but before recipient host acknowledges receipt of the message, as a “possible
delivery.” This functionality prevents recipients from receiving multiple copies of a message if
continuous errors at their recipient host prevent acknowledgment of receipt. AsyncOS logs this recipient
as a possible delivery in the mail logs and counts the message as completed.
of the message is delivered, but before recipient host acknowledges receipt of the message, as a “possible
delivery.” This functionality prevents recipients from receiving multiple copies of a message if
continuous errors at their recipient host prevent acknowledgment of receipt. AsyncOS logs this recipient
as a possible delivery in the mail logs and counts the message as completed.