This article contains information on configuring Attachment Block on Size policies, considerations for file size restrictions, handling compressed files, and steps for setting up and managing these policies in the Mimecast Administration Console.
Considerations
Consider the following before getting started:
- End users cannot release the attachments, as they are placed in the administration on-hold queue. Administrators can release attachments via the Administration Console. See the Releasing Emails and Attachments page for further details.
- Policies with individual file size restrictions are considered first, followed by the cumulative limits. For example, if an Attachment Hold on Size policy is set to block attachments over 10MB, and an Attachment Block on Size policy is configured to block attachments over 15MB, the following happens if a message is received with one attachment of 11MB and the second 5MB in size.
- The 11MB attachment exceeds the limit in the Attachment Hold on Size policy and is sent to the administration On Hold queue.
- The 5MB attachment is unaffected by the Attachment Hold on Size policy.
- The combined size of the two attachments (16MB) exceeds the limit in the Block on Size policy, so all attachments are blocked.
This behavior is outlined in the notification generated when the policies are applied. This is dependent on your configured notification settings. For example:
| Action Taken | Reason |
|---|---|
| Stripped and Linked | Contributes to exceed size policy of 10485760 |
| Stripped (Blocked) | Exceeds size policy of 15728640 |
- For cumulative stripping, there is a minimum file size of 50kB before an attachment is stripped. For example, if a policy is set to block attachments over 10MB, and a message with five attachments with a cumulative size over 10MB is received, the policy is triggered and all attachments are removed.
- With compressed files (e.g. .ZIP, RAR, .7Z) the policy considers the unpacked size of a compressed file rather than the compressed size. For example, if a policy is set to block attachments over 10MB, and a .ZIP file is 4.5MB compressed but over 10MB when unpacked, the policy is triggered and the attachment is removed.
Configuring Attachment Block on Size Policies
To configure an Attachment Block on Size policy:
- Log in to the Mimecast Administration Console.
- Select the Gateway | Policies | Gateway Policies menu item.
- Click on Attachment Block on Size.
- Either select the:
-
- Policy to be changed.
- New Policy button to create a policy.
- Complete the Options section as required:
| Field / Option | Description |
|---|---|
| Policy Narrative | Provide a description of the policy to allow you to easily identify it in the future. |
| Maximum Attachment Size (KB) | Specify a value in kilobytes for the maximum file size of all attachments in a message. |
- Complete the Emails From and Emails To sections as required:
| Field / Option | Description |
|---|---|
| Addresses Based On | Specify the email address characteristics on which the policy is based. This option is only available in the "Emails From" section. The options are:
|
| Applies From / To | Specify the Sender characteristics that the policy is based on. For multiple policies, you should apply them from the most to the least specific. The options are:
|
- Complete the Validity section as required:
| Field / Option | Description |
|---|---|
| Enable / Disable | Use this to enable (default) or disable a policy. If a date range has been specified, the policy will automatically be disabled when the end of the configured date range is reached. |
| Set Policy as Perpetual | If the policy's date range has no end date, this field displays "Always On" meaning that the policy never expires. |
| Date Range | Use this field to specify a start and/or end date for the policy. If the "Eternal" option is selected, no date is required. |
| Policy Override | This overrides the default order in which policies are applied. If there are multiple applicable policies, this policy is applied first unless more specific policies of the same type are configured with an override. |
| Bi-Directional | If selected, the policy is applied when the policy's recipient is the sender, and the sender is the recipient. |
| Source IP Ranges (n.n.n.n/x) | Enter any required Source IP Ranges for the policy. These only apply if the source IP address used to transmit the message data falls inside or matches the range(s) configured. IP ranges should be entered in CIDR notation. |
- Click on the Save and Exit button.
Comments
Please sign in to leave a comment.