Cisco Cisco Email Security Appliance C160 Betriebsanweisung
6-191
Cisco IronPort AsyncOS 7.1 for Email Configuration Guide
OL-22158-02
Chapter 6 Email Security Manager
Note
Content dictionaries, disclaimers, and notification templates must be created
before they can be referenced by content filters. For more information, see
before they can be referenced by content filters. For more information, see
Incoming vs. Outgoing Messages
Two policy tables are defined in the Email Security Manager: one table for
messages from sending hosts that are stipulated by HAT policies with the
“Accept” behavior, the other table for sending hosts qualified as having HAT
“Relay” behavior. The former table is the incoming policy table, the latter is the
outgoing policy table.
messages from sending hosts that are stipulated by HAT policies with the
“Accept” behavior, the other table for sending hosts qualified as having HAT
“Relay” behavior. The former table is the incoming policy table, the latter is the
outgoing policy table.
•
Incoming messages are messages received from connections that match an
ACCEPT HAT policy in any listener.
ACCEPT HAT policy in any listener.
•
Outgoing messages are messages from connections that match a RELAY HAT
policy in any listener. This includes any connection that was authenticated
with SMTP AUTH.
policy in any listener. This includes any connection that was authenticated
with SMTP AUTH.
Note
In certain installations, “internal” mail being routed through the IronPort
appliance will be considered outgoing, even if all the recipients are addressed to
internal addresses. For example, by default for IronPort C10/100 customers, the
system setup wizard will configure only one physical Ethernet port with one
listener for receiving inbound email and relaying outbound email.
appliance will be considered outgoing, even if all the recipients are addressed to
internal addresses. For example, by default for IronPort C10/100 customers, the
system setup wizard will configure only one physical Ethernet port with one
listener for receiving inbound email and relaying outbound email.
For many configurations, you can think of the incoming table as Public, while the
Outgoing table is Private, although both could be used by a single listener. The
policy table used on a particular message is not dependant on the direction of the
message, with respect to sender or recipient addresses, out to the internet or in to
an intranet.
Outgoing table is Private, although both could be used by a single listener. The
policy table used on a particular message is not dependant on the direction of the
message, with respect to sender or recipient addresses, out to the internet or in to
an intranet.
You manage these tables using the Mail Policies > Incoming Mail Policies or
Outgoing Mail Policies pages in the GUI, or the
Outgoing Mail Policies pages in the GUI, or the
policyconfig
command in the
CLI.