Cisco Cisco Content Security Management Appliance M160 ユーザーガイド
7-8
AsyncOS 9.0 for Cisco Content Security Management Appliances User Guide
Chapter 7 Spam Quarantine
Edit Spam Quarantine Page
Edit Spam Quarantine Page
•
•
•
•
•
Using Safelists and Blocklists to Control Email Delivery Based
on Sender
on Sender
Administrators and end users can use safelists and blocklists to help determine which messages are
spam. Safelists specify senders and domains that are never treated as spam. Blocklists specify senders
and domains that are always treated as spam.
spam. Safelists specify senders and domains that are never treated as spam. Blocklists specify senders
and domains that are always treated as spam.
You can allow end users (email users) to manage the safelist and blocklist for their own email accounts.
For example, an end user may receive email from a mailing list that no longer interests him. He may
decide to add this sender to his blocklist to prevent emails from the mailing list from being sent to his
inbox. On the other hand, end users may find that emails from specific senders are sent to their spam
quarantine when they do not want them to be treated as spam. To ensure that messages from these senders
are not quarantined, they may want to add the senders to their safelists.
For example, an end user may receive email from a mailing list that no longer interests him. He may
decide to add this sender to his blocklist to prevent emails from the mailing list from being sent to his
inbox. On the other hand, end users may find that emails from specific senders are sent to their spam
quarantine when they do not want them to be treated as spam. To ensure that messages from these senders
are not quarantined, they may want to add the senders to their safelists.
Changes that end users and administrators make are visible to and can be changed by either.
Related Topics
•
•
•
•
•
•
•
Message Processing of Safelists and Blocklists
A sender’s being on a safelist or blocklist does not prevent the appliance from scanning a message for
viruses or determining if the message meets the criteria for a content-related mail policy. Even if the
sender of a message is on the recipient’s safelist, the message may not be delivered to the end user
depending on other scanning settings and results.
viruses or determining if the message meets the criteria for a content-related mail policy. Even if the
sender of a message is on the recipient’s safelist, the message may not be delivered to the end user
depending on other scanning settings and results.
When you enable safelists and blocklists, the appliance scans the messages against the safelist/blocklist
database immediately before anti-spam scanning. If the appliance detects a sender or domain that
matches a safelist or blocklist entry, the message will be splintered if there are multiple recipients (and
the recipients have different safelist/blocklist settings). For example, a message is sent to both recipient
A and recipient B. Recipient A has safelisted the sender, whereas recipient B does not have an entry for
the sender in the safelist or the blocklist. In this case, the message may be split into two messages with
database immediately before anti-spam scanning. If the appliance detects a sender or domain that
matches a safelist or blocklist entry, the message will be splintered if there are multiple recipients (and
the recipients have different safelist/blocklist settings). For example, a message is sent to both recipient
A and recipient B. Recipient A has safelisted the sender, whereas recipient B does not have an entry for
the sender in the safelist or the blocklist. In this case, the message may be split into two messages with