Cisco Cisco Content Security Management Appliance M160 Guia Do Utilizador
6-19
Cisco IronPort AsyncOS 7.2.0 for Security Management User Guide
OL-21768-01
Chapter 6 Managing the Cisco IronPort Spam Quarantine
Enabling the End User Safelist/Blocklist Feature
You can allow end users to create safelists and blocklists to better control which
email messages are treated as spam. Safelists allow a user to ensure that mail from
specified users and domains is never treated as spam. Blocklists ensure that mail
from other users and domains is always treated as spam. The safelists and
blocklists settings are configured from the Cisco IronPort Spam Quarantine, so
you must enable and configure the Cisco IronPort Spam Quarantine to use this
feature. When you enable the safelist/blocklist feature, each end user can maintain
a safelist and blocklist for his or her email account.
email messages are treated as spam. Safelists allow a user to ensure that mail from
specified users and domains is never treated as spam. Blocklists ensure that mail
from other users and domains is always treated as spam. The safelists and
blocklists settings are configured from the Cisco IronPort Spam Quarantine, so
you must enable and configure the Cisco IronPort Spam Quarantine to use this
feature. When you enable the safelist/blocklist feature, each end user can maintain
a safelist and blocklist for his or her email account.
Note
A safelist or blocklist setting does not prevent the Email Security appliance from
scanning a message for viruses or determining if the message meets the criteria
for a content-related mail policy. If a message is sent from a safelist member, it
might not be delivered to the end user depending on other scanning settings.
scanning a message for viruses or determining if the message meets the criteria
for a content-related mail policy. If a message is sent from a safelist member, it
might not be delivered to the end user depending on other scanning settings.
When a user adds an entry to a safelist or blocklist, the entry is stored in a database
on the Security Management appliance and periodically updated and
synchronized on all related Email Security appliances. For information about
synchronization, see
on the Security Management appliance and periodically updated and
synchronized on all related Email Security appliances. For information about
synchronization, see
. For information on backing up the database, see
.
The safelists and blocklists are created and maintained by end users. However, an
administrator enables the feature and configures delivery settings for email
messages that match entries in the blocklist. Because the safelists and blocklists
are related to the Cisco IronPort Spam Quarantine, delivery behavior is also
contingent on other anti-spam settings. A message might skip anti-spam scanning
based on the processing that occurs before the message reaches the Email Security
Manager in the email pipeline. For more information about message processing,
see “Understanding the Email Pipeline” in the Cisco IronPort AsyncOS for Email
User Guide.
administrator enables the feature and configures delivery settings for email
messages that match entries in the blocklist. Because the safelists and blocklists
are related to the Cisco IronPort Spam Quarantine, delivery behavior is also
contingent on other anti-spam settings. A message might skip anti-spam scanning
based on the processing that occurs before the message reaches the Email Security
Manager in the email pipeline. For more information about message processing,
see “Understanding the Email Pipeline” in the Cisco IronPort AsyncOS for Email
User Guide.
For example, if you configure the “Accept” mail flow policy in the HAT to skip
anti-spam scanning, then users who receive mail on that listener will not have
their safelist and blocklist settings applied to mail received on that listener.
Similarly, if you create a mailflow policy that skips anti-spam scanning for certain
message recipients, these recipients will not have their safelist and blocklist
settings applied.
anti-spam scanning, then users who receive mail on that listener will not have
their safelist and blocklist settings applied to mail received on that listener.
Similarly, if you create a mailflow policy that skips anti-spam scanning for certain
message recipients, these recipients will not have their safelist and blocklist
settings applied.