PDF(4.5 KB) View with Adobe Reader on a variety of devices
Updated:August 20, 2014
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Attachments not being dropped as expected and one of the following:
Message Filter using drop-attachments-by-name Content Filter using Drop_Attachments_By_Name_Action.
The Drop Attachments by Name action finds the files name in one of two ways. First it checks the filename as declared on the MIME header data. The second method only happens with archives: the files in the archive are extracted so the filenames can be listed. If the attachment is an archive and the extracted content's total size is greater than the max scan size or exceeds the max scan depth, the filenames will not be obtained.
There also may have been a scan error on the message and it is possible that the detected MIME type is configured to be skipped. To find out the exact cause for a given message, search the mail logs using grep from the CLI. When you search on the MID, any scan issues will be reported on their own line. Here is an example:
Tue Aug 3 16:36:29 2004 Warning: MID 256, Message Scanning Problem: Continuation line seen before first header