Cisco Cisco Content Security Management Appliance M1070 Mode D'Emploi

Page de 390
 
7-10
AsyncOS 8.2 for Cisco Content Security Management User Guide
 
Chapter 7      Managing the Spam Quarantine
New Message Count (%new_message_count%): number of new messages since the user’s last 
login
Total Message Count (%total_message_count%): number of messages for the user in the end user 
quarantine
Days Until Message Expires (%days_until_expire%)
Quarantine URL (%quarantine_url%): URL to log in to the quarantine and view messages
Username (%username%)
New Message Table (%new_quarantine_messages%): list of new messages in the quarantine for 
the user
You can include these message variables in the message body by entering them directly in the text of the 
Message Body field, or you can place the cursor where you want the variable inserted and then click the 
name of the variable in the Message Variables list on the right.
Step 9
Select a message format (HTML, Text, or HTML/Text).
Step 10
Specify a bounce address. Bounced notifications are sent to this address.
Step 11
Optionally, you can consolidate messages sent to the same LDAP user at different addresses. 
Step 12
Set the notification schedule. You can configure the notifications to be sent once a month, once a week, 
or at specified times during the day (weekdays only or including weekends).
Step 13
Submit commit your changes.
Configuring and Managing 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. 
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.
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 
. 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 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 
documentation or online help for your Email Security appliance.