MBF Knowledge Base

Declude will not run with SmarterMail 17x

Starting with SmarterMail Build 6911 (SmarterMail 17x), SmarterTools has changed their file format from xml files to json files which breaks Declude because Declude depends on a SM .xml file in order to start and run properly. For people who are upgrading from a previous version of SM to SM 17x, the fix in this article will work to resolve the issue with Declude not starting and running. However, if you install SmarterMail 17x as a new install (not an upgrade) you will not be able to use Declude on your server and currently there is no resolution for this.

If you have upgraded from a previous SmarterMail version to version 17x, you should still have the .xml file that Declude needs to run. The file in SM that Declude needs to run is the mailConfig.xml located in the SmarterMail Service folder.

If you have upgraded from a previous version of SM, you should still have this file, but it will be renamed to mailConfig.old.xml

We have verified with SmarterTools that you can rename it back to mailConfig.xml without any repercussions to SM 17x. To do this, simply right-click the file and rename it to mailConfig.xml.

Next. be sure to set the mailConfig.xml to read-only or SmarterMail will rename it again if you restart the SmarterMail service. To do this, right-click on the file and go to Properties. Put a check in the Read-Only box then click Apply > OK.

Go to your Windows Services area and restart the decludeproc service. To find your Windows Services area, do a search for Services.msc then click on it.

Lastly, go to your SM admin interface, disable Declude then click save. Now, re-enable Declude and click save.