Cisco Cisco Content Security Management Appliance M1070 Mode D'Emploi
7-13
AsyncOS 8.2 for Cisco Content Security Management User Guide
Chapter 7 Managing the Spam Quarantine
Backing Up and Restoring the Safelist/Blocklist Database
To maintain a backup of the safelist/blocklist database, the Security Management appliance enables you
to save the database as a .csv file. The .csv file is maintained separately from the XML configuration file
that contains the appliance configuration settings. If you upgrade your appliance or run the System Setup
Wizard, first back up the safelist/blocklist database to the .csv file.
to save the database as a .csv file. The .csv file is maintained separately from the XML configuration file
that contains the appliance configuration settings. If you upgrade your appliance or run the System Setup
Wizard, first back up the safelist/blocklist database to the .csv file.
Note
You can edit the .csv file and then upload it to modify individual end users’ safelists and blocklists.
When you back up the database, the appliance saves the .csv file to the
/configuration
directory using
the following naming convention:
slbl-<serial number>-<timestamp>.csv
When you back up your Security Management appliance, you can choose whether or not to include the
Safelist/Blocklist database. See
Safelist/Blocklist database. See
.
Procedure
Step 1
On the Security Management appliance, choose Management Appliance > System Administration >
Configuration File.
Configuration File.
Step 2
Scroll down to the End-User Safelist/Blocklist Database (Spam Quarantine) section.
Step 3
Click Backup Now to back up the database to a .csv file.
Step 4
Click Select File to Restore to restore the database.
The appliance displays a list of backup files that are stored in the
/configuration
directory.
Step 5
Select the Safelist/Blocklist backup file that you want to restore, and click Restore.
Using End User Safelists and Blocklists
End users can create safelists to ensure that messages from specified senders are never treated as spam,
and they can use blocklists to ensure that messages from specified senders are always treated as spam.
For example, an end user might 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 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.
and they can use blocklists to ensure that messages from specified senders are always treated as spam.
For example, an end user might 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 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.
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.