Cisco Cisco Email Security Appliance C190 Guía Del Usuario
8-5
User Guide for AsyncOS 9.8 for Cisco Email Security Appliances
Chapter 8 Accepting or Rejecting Connections Based on Domain Name or Recipient Address
Domains and Users
When you configure a RAT entry to bypass LDAP acceptance, be aware that the order of RAT entries
affects how recipient addresses are matched. The RAT matches the recipient address with the first RAT
entry that qualifies. For example, you have the following RAT entries: postmaster@ironport.com and
ironport.com. You configure the entry for postmaster@ironport.com to bypass LDAP acceptance
queries, and you configure the entry for ironport.com for ACCEPT. When you receive mail for
postmaster@ironport.com, the LDAP acceptance bypass will occur only if the entry for
postmaster@ironport.com is before the entry for ironport.com. If the entry for ironport.com is before the
postmaster@ironport.com entry, the RAT matches the recipient address to this entry and applies the
ACCEPT action.
affects how recipient addresses are matched. The RAT matches the recipient address with the first RAT
entry that qualifies. For example, you have the following RAT entries: postmaster@ironport.com and
ironport.com. You configure the entry for postmaster@ironport.com to bypass LDAP acceptance
queries, and you configure the entry for ironport.com for ACCEPT. When you receive mail for
postmaster@ironport.com, the LDAP acceptance bypass will occur only if the entry for
postmaster@ironport.com is before the entry for ironport.com. If the entry for ironport.com is before the
postmaster@ironport.com entry, the RAT matches the recipient address to this entry and applies the
ACCEPT action.
Bypassing Throttling for Special Recipients
For recipient entries, you can specify that the recipient bypasses throttling control mechanisms enabled
on the listener.
on the listener.
This feature is useful if there are certain recipients for whom you do not want to limit messages. For
example, many users will want to receive email for the address “
example, many users will want to receive email for the address “
postmaster@domain
” on a listener, even
if the sending domain is being throttled based on the receiving control defined in mail flow policies.
Specifying this recipient to bypass receiving control in a listener’s RAT allows the listener to receive
unlimited messages for the recipient “
Specifying this recipient to bypass receiving control in a listener’s RAT allows the listener to receive
unlimited messages for the recipient “
postmaster@domain
” while retaining mail flow policies for other
recipients in the same domain. Recipients will avoid being counted against the recipients-per-hour
counter maintained by the system if the sending domain is being limited.
counter maintained by the system if the sending domain is being limited.
To specify certain recipients to bypass receiving control via the GUI, select Yes for the “Bypass
Receiving Control” setting when adding or editing a RAT entry:
Receiving Control” setting when adding or editing a RAT entry:
To specify certain recipients to bypass receiving control via the CLI, answer yes to the following
question when you enter recipients using the
question when you enter recipients using the
listenerconfig > edit > rcptaccess
command:
Rearranging the Order of Domains and Users in the Recipient Access Table
Procedure
Step 1
Navigate to the Mail Policies > Recipient Access Table (RAT) page.
Step 2
Choose the listener to edit in the Overview for Listener field.
Step 3
Click Edit Order.
Step 4
Change the order by arranging the values in the Order column.
Step 5
Submit and commit your changes.
Exporting the Recipient Access Table to an External File
Procedure
Step 1
Navigate to the Mail Policies > Recipient Access Table (RAT) page.
Would you like to bypass receiving control for this entry? [N]> y