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.

Positively Identified versus Suspected Spam<br />

9-16<br />

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

Chapter 9 Anti-Spam<br />

Because Cisco <strong>IronPort</strong> Anti-Spam and Cisco <strong>IronPort</strong> Intelligent Multi-Scan make the distinction<br />

between positively identified and suspected spam (Positive and Suspect Spam Threshold, page 9-15),<br />

many users configure their systems in one of the following ways:<br />

Table 9-1 Common Example <strong>Configuration</strong>s of Positively Identified and Suspected Spam<br />

Spam<br />

Positively<br />

Identified<br />

Method 1 Actions<br />

(Aggressive)<br />

The first configuration method tags only suspected spam messages, while dropping those messages that<br />

are positively identified. Administrators and end-users can check the subject line of incoming message<br />

for false positives, and an administrator can adjust, if necessary, the suspected spam threshold.<br />

In the second configuration method, positively identified and suspected spam is delivered with an altered<br />

subject. Users can delete suspected and positively identified spam. This method is more conservative<br />

than the first.<br />

See Table 6-6 on page 6-29 for a further discussion of mixing aggressive and conservative policies on a<br />

per-recipient basis using the Email Security Manager feature.<br />

Unwanted Marketing Message Detection<br />

Method 2 Actions<br />

(Conservative)<br />

Drop Deliver with “[Positive Spam]” added to<br />

the subject of messages<br />

Suspected Deliver with “[Suspected Spam]”<br />

added to the subject of messages<br />

Cisco <strong>IronPort</strong> Anti-Spam and Cisco <strong>IronPort</strong> Intelligent Multi-Scan can distinguish between spam and<br />

unwanted marketing messages from a legitimate source. Even though marketing messages are not<br />

considered spam, your organization or end-users may not want to receive them. Like spam, you have the<br />

option to deliver, drop, quarantine, or bounce unwanted marketing message. You also have the option to<br />

tag unwanted marketing messages by adding text to the message’s subject to identify it as marketing.<br />

Headers Added by Cisco <strong>IronPort</strong> Anti-Spam and Intelligent Multi-Scan<br />

If Cisco <strong>IronPort</strong> Anti-Spam scanning or Intelligent Multi-Scan is enabled for a mail policy, each<br />

message that passes through that policy will have the following header added to the message:<br />

X-<strong>IronPort</strong>-Anti-Spam-Filtered: true<br />

A second header will also be inserted for each message filtered by Cisco <strong>IronPort</strong> Anti-Spam or<br />

Intelligent Multi-Scan. This header contains information that allows Cisco <strong>IronPort</strong> Support to identify<br />

the CASE rules and engine version used to scan the message:<br />

X-<strong>IronPort</strong>-Anti-Spam: result<br />

Deliver with “[Suspected Spam]” added to<br />

the subject of messages<br />

Cisco <strong>IronPort</strong> Intelligent Multi-Scan also adds headers from the third-party anti-spam scanning<br />

engines.<br />

OL-25136-01

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

Saved successfully!

Ooh no, something went wrong!