Cisco Cisco Email Security Appliance C650 Mode D'Emploi
27-38
Cisco AsyncOS 8.0 for Email User Guide
Chapter 27 Quarantines
Using Safelists and Blocklists to Control Email Delivery Based on Sender
End User Tasks for Configuring Safelists and Blocklists
End users can create safelists to ensure that messages from certain senders are never treated as spam,
and they can use blocklists to ensure that messages from certain senders are always treated as spam. 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 getting sent to his inbox.
On the other hand, end users may find that emails from specific senders get sent to their Spam Quarantine
when they don’t want them to be treated as spam. To ensure mail from these senders are not quarantined,
they may want to add the senders to their safelists.
and they can use blocklists to ensure that messages from certain senders are always treated as spam. 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 getting sent to his inbox.
On the other hand, end users may find that emails from specific senders get sent to their Spam Quarantine
when they don’t want them to be treated as spam. To ensure mail from these senders are not quarantined,
they may want to add the senders to their safelists.
Note
Safelist/Blocklist settings are contingent on other settings configured by the system administrator.
To work with safelists and blocklists, end users must complete the following tasks:
•
Access safelists and blocklists. Depending on authentication settings, end users may need to log
into their Spam Quarantine accounts. For more information, see
into their Spam Quarantine accounts. For more information, see
•
Add safelist entries. Users add safelist entries from the Options menu or the list of quarantined
messages in Spam Quarantine. For more information, see
messages in Spam Quarantine. For more information, see
•
Add blocklist entries. Users add blocklist entries from the Options menu of the Spam Quarantine.
For more information, see
For more information, see
Accessing Safelists and Blocklists
To access safelists and blocklists, end users whose accounts are authenticated using LDAP or Mailbox
(IMAP/POP) authentication must log into their accounts on the Spam Quarantine. The end user must log
into their account even if they are accustomed to accessing their messages via a spam notification (which
usually doesn’t require authentication). If the end-user authentication is set to NONE, end users do not
need to log into their accounts to access safelist/blocklist settings.
(IMAP/POP) authentication must log into their accounts on the Spam Quarantine. The end user must log
into their account even if they are accustomed to accessing their messages via a spam notification (which
usually doesn’t require authentication). If the end-user authentication is set to NONE, end users do not
need to log into their accounts to access safelist/blocklist settings.
Syntax for Safelists and Blocklist Entries
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 safe and block lists at the same time. However, if the
end user adds a domain to a safelist, and the email address for a user of 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 will treat mail from george@example.com as spam.
end user adds a domain to a safelist, and the email address for a user of 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 will treat mail from george@example.com as spam.
End users cannot allow or block a range of sub-domains using the following syntax: .domain.com.
However, an end user can explicitly block a specific domain using the following syntax:
server.domain.com.
However, an end user can explicitly block a specific domain using the following syntax:
server.domain.com.
Adding Entries to Safelists
End users can add senders to safelists in two ways: