End-User Quarantine Reports are email messages sent to email users when they have messages in the LibraCyber ESG Spam Quarantine. Notifications contain a list of quarantined spam or suspected spam for the user. Notifications also include a link for users to release their quarantined messages or whitelist blocked senders. Once enabled, notifications are sent according to the schedule that you specify. You can schedule up to four notifications per day for each user.
Spam notifications can provide a way for end-users to check and release quarantine without authentication, directly from their email client.
In case you require end-users to login into their quarantine via the web interface, with full access to all features, like an example, message body view, whitelist and blacklist management, and real-time personal email traffic, you must set up an authentication method (Local Database or LDAP supported, POP3 or IMAP).
To configure End User Quarantine Reports, you need users configured on LibraCyber ESG.
Select menu Admin Area->Authentication->User Management, and populate users:
- Manually, by adding them individually, using the email address as a username
- Text Import, by importing a list of users from a text file
- LDAP Import, by importing and syncing users with an LDAP server
- O365 Import, by importing and syncing users with the O365 connector
Once you have your user list populated, configure Quarantine Report to a single user, edit user properties select Quarantine Report, fill in the email address you want the digest to be sent to, and select a schedule, you can also specify the quarantine action you want to give to the user.
You can schedule (or remove schedule) the Quarantine Report to a block of users at once: simply select multiple users with checkboxes and press the Digest Report Schedule Button:
Quarantine Report has a standard layout that can be easily customized.
Select menu Admin Area->Appliance>Quarantine Settings and set your preferences:
NOTE: when importing and syncing from an LDAP Set all the above steps are automatically taken over by the import job, simplifying administrative tasks.