Manual scans and Quick scans do not mark .eml files as "ExceedinglyNested" files in Forefront Security for SharePoint

This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
Microsoft Forefront Security for SharePoint does not detect .eml files as ExceedinglyNested during Manual scans and Quick scans. This is true even if the nested attachment number exceeds the value of the Max Nested Attachments setting in the Forefront Security for SharePoint General Option settings.

Note Typically, when a file exceeds the limit for the maximum nested documents that can appear in MSG, TNEF, MIME, and UUENCODE documents, the file is marked as ExceedinglyNested and is blocked or deleted by Forefront Security for SharePoint. This limit is determined by the Max Nested Attachments setting. The limit includes the sum of the nestings of all of the document types (MSG, TNEF, MIME, and UUENCODE). The default value is 30.
Resolution
To resolve this issue, install Forefront Security for SharePoint Service Pack 3 (SP3). For more information, click the following article number to view the article in the Microsoft Knowledge Base:
967995 Description of Forefront Security for SharePoint with Service Pack 3
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
ExceedinglyNest FSSP SP3
Properties

Article ID: 968989 - Last Review: 01/16/2015 03:08:43 - Revision: 2.0

  • Microsoft Forefront Security for SharePoint
  • Microsoft Forefront Security for SharePoint Service Pack 1
  • Microsoft Forefront Security for SharePoint Service Pack 2
  • kbnosurvey kbarchive kbexpertiseinter kbbug kbqfe kbsurveynew kbprb KB968989
Feedback