IronPort - daily management guide - AsyncOS 7.6.1
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 4 Quarantines<br />
OL-25138-01<br />
Table 4-5 Synchronization for Safelist and Blocklist Settings<br />
Appliance Synchronization Time<br />
C650/C660/C670 30 minutes<br />
X1050/X1060/X1070 60 minutes<br />
M600/M660 120 minutes<br />
M1000/M1050/M1060 240 minutes<br />
Working with Safelists and Blocklists<br />
When you use a group of C-Series appliances without an M-Series appliance, you may need to<br />
synchronize the safelist/blocklist settings and database across machines.<br />
If you use the centralized <strong>management</strong> feature to configure multiple Cisco <strong>IronPort</strong> appliances, you can<br />
configure administrator settings using centralized <strong>management</strong>. If you do not use centralized<br />
<strong>management</strong>, you can manually verify that settings are consistent across machines.<br />
For more information about accessing the appliance using FTP see “Accessing the Appliance” in either<br />
the Cisco <strong>IronPort</strong> <strong>AsyncOS</strong> for Email Configuration Guide or the Cisco <strong>IronPort</strong> <strong>AsyncOS</strong> for Email<br />
Advanced Configuration Guide.<br />
Troubleshooting Safelists and Blocklists<br />
An end user maintains his or her own safelists and blocklists. Administrators can access an end user’s<br />
safelist or blocklist only by logging into the end user account with the user’s login and password. To<br />
troubleshoot issues with safelists and blocklists, you can view the log files or system alerts.<br />
When an email is blocked due to safelist/blocklist settings, the action is logged in the ISQ_logs or the<br />
antispam log files. Emails that are safelisted are marked as safelisted with an X-SLBL-Result-Safelist<br />
header. Emails that are blocklisted are marked as blocklisted with an X-SLBL-Result-Blocklist header.<br />
Alerts are sent out when the database is created, updated, or if there are errors in modifying the database<br />
or running the safelist/blocklist processes.<br />
For more information about alerts, see “System Administration” in the Cisco <strong>IronPort</strong> <strong>AsyncOS</strong> for<br />
Email Configuration Guide.<br />
For more information about log files, see Chapter 5, “Logging.”<br />
End User Tasks for Configuring Safelists and Blocklists<br />
End users can create safelists to ensure that messages from certain senders are never treated as spam,<br />
and they can use blocklists to ensure that messages from certain senders are always treated as spam. For<br />
example, an end user may receive email from a mailing list that no longer interests him. He may decide<br />
to add this sender to his blocklist to prevent emails from the mailing list from getting sent to his inbox.<br />
On the other hand, end users may find that emails from specific senders get sent to their Cisco <strong>IronPort</strong><br />
Spam Quarantine when they don’t want them to be treated as spam. To ensure mail from these senders<br />
are not quarantined, they may want to add the senders to their safelists.<br />
Note Safelist/Blocklist settings are contingent on other settings configured by the system administrator.<br />
To work with safelists and blocklists, end users must complete the following tasks:<br />
Cisco <strong>IronPort</strong> <strong>AsyncOS</strong> 7.6 for Email Daily Management Guide<br />
4-41