Why are attachments not being dropped by MIME type filter on ESA?

Available Languages

Download Options

PDF (4.3 KB)
View with Adobe Reader on a variety of devices

Updated:August 20, 2014

Document ID:118310

Bias-Free Language

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.

Question:

Attachments are not being dropped as expected as one of the following:

Message Filter using drop-attachments-by-mimetype.
Content Filter using Drop_Attachments_By_Mimetype_Action.

Answer:

The "Drop Attachments by MIME Type" action finds the attachment MIME type by examining the MIME header data. The common causes an attachment not being detected and dropped by MIME type is that there was a scan error on the message or 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

Revision History

Revision	Publish Date	Comments
1.0	20-Aug-2014	Initial Release

Contributed by Cisco Engineers

Jackie Fleming and Enrico Werner
Cisco TAC Engineers.