Worms are removed but not purged in Forefront Security for Exchange Server when you create a custom worm purge list and set the MaxCompressedFileInfections option to zero

Article translations Article translations
Article ID: 961936 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

Consider the following scenario:
  • In Microsoft Forefront Security for Exchange Server, you create a custom worm purge list as described in the following Microsoft Web site:
    http://technet.microsoft.com/en-us/library/bb795079.aspx
  • In General Options, the Max Container File Infections option is set to zero (0). This means the value of the following registry entry is set to 0:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Forefront Server Security\Exchange Server\MaxCompressedFileInfections
In this scenario, you notice that worms are removed, but the messages are not purged as expected.

RESOLUTION

To resolve the problem, set the Max Container File Infections value to a number instead of 0. Or, install Forefront Security for Exchange Server with Service Pack 2 (SP2)

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
960465 Description of Forefront Security for Exchange Server with Service Pack 2

Properties

Article ID: 961936 - Last Review: July 1, 2009 - Revision: 1.0
APPLIES TO
  • Microsoft Forefront Security for Exchange Server Service Pack 1, when used with:
    • Microsoft Forefront Security for Exchange Server
  • Microsoft Forefront Security for Exchange Server
Keywords: 
kbqfe kbprb kbexpertiseinter kbsurveynew KB961936

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com