Cisco Cisco Email Security Appliance C160 Mode D'Emploi
C H A P T E R
8-1
AsyncOS 9.1.2 for Cisco Email Security Appliances User Guide
8
Accepting or Rejecting Connections Based on
Domain Name or Recipient Address
Domain Name or Recipient Address
•
•
•
•
•
Overview of Accepting or Rejecting Connections Based on the
Recipient’s Address
Recipient’s Address
AsyncOS uses a Recipient Access Table (RAT) for each public listener to manage accept and reject
actions for recipient addresses. Recipient addresses include these:
actions for recipient addresses. Recipient addresses include these:
•
Domains
•
Email addresses
•
Groups of email addresses
The System Setup Wizard guides the administrator in configuring at least one public listener (with
default values) on the appliance. Configuring a public listener during setup involves specifying default
local domains or specific addresses to accept mail. These local domains or specific addresses are the first
entries in the RAT for that public listener.
default values) on the appliance. Configuring a public listener during setup involves specifying default
local domains or specific addresses to accept mail. These local domains or specific addresses are the first
entries in the RAT for that public listener.
For eac h public listener, the default entry, “All Other Recipients”, rejects email from all recipients. The
administrator defines all local domains for which the appliance accepts messages. Optionally, you can
also define specific users for whom the appliance will accept or reject messages. AsyncOS allows you
to define acceptable local domains and specific users using the Recipient Access Table (RAT).
administrator defines all local domains for which the appliance accepts messages. Optionally, you can
also define specific users for whom the appliance will accept or reject messages. AsyncOS allows you
to define acceptable local domains and specific users using the Recipient Access Table (RAT).
You might need to configure a listener to accept messages for multiple domains. For example, if your
organization uses the domain
organization uses the domain
currentcompanyname.com
and it previously used
oldcompanyname.com
,
then you might accept messages for both
currentcompanyname.com
and
oldcompanyname.com
. In this
case, include both local domains in the RAT for your public listener.
(Note: the Domain Map feature can map messages from one domain to another. See the Domain Map
feature section of the “Configuring Routing and Delivery Features” chapter.)
feature section of the “Configuring Routing and Delivery Features” chapter.)