Руководство Пользователя для Cisco Cisco Content Security Management Appliance M160
Chapter 6 Managing the Cisco IronPort Spam Quarantine
6-24
Cisco IronPort AsyncOS 7.2.0 for Security Management User Guide
OL-21768-01
receive unwanted email from a mailing list. The user can add this sender to the
user’s blocklist to prevent email messages from the sender from being delivered.
On the other hand, an end user might find that email messages from a legitimate
sender are sent to the Cisco IronPort Spam Quarantine, but those email messages
should not be treated as spam. To prevent mail from that sender from being
quarantined, the user can add the sender to the user’s safelist.
user’s blocklist to prevent email messages from the sender from being delivered.
On the other hand, an end user might find that email messages from a legitimate
sender are sent to the Cisco IronPort Spam Quarantine, but those email messages
should not be treated as spam. To prevent mail from that sender from being
quarantined, the user can add the sender to the user’s safelist.
Note
Safelist/blocklist settings are contingent on other settings configured by the
system administrator. For example, a safelisted message may not be delivered if
it is determined to be virus positive, or if the administrator determines that the
content does not conform to company email policies.
system administrator. For example, a safelisted message may not be delivered if
it is determined to be virus positive, or if the administrator determines that the
content does not conform to company email policies.
Accessing Safelists and Blocklists
To access safelists and blocklists, end users whose accounts are authenticated
using LDAP or mailbox authentication (IMAP or POP) must log in to their
accounts on the Cisco IronPort Spam Quarantine. The end users must log in to
their accounts even if they are accustomed to accessing messages through a spam
notification (which typically does not require LDAP or mailbox authentication).
If the end user authentication is set to None, end users do not need to log in to
their accounts to access safelist/blocklist settings.
using LDAP or mailbox authentication (IMAP or POP) must log in to their
accounts on the Cisco IronPort Spam Quarantine. The end users must log in to
their accounts even if they are accustomed to accessing messages through a spam
notification (which typically does not require LDAP or mailbox authentication).
If the end user authentication is set to None, end users do not need to log in to
their accounts to access safelist/blocklist settings.
Adding Entries to Safelists and Blocklists
Entries can be added to safelists and blocklists using the following formats:
•
user@domain.com
•
server.domain.com
•
domain.com
End users cannot add a sender or domain to both their safelist and their blocklist
at the same time. However, if they add a domain to a safelist and a user in that
domain to the blocklist (or vice versa), the appliance applies both rules. For
example, if the end user adds example.com to the safelist, and adds
george@example.com to the blocklist, the appliance delivers all mail from
example.com without scanning for spam, but it treats mail from
george@example.com as spam.
at the same time. However, if they add a domain to a safelist and a user in that
domain to the blocklist (or vice versa), the appliance applies both rules. For
example, if the end user adds example.com to the safelist, and adds
george@example.com to the blocklist, the appliance delivers all mail from
example.com without scanning for spam, but it treats mail from
george@example.com as spam.