Cisco Cisco Email Security Appliance C170 Guia Do Utilizador

Página de 1211
 
7-9
AsyncOS 9.1.2 for Cisco Email Security Appliances User Guide
 
Chapter 7      Defining Which Hosts Are Allowed to Connect Using the Host Access Table (HAT)
  Defining Access Rules for Email Senders Using Mail Flow Policies
CONTINUE. The mapping in the HAT is ignored, and processing of the HAT continues. If the 
incoming connection matches a later entry that is not CONTINUE, that entry is used instead. The 
CONTINUE rule is used to facilitate the editing of the HAT in the GUI. For more information, see 
Related Topics
HAT Variable Syntax
 defines a set of variables that can also be used in conjunction with the custom SMTP and Rate 
Limiting banners defined for a mail flow policy. Variable names are case-insensitive. (That is, 
$group
 is 
equivalent to 
$Group
.)
Related Topics
Using HAT Variables
Note
These variables can be used with the 
smtp_banner_text
 and 
max_rcpts_per_hour_text 
advanced HAT 
parameters described in the “Configuring the Gateway to Receive Email” chapter. 
Using these variables, you could edit the custom SMTP banner response text for accepted connections 
in the $TRUSTED policy in the GUI:
Table 7-5
HAT Variable Syntax
Variable
Definition
$Group
Replaced by the name of the sender group that was matched in the HAT. If the sender 
group has no name, “None” is displayed.
$Hostname
Replaced by the remote hostname if and only if is has been validated by the appliance. 
If the reverse DNS lookup of the IP address is successful but returns no hostname, then 
“None” is displayed. If the reverse DNS lookup fails (for example, if the DNS server 
cannot be reached, or no DNS server has been configured) then “Unknown” is 
displayed.
$OrgID
Replaced by the SenderBase Organization ID (an integer value).
If the appliance cannot obtain a SenderBase Organization ID, or if the SenderBase 
Reputation Service did not return a value, “None” is displayed.
$RemoteIP
Replaced by the IP address of the remote client. 
$HATEntry
Replaced by the entry in the HAT that the remote client matched.