Cisco Cisco Email Security Appliance X1070 ユーザーガイド
7-20
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)
Handling Messages from a Group of Senders in the Same Manner
Note
If anti-spam or anti-virus scanning is enabled globally in the HAT, messages are flagged for
anti-spam or anti-virus scanning as they are accepted by the appliance. If anti-spam or anti-virus
scanning is disabled after the message is accepted, the message will still be subject to scanning
when it leaves the work queue.
anti-spam or anti-virus scanning as they are accepted by the appliance. If anti-spam or anti-virus
scanning is disabled after the message is accepted, the message will still be subject to scanning
when it leaves the work queue.
Step 4
Submit and commit your changes.
Defining Default Values for Mail Flow Policies
Procedure
Step 1
Click Mail Policies > Mail Flow Policies.
Step 2
Choose the listener to edit in the Listener field.
Step 3
Click the Default Policy Parameters link below the configured mail flow policies.
Step 4
Define the default values that all mail flow policies for this listener use.
For more information on the properties, see
DMARC Feedback Reports
Enable sending of DMARC aggregate feedback reports.
For more information about DMARC aggregate feedback report, see
Note
DMARC specification requires the feedback report messages to
be DMARC compliant. Make sure that these messages are
DKIM signed or you must publish appropriate SPF records.
be DMARC compliant. Make sure that these messages are
DKIM signed or you must publish appropriate SPF records.
Untagged Bounces
Consider Untagged Bounces
to be Valid
to be Valid
Applies only if bounce verification tagging (discussed in the
“Configuring Routing and Delivery Features” chapter) is enabled. By
default, the appliance considers untagged bounces invalid and either
rejects the bounce or adds a custom header, depending on the Bounce
Verification settings. If you choose to consider untagged bounces to be
valid, the appliance accepts the bounce message.
“Configuring Routing and Delivery Features” chapter) is enabled. By
default, the appliance considers untagged bounces invalid and either
rejects the bounce or adds a custom header, depending on the Bounce
Verification settings. If you choose to consider untagged bounces to be
valid, the appliance accepts the bounce message.
Envelope Sender DNS Verification
See
Exception Table
Use Exception Table
Use the sender verification domain exception table. You can only have
one exception table, but you can enable it per mail flow policy. See
one exception table, but you can enable it per mail flow policy. See
for more information.
Table 7-8
Mail Flow Policy Parameters (continued)
Parameter
Description