Cisco Cisco Email Security Appliance C160 Mode D'Emploi
8-4
Cisco AsyncOS 9.1 for Email User Guide
Chapter 8 Accepting or Rejecting Connections Based on Domain Name or Recipient Address
Domains and Users
Defining Recipient Addresses
The RAT allows you to define a recipient or group of recipients. Recipients can be defined by full email
address, domain, partial domain, username, or IP address:
address, domain, partial domain, username, or IP address:
Note
When you add a domain to the Recipient Access Table in step 4 of the System Setup Wizard in the GUI
(see
(see
), you might want to consider adding a second entry to specify
subdomains. For example, if you type the domain
example.net
, you might also want to enter
.example.net
. The second entry ensures that mail destined for any subdomain of
example.net
will
match in the Recipient Access Table. Note that only specifying
.example.com
in the RAT will accept for
all subdomains of
.example.com
but will not accept mail for complete email address recipients without
a subdomain (for example joe@example.com).
Bypassing LDAP Accept for Special Recipients
If you configure LDAP acceptance queries, you may wish to bypass the acceptance query for certain
recipients. This feature can be useful if there are recipients for whom you receive email which you do
not want to be delayed or queued during LDAP queries, such as
recipients. This feature can be useful if there are recipients for whom you receive email which you do
not want to be delayed or queued during LDAP queries, such as
customercare@example.com
.
If you configure the recipient address to be rewritten in the work queue prior to the LDAP acceptance
query, (such as aliasing or using a domain map), the rewritten address will not bypass LDAP acceptance
queries. For example you use an alias table to map
query, (such as aliasing or using a domain map), the rewritten address will not bypass LDAP acceptance
queries. For example you use an alias table to map
customercare@example.com
to
bob@example.com
and
sue@example.com
. If you configure bypassing LDAP acceptance for
customercare@example.com
, an
LDAP acceptance query is still run for
bob@example.com
and
sue@example.com
after the aliasing takes
place.
To configure bypassing LDAP acceptance via the GUI, select Bypass LDAP Accept Queries for this
Recipient when you add or edit the RAT entry.
Recipient when you add or edit the RAT entry.
To configure bypassing LDAP acceptance queries via the CLI, answer yes to the following question
when you enter recipients using the
when you enter recipients using the
listenerconfig -> edit -> rcptaccess
command:
[IPv4 address]
Specific Internet Protocol version 4 (IPv4) address of the host.
Note that the IP address must be between the “
Note that the IP address must be between the “
[]
” characters.
[IPv6 address]
Specific Internet Protocol version 6 (IPv6) address of the host.
Note that the IP address must be between the “
Note that the IP address must be between the “
[]
” characters.
division.example.com
Fully-qualified domain name.
.partialhost
Everything within the “partialhost” domain.
user@domain
Complete email address.
user@
Anything with the given username.
user@[IP_address]
Username at a specific IPv4 or IPv6 address. Note that the IP
address must be between the “
address must be between the “
[]
” characters.
Note that “
user@
IP_address” (without the bracket characters) is
not a valid address. The system will append the brackets when it
receives the message to create a valid address, which could affect
whether a recipient is matched in the RAT.
receives the message to create a valid address, which could affect
whether a recipient is matched in the RAT.
Would you like to bypass LDAP ACCEPT for this entry? [Y]> y