Digests sets are email notifications that give the end user direct control over their personal hold queue. They do this by presenting them with a summary of emails that have been quarantined by a policy. Digests can be enabled for spam, attachment, or content policies by the administrator. Read the Using a Digest page for further details.
The first digest sent to the user includes all the messages currently on hold for that user. This is important to consider, if there already are emails in the hold queue before the digest is enabled. Administrators should educate users on how to work with digests, and consider clearing the hold queue, before enabling the digest.
- Provide control over which users will receive digest notifications, and how often these are sent out.
- Allow different users and groups to receive digests at different intervals, or none at all.
- Can also be configured to be sent only on specific days of the week.
- Reduce the load of support queries directed to the administrator, and help streamline email delivery.
- Allow the user can identify legitimate messages they wish to receive, or block future unwanted messages. By applying these actions correctly, the messages in the hold queue should reduce over time.
A digest notification is not sent to the user if there are no new emails to report on. Additionally the user is only notified about an email in the hold queue once. If the digest is deleted, they will have to either:
- Contact their administrator to release the message from the hold queue via the Administration Console.
- View their personal on hold queue by accessing Mimecast Personal Portal, Mimecast Mobile, or Mimecast for Outlook.
Messages remain in the hold queue until they are either:
- Expired: Messages are automatically expired at the end of the time period specified by Mimecast Support, if there has been no action against the help the message by the user or administrator. By default the time period is after 14 days, but may be adjusted if required. Following the message's expiration, it will still be available in the archive.
- Released: Either through the Mimecast Personal Portal, Mimecast for Outlook, or Administration Console.
- Deleted: Either through the Mimecast Personal Portal, or Mimecast for Outlook, or Administration Console (rejected). These messages are bounced, and removed from the queue.
- Rejected: Through the Administration Console. These messages are bounced, and removed from the queue.
What You'll Need
- An Administrator Console logon with access to the Services | Gateway | Policies menu item.
- A previously configured Digest Set definition.
Creating a Policy
To create a policy, follow the instructions in the Creating / Changing a Policy article, but using the following options:
|Field / Option||Description|
|Policy Narrative||Provide a description for the Policy to allow you to easily identify it in the future.|
|Select Digest Set||Select the required Digest Set definition for the policy.|
Preventing Emails / Digests to Distribution Lists
You may wish to prevent emails or digests being sent to external facing Distribution Lists. Policies can be implemented to use Active Directory Attributes to distinguish between user accounts and distribution lists. Some example attributes that customers have used include "Country", "HomeMDB", or "ObjectCategory". Administrators need to determine a suitable attribute based on their Active Directory configuration. This attribute needs to be configured in Mimecast, and synced before it can be used in the relevant policies.
|Prevent digests to DL's||Create a Digest Set policy using an attribute in the "To" field which specifically belongs to user accounts. Digests will then only be sent to users.|
|Prevent inbound emails to DL's||Create a Creating / Changing a Blocked Senders Policy and in the "To" field select an attribute which is specific to distribution lists. This would cause all emails to DL's to be rejected.|