Cisco Cisco Email Security Appliance C160 Mode D'Emploi
29-6
Cisco AsyncOS 8.5 for Email User Guide
Chapter 29 Spam Quarantine
Using Safelists and Blocklists to Control Email Delivery Based on Sender
Doing so will help ensure that these types of messages display properly in the spam quarantine. However,
specifying a default encoding can cause messages in other character sets to display incorrectly. This
setting applies only to messages that do not specify the encoding in the message headers. Generally, you
would only set a default encoding if you expect the majority of your mail that falls into this category to
be of one specific encoding.
specifying a default encoding can cause messages in other character sets to display incorrectly. This
setting applies only to messages that do not specify the encoding in the message headers. Generally, you
would only set a default encoding if you expect the majority of your mail that falls into this category to
be of one specific encoding.
For example, if most quarantined messages that do not specify the character set encoding in the message
headers are in Japanese (ISO-2022-JP), you can set the encoding on the Scan Behavior page as Japanese
(ISO-2022-JP).
headers are in Japanese (ISO-2022-JP), you can set the encoding on the Scan Behavior page as Japanese
(ISO-2022-JP).
Procedure
Step 1
Click Security Services > Scan Behavior.
Step 2
Under Global Settings, click Edit Global Settings.
Step 3
From the Encoding to use when none is specified drop-down list, select the desired encoding type.
Step 4
Click Submit.
Step 5
Click Commit Changes.
Spam Quarantine Language
Each user selects a language in the spam quarantine from the Options menu at the top right of the
window.
window.
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.
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.