Руководство Пользователя для Cisco Cisco Content Security Management Appliance M160
7-21
AsyncOS 9.5.2 for Cisco Content Security Management Appliances User Guide
Chapter 7 Spam Quarantine
Configuring Spam Management Features for End Users
•
•
Recipient Email Mailing List Aliases and Spam Notifications
Notifications can be sent to each Envelope Recipient that has quarantined email, including mailing lists
and other aliases. Each mailing list receives a single digest. If you send notifications to a mailing list, all
subscribers to the list will receive the notification. Users who belong to multiple email aliases, or who
belong to LDAP groups that receive notifications, or who use several email addresses, may receive
multiple spam notifications. The following table shows example situations in which users may receive
multiple notifications.
and other aliases. Each mailing list receives a single digest. If you send notifications to a mailing list, all
subscribers to the list will receive the notification. Users who belong to multiple email aliases, or who
belong to LDAP groups that receive notifications, or who use several email addresses, may receive
multiple spam notifications. The following table shows example situations in which users may receive
multiple notifications.
If you use LDAP authentication, you can choose not to send notifications to mailing list aliases. Or, if
you choose to send spam notifications to mailing list aliases, you can prevent some occurrences of
multiple notifications. See
you choose to send spam notifications to mailing list aliases, you can prevent some occurrences of
multiple notifications. See
Users who access the spam quarantine by clicking a link in a notification will not see quarantined
messages for any other aliases that the end-user may have, unless the appliance is using a spam
quarantine alias consolidation query for email notifications. If the notification was sent to a distribution
list that is expanded after processing by the appliance, then multiple recipients may have access to the
same quarantine for that list.
messages for any other aliases that the end-user may have, unless the appliance is using a spam
quarantine alias consolidation query for email notifications. If the notification was sent to a distribution
list that is expanded after processing by the appliance, then multiple recipients may have access to the
same quarantine for that list.
This means that all subscribers to a mailing list will receive the notification and can log in to the
quarantine to release or delete messages. In this case, end users visiting the quarantine to view messages
mentioned in a notification may find that those messages have already been deleted by other users.
quarantine to release or delete messages. In this case, end users visiting the quarantine to view messages
mentioned in a notification may find that those messages have already been deleted by other users.
Note
If you do not use LDAP and you do not want your end users to receive multiple email notifications,
consider disabling notifications and instead allow end users to access the quarantine directly and
authenticate via LDAP or POP/IMAP.
consider disabling notifications and instead allow end users to access the quarantine directly and
authenticate via LDAP or POP/IMAP.
Testing Notifications
You can test notifications by configuring a testing mail policy, and having spam quarantined for just a
single user. Then, configure the spam quarantine notification settings: Select the Enable Spam
Notification checkbox and do not select Enable End-User Quarantine Access. Then only the
administrator configured in the Deliver Bounced Messages To field is notified of new spam in the
quarantine.
single user. Then, configure the spam quarantine notification settings: Select the Enable Spam
Notification checkbox and do not select Enable End-User Quarantine Access. Then only the
administrator configured in the Deliver Bounced Messages To field is notified of new spam in the
quarantine.
Table 7-1
Notifications per Address/Alias
User
Email Addresses
Aliases
Notifications
Sam
sam@example.com
—
1
Mary
mary@example.com
dev@example.com
qa@example.com
pm@example.com
4
Joe
joe@example.com,
admin@example.com
admin@example.com
hr@example.com
3