Cisco Cisco Email Security Appliance C160 Mode D'Emploi
13-10
Cisco AsyncOS 8.0.1 for Email User Guide
Chapter 13 Anti-Spam
Defining Anti-Spam Policies
Related Topics
•
•
Configuration Examples: Actions for Positively Identified versus Suspected
Spam
Spam
The aggressive example tags only suspected spam messages, while dropping those messages that are
positively identified. Administrators and end-users can check the subject line of incoming message for
false positives, and an administrator can adjust, if necessary, the suspected spam threshold.
positively identified. Administrators and end-users can check the subject line of incoming message for
false positives, and an administrator can adjust, if necessary, the suspected spam threshold.
In the conservative example, positively identified and suspected spam is delivered with an altered
subject. Users can delete suspected and positively identified spam. This method is more conservative
than the first.
subject. Users can delete suspected and positively identified spam. This method is more conservative
than the first.
For a further discussion of aggressive and conservative policies in mail policies, see
in the Mail Policies chapter.
Unwanted Marketing Messages From Legitimate Sources
Both anti-spam scanning engines can distinguish between spam and unwanted marketing messages from
a legitimate source. Even though marketing messages are not considered spam, your organization or
end-users may not want to receive them. Like spam, you have the option to deliver, drop, quarantine, or
bounce unwanted marketing messages. You also have the option to tag unwanted marketing messages by
adding text to the message’s subject to identify it as marketing.
a legitimate source. Even though marketing messages are not considered spam, your organization or
end-users may not want to receive them. Like spam, you have the option to deliver, drop, quarantine, or
bounce unwanted marketing messages. You also have the option to tag unwanted marketing messages by
adding text to the message’s subject to identify it as marketing.
Enabling Different Anti-Spam Scanning Engines in Different Mail Policies:
Configuration Example
Configuration Example
When using the System Setup Wizard (or
systemsetup
command in the CLI), you are presented with
option to enable either Cisco Intelligent Multi-Scan or the Cisco Anti-Spam engine. You cannot enable
both during system setup, but after system setup is complete you can enable the anti-spam solution that
you didn’t choose, by using the Security Services menu.
both during system setup, but after system setup is complete you can enable the anti-spam solution that
you didn’t choose, by using the Security Services menu.
After the system is set up, you can configure the anti-spam scanning solution for incoming mail policies
via the Mail Policies > Incoming Mail Policies page. (Anti-spam scanning is typically disabled for
outgoing mail policies.) You can even disable anti-spam scanning for a policy.
via the Mail Policies > Incoming Mail Policies page. (Anti-spam scanning is typically disabled for
outgoing mail policies.) You can even disable anti-spam scanning for a policy.
Spam
Sample Actions
(Aggressive)
(Aggressive)
Sample Actions
(Conservative)
(Conservative)
Positively
Identified
Identified
Drop
•
Deliver with “
[Positive Spam]
” added
to the subject of messages, or
•
Quarantine
Suspected
Deliver with “
[Suspected Spam]
”
added to the subject of messages
Deliver with “
[Suspected Spam]
” added to
the subject of messages