IronPort - advanced configuration guide

1-8
Cisco IronPort AsyncOS 7.6 for Email Advanced Configuration Guide
Chapter 1 Customizing Listeners
Step 5 Select a bounce profile (bounce profiles created via the bounceconfig command in the CLI are available
in the list, see Creating a New Bounce Profile, page 2-40).
Step 6 Select a disclaimer to attach above or below emails (disclaimers created via the Mail Policies > Text
Resources page or the textconfig command in the CLI are available in the list, see the “Text Resources”
chapter in the Cisco IronPort AsyncOS for Email Configuration Guide).
Step 7 Specify an SMTP Authentication profile.
Step 8 Specify a certificate for TLS connections to the listener (certificates added via the Network > Certificates
page or the certconfig command in the CLI are available in the list, see Encrypting SMTP
Conversations Using TLS, page 1-22).
Step 9 Configure any optional SMTP Address Parsing, Advanced, and LDAP options (discussed in detail
below).
Step 10 Submit and commit your changes.
SMTP Address Parsing Options
Strict Mode
To access the SMTP address parsing options, expand the section by clicking on SMTP Address Parsing
in the listing.
Figure 1-6 Listeners SMTP Address Parsing Options
SMTP address parsing controls how strict the AsyncOS address parser behaves for the SMTP “MAIL
FROM” and “RCPT TO” commands. SMTP address parsing has two modes: Strict and Loose as well as
several other parsing options (configured independently of the address parsing mode).
Selecting a parsing mode or type is deciding whether you want your appliance to strictly adhere to the
standards of RFC2821.
Strict mode tries to follow RFC 2821. In Strict mode, the address parser follows RFC 2821 rules
with the following exceptions/enhancements:
– Space is allowed after the colon, as in “MAIL FROM: ”.
– Underscores are allowed in the domain name.
– “MAIL FROM” and “RCPT TO” commands are case-insensitive.
– Periods are not treated specially (for example, RFC 2821 does not allow a username of “J.D.”).
Some of the additional options below may be enabled which technically would violate RFC 2821.
OL-25137-01