This article applies to:

• MailMarshal Exchange 5.X

Symptoms:

• MailMarshal for Exchange Engine service shows high CPU usage.

Causes:

Badly formatted email causes the MMEengine to not function porperly when processing the e-mail.

Resolution:

Upgrading to the latest version of MailMarshal Exchange resolves the issue.

Workaround:

Rules can be created to send the badly formatted email via a template and store the original email in a folder for reference. This can be done by following the steps in the order presented:

1. Create a new Ruleset named Process Badly Formatted Mail.
2. Enable the When message is incoming Ruleset condition.
3. In the newly created Ruleset create a new standard rule named Allow valid mail with the rule description the same as the following:
   
   When a message arrives
   Where message is incoming
   Where message attachment is of type 'EXECUTABLE' or 'IMAGE' or 'VIDEO'' or 'SOUND' or 'DOCUMENT' or 'ARCHIVE' or 'ENCRYPTED' or 'DRAWING' or 'FONTS' or 'OTHER' or 'TNEF' or 'MBODY'
   Pass the message on to the next Ruleset.
   
4. Under the newly created rule create another standard rule named Block invalid mail with the rule description the same as the following:
   
   When a message arrives
   Where message is incoming
   Send a 'Bad Mail Template' notification message
   And move the message to 'Badly Formated Mail'

The Bad Mail Template can be created within the rule or under the E-mail Template node in the MailMarshal for Exchange Configurator using the following properties:

Template Name: Bad Mail Template
Return Path: {ReturnPath}
From:{Sender}
To:{Recipient}
Subject:{Subject}
Message Body: (Just input a single space from the space bar because this field cannot be null)

The Badly Formatted Mail can be created from within the rule or under the Folders node in the MailMarshal for Exchange Configurator.

Note: The Allow valid mail rule must be at the top of the Process Badly Formatted Mail Ruleset followed by the Block invalid mail rule to function properly.

This article was previously published as:

NETIQKB37988