Cisco Cisco Email Security Appliance C190 Guía Del Usuario
5-10
Cisco AsyncOS 8.5.5 for Email Security User Guide
Chapter 5 Configuring the Gateway to Receive Email
Listening for Connection Requests by Creating a Listener via the GUI
Allow Partial Domains
If enabled, will allow partial domains. Partial domains can be no domain at
all, or a domain with no dots.
all, or a domain with no dots.
The following addresses are examples of partial domains:
•
foo
•
foo@
•
foo@bar
This option must be enabled in order for the Default Domain feature to work
properly.
properly.
Add Default Domain: A default
domain to use for email addresses without
a fully qualified domain name. This option is disabled unless Allow Partial
Domains is enabled in SMTP Address Parsing options (see
Domains is enabled in SMTP Address Parsing options (see
). This
affects how a listener modifies email that it relays by adding the “default
sender domain” to sender and recipient addresses that do not contain
fully-qualified domain names. (In other words, you can customize how a
listener handles “bare” addresses).
sender domain” to sender and recipient addresses that do not contain
fully-qualified domain names. (In other words, you can customize how a
listener handles “bare” addresses).
If you have a legacy system that sends email without adding (appending)
your company’s domain to the sender address, use this to add the default
sender domain. For example, a legacy system may automatically create
email that only enters the string “
your company’s domain to the sender address, use this to add the default
sender domain. For example, a legacy system may automatically create
email that only enters the string “
joe
” as the sender of the email. Changing
the default sender domain would append “
@yourdomain.com
” to “
joe
” to
create a fully-qualified sender name of
joe@yourdomain.com
.
Source Routing
Determines behavior if source routing is detected in the “MAIL FROM” and
“RCPT TO” addresses. Source routing is a special form of an email address
using multiple ‘@’ characters to specify routing (for example:
@one.dom@two.dom:joe@three.dom). If set to “reject,” the address will be
rejected. If “strip,” the source routing portion of the address will be deleted,
and the message will be injected normally.
“RCPT TO” addresses. Source routing is a special form of an email address
using multiple ‘@’ characters to specify routing (for example:
@one.dom@two.dom:joe@three.dom). If set to “reject,” the address will be
rejected. If “strip,” the source routing portion of the address will be deleted,
and the message will be injected normally.
Unknown Address
Literals
Literals
Determines behavior for when an address literal is received that the system
cannot handle. Currently, this is everything except for IPv4. Thus, for
example, for an IPv6 address literal, you can either reject it at the protocol
level, or accept it and immediately hard bounce it.
cannot handle. Currently, this is everything except for IPv4. Thus, for
example, for an IPv6 address literal, you can either reject it at the protocol
level, or accept it and immediately hard bounce it.
Recipient addresses containing literals will cause an immediate hard
bounce. Sender addresses may get delivered. If the message cannot be
delivered, then the hard bounce will hard bounce (double hard bounce).
bounce. Sender addresses may get delivered. If the message cannot be
delivered, then the hard bounce will hard bounce (double hard bounce).
In the case of reject, both sender and recipient addresses will be rejected
immediately at the protocol level.
immediately at the protocol level.
Reject These Characters
in User Names
in User Names
Usernames that include characters (such as % or !, for example) entered here
will be rejected.
will be rejected.
Setting
Description