Cisco Cisco Email Security Appliance C160 Mode D'Emploi
Chapter 8 Anti-Spam
8-276
Cisco IronPort AsyncOS 7.1 for Email Configuration Guide
OL-22158-02
Figure 8-9
Rules Updates Section of Security Services > IronPort
Anti-Spam Page: GUI
Anti-Spam Page: GUI
Configuring Per-Recipient Policies for Anti-Spam
The IronPort Anti-Spam and IronPort Intelligent Multi-Scan solutions process
email for incoming (and outgoing) mail based on policies (configuration options)
you configure using the Email Security Manager feature. IronPort Anti-Spam and
IronPort Intelligent Multi-Scan scan messages through their filtering modules for
classification. The classification, or verdict, is then returned for subsequent
delivery action. Four verdicts are possible: messages can be identified as not
spam, identified as a unwanted marketing email, positively identified as spam, or
suspected to be spam. Actions taken on messages positively identified as spam,
suspected to be spam, or identified as unwanted marketing messages include:
email for incoming (and outgoing) mail based on policies (configuration options)
you configure using the Email Security Manager feature. IronPort Anti-Spam and
IronPort Intelligent Multi-Scan scan messages through their filtering modules for
classification. The classification, or verdict, is then returned for subsequent
delivery action. Four verdicts are possible: messages can be identified as not
spam, identified as a unwanted marketing email, positively identified as spam, or
suspected to be spam. Actions taken on messages positively identified as spam,
suspected to be spam, or identified as unwanted marketing messages include:
•
Specifying a Positive or Suspected Spam threshold.
•
Choosing which overall action to take on unwanted marketing messages,
positively identified spam, or suspected spam messages: deliver, drop,
bounce, or quarantine.
positively identified spam, or suspected spam messages: deliver, drop,
bounce, or quarantine.
•
Archiving messages to an mbox-format log file. You must create a log to
enable archiving messages identified as spam. See
enable archiving messages identified as spam. See
.
•
Altering the subject header of messages identified as spam or marketing.
•
Sending messages to an alternate destination mailhost.
•
Adding a custom X-Header to messages.
•
Sending messages to an alternate envelope recipient address. (For example,
you could route messages identified as spam to an administrator’s mailbox for
subsequent examination.) In the case of a multi-recipient message, only a
single copy is sent to the alternate recipient.
you could route messages identified as spam to an administrator’s mailbox for
subsequent examination.) In the case of a multi-recipient message, only a
single copy is sent to the alternate recipient.