Magicspam locking MailEnable files

[Bradley]

We've recently had a support call with mail enable to troubleshoot why creating, enabling and disabling domains were causing issues.

It turns out that magicspam.dll, when active causes an issue with domain management. It's as if it locks Mailenable files and it cannot write to it.

when they renamed the magicspam.dll file, we were able to manage domains again.

Is there perhaps an update or a fix to magicspam that can prevent this from happening? We've disabled magic spam on our servers for now so that we can create new accounts, but that leaves our mail server open to spam. Could you please get back to us as we need urgent spam protection.

We are experiencing this issue on 2 of our mailservers running mailenable and magic spam.

[magicspam]

Hello Bardley,

Thank you for contacting us.

Based on our understanding, you are not able to create, enable or disable domains through the MailEnable MagicSpam Console due to MagicSpam locking MailEnable files. We have replicated the reported issue and have identified the cause of the issue to be the 'Local SMTP sender addresses must authenticate' policy.

As a temporary workaround to reestablish MagicSpam protection, please follow these instructions:

1. Revert any changes to MagicSpam files (e.g. magicspam.dll)
2. Set 'Local SMTP sender addresses must authenticate' policy to OFF

   Code: Select all

   Anti-Spam >> Spam Policies

3. Restart MailEnable SMTP Connector Service (MESMTPC)

   Code: Select all

   MailEnable Management Console >> Servers >> localhost >> Services and Connectors
       SMTP (Right-Click) >> Stop
       SMTP (Right-Click) >> Start
   

We have informed the development to implement a permanent solution which will be included in the next release of MagicSpam for MailEnable which will be available in the next two weeks.

Please let us know if you have any other questions.

-- MagicSpam Support Team --