About Attachment Merging and Splitting
Attachment merging and splitting policies can be applied to any rule that routes messages to a connector with a final form of PDF Image, PDF Image + Text, or TIFF.
Merging
A merge policy can be applied only to messages with multiple attachments. For example, if the user sends a message that includes four file attachments, the server merges the four attachments into a single attachment, and then routes the message to the connector that delivers it to its final destination.
Splitting
A split policy is based on either a page count restriction or file size restriction. This ensures that all resulting attachments are in compliance with the policy.
-
Based on page count: A split policy based on page count dictates the maximum number of pages in an attachment. This policy is applied to individual attachments that do not comply with the policy. For example, if the page count policy does not permit an attachment with more than 10 pages and the user sends an attachment with 16 pages, the server "splits" the original attachment so that the first attachment includes pages 1 - 10, and the second attachment includes pages 11-16.
-
Based on file size: A split policy based on file size dictates the maximum size of an attachment. This policy is applied only if the message attachments do not comply with the policy, and only if the attachment includes multiple pages. For example, if the page size policy does not permit an attachment larger than 2MB and the user sends a multiple-page attachment that is 10MB, the server "splits" the original attachment into as many attachments as necessary so that all attachments comply with the policy.
When the server cannot enforce the file size policy, the message fails. A failure occurs when a page in an attachment is larger than the maximum file size permitted by the policy. For example, if the file size policy does not permit an attachment larger than 2MB but a single page attachment is 4MB, the server fails the message. Messages that fail because the server cannot enforce the file size policy appear in the History (General failures) folder.
See also
Configuring Attachment Merging Policy
Configuring Attachment Splitting Policy
Customizing Attachment FileName Templates