Skip to main content

LevelBlue Named Official Cybersecurity Advisor of the PGA of America. Learn more

LevelBlue Named Official Cybersecurity Advisor of the PGA of America. Learn more

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
PGA of America Partnership
Secure What's Next
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

ERRMSG: Faulting module SpamChecker.dll

Expand / Collapse


This article applies to:

  • MailMarshal (SEG)
  • MailMarshal ECM/MailMarshal Exchange 7.X

Symptoms:

  • Error: faulting module SpamChecker.dll
  • MailMarshal Engine stops or will not start

Causes:

  • This error indicates a problem with one or more of the "category script" XML files.
  • For a specific, older upgrade issue that could cause this message, see Q11704.

Resolution:

This issue will typically occur immediately after you make a change in a category script XML file. To correct the issue, revert the change.

If you made several changes or you are unsure what changes have been made:

  1. Remove any custom XML file inclusions from default XML files such as the SpamCensor or Zero Day files.
  2. Remove any custom rule conditions that use the rule condition "Where messages is categorized as..."
  3. Commit configuration and ensure that the engine can process messages.
  4. Add the conditions or file inclusions to the configuration one by one, commit configuration, restart the engine and check that the engine will process messages. If the engine stops, the last XML file you added is likely to be the cause.

 



To contact LevelBlue about this article or to request support:


Rate this Article:
     

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.