27.11.2012 Views

IronPort - Configuration Guide - AsyncOS 7.6.1

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 5 Configuring the Gateway to Receive Email<br />

HAT Variable Syntax<br />

Using HAT Variables<br />

OL-25136-01<br />

Table 5-3 HAT Mail Flow Policy Parameters (Continued)<br />

Parameter Description<br />

Envelope Sender DNS Verification<br />

Exception Table<br />

See Sender Verification, page 5-40.<br />

Use Exception Table Use the sender verification domain exception table. You can only have<br />

one exception table, but you can enable it per mail flow policy. See<br />

Sender Verification Exception Table, page 5-43 for more information.<br />

By default, these parameters are set to the following default values shown in Table 5-5 and Table 5-6 for<br />

each listener on the appliance.<br />

Note If anti-spam or anti-virus scanning is enabled globally in the HAT, messages are flagged for anti-spam<br />

or anti-virus scanning as they are accepted by the Cisco <strong>IronPort</strong> appliance. If anti-spam or anti-virus<br />

scanning is disabled after the message is accepted, the message will still be subject to scanning when it<br />

leaves the work queue.<br />

Table 5-4 defines a set of variables that can also be used in conjunction with the custom SMTP and Rate<br />

Limiting banners defined for a Mail Flow Policy. Variable names are case-insensitive. (That is, $group<br />

is equivalent to $Group.)<br />

Table 5-4 HAT Variable Syntax<br />

Variable Definition<br />

$Group Replaced by the name of the sender group that was matched in the HAT. If the sender<br />

group has no name, “None” is displayed.<br />

$Hostname Replaced by the remote hostname if and only if is has been validated by the Cisco<br />

<strong>IronPort</strong> appliance. If the reverse DNS lookup of the IP address is successful but<br />

returns no hostname, then “None” is displayed. If the reverse DNS lookup fails (for<br />

example, if the DNS server cannot be reached, or no DNS server has been configured)<br />

then “Unknown” is displayed.<br />

$OrgID Replaced by the SenderBase Organization ID (an integer value).<br />

If the Cisco <strong>IronPort</strong> appliance cannot obtain a SenderBase Organization ID, or if the<br />

SenderBase Reputation Service did not return a value, “None” is displayed.<br />

$RemoteIP Replaced by the IP address of the remote client.<br />

$HATEntry Replaced by the entry in the HAT that the remote client matched.<br />

Note These variables can be used with the smtp_banner_text and max_rcpts_per_hour_text advanced HAT<br />

parameters shown in Table 1-3 of the “Customizing Listeners” chapter in the Cisco <strong>IronPort</strong> <strong>AsyncOS</strong><br />

for Email Advanced <strong>Configuration</strong> <strong>Guide</strong>.<br />

Cisco <strong>IronPort</strong> <strong>AsyncOS</strong> 7.6 for Email <strong>Configuration</strong> <strong>Guide</strong><br />

5-13

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!