GFI MailSecurity 10 blocking Exchange 2003 Emails

Lg_msec_headLast Wednesday, one of our clients had a server STOP crash issue after a new Brooktrout driver was installed.   Since then, all mails started to get to the SMTP advance queue and then disappearing.   Well, actually, they did not disappear…   they actually ended up in the GFI MailSecurity FailedMails folder.

Removing and reinstalling MailSecurity made no difference so I had to contact the support team at GFI.    The initial engineers, whilst helpful, could only point me to an unreleased update that had the same symptoms (the mails going to the failedmail folder) but this made no difference.  

The case was escalated to a very helpful guy, Andrew, who connected in to the server and found the following:

Open Insink.txt from the ContentSecurityMailSecurityDebuglogs folder and look for the following entry:

YYYY-MM-DD,HH:MM:SS,XXX,1,”#000006b0″,”#000019e0″,“error  “,”msecsink”,”Scanning…FAILED [0x80040155]”
YYYY-MM-DD, HH:MM:SS,XXX,1,”#000006b0″,”#000019e0″,“error  “,”msecsink”,”Failed to scan mail, hr=0x80040155″


The important thing to note here is the part at the end, from “error “ onwards.

0x80040155 = Interface Not Registered

If installed on the Exchange server, you will see the same in OutSink.txt as well.

To resolve this issue you need to re-register the required interfaced, by doing the following:

  1. Open a command prompt and navigate to the WINDOWSSYSTEM32 folder.  
  2. Type “regsvr32 OLE32.dll” without the quotes
  3. Now navigate to the ContentSecurityMailSecurity folder and type “regsvr32 gfiscanmps.dll” again, without the quotes.
  4. From the services console, restart the GFI MailSecurity Scan Engine Service, the IIS Admin services and the Information Store service.

All should now start to function correctly.

  4 Replies to “GFI MailSecurity 10 blocking Exchange 2003 Emails”

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.