Cisco Cisco Email Security Appliance C160 Mode D'Emploi

Select a bounce profile (bounce profiles created via the 

bounceconfig

 command in the CLI are available 

in the list, see 

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).

Specify an SMTP Authentication profile.

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 

Configure any optional SMTP Address Parsing, Advanced, and LDAP options (discussed in detail 
below).

Submit and commit your changes.

To access the SMTP address parsing options, expand the section by clicking on SMTP Address Parsing 
in the listing.

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: <joe@example.com>”.

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.