We don’t use marketing cookies. Functional cookies ensure a smooth performance of our website. If you continue to use our services, you agree to the use of cookies. Data protection at JAM OK

FAQs & Knowledge Base

Welcome to our Knowledge Base. Search or browse through the topics below to find answers to your questions.

Categories: SmartPOP2Exchange | Show all categories

The path to rules and/or config dir is invalid. Make sure you run the executable (spamd.exe, spamassassin.exe, ...) from their main directory instead of specifying an absolute path to run.

Most likely SpamAssassin is not able to find a valid rule set. Please run sa-update.bat to download the latest rules.

If you use SpamAssassin in conjunction with "Exchange Server Toolbox" or "SmartPOP2Exchange", the Configured Score in "Exchange Server Toolbox" or "SmartPOP2Exchange" Rule-Condition usually determines how a scanned email should be handled.

If you use "SpamAssassin in a Box" alone, proceed as follows:
The threshold can be configured in the configuration "C:\ProgramData\JAM Software\spamdService\sa-config". Please open the text file with an appropriate text editor and search for the following line:
# required_score 5.0
Remove the comment sign (#) in front of the line and adjust the score to the desired value. Please note that any changes in the configuration files in the configuration directory will require a restart of the SpamAssassin daemon in order to take effect.

In case the required ports are not open, SpamAssassin scans will take much more time - which may cause a timeout.

The integrated SpamAssassin uses DNS (target port 53, TCP and UDP) for blacklist (RBL) requests. You also need to allow requests to target port 2703 (TCP) for Razor2. Otherwise spam scans may last longer than a minute. Alternatively, you may disable Razor2:
- Create a CF file like "XMySettings.cf" (text files) and put "score RAZOR2_CHECK 0" in it.
- Put this file in "C:\ProgramData\JAM Software\spamdService\sa-config\"

To solve this problem, you must first stop the SpamAssassin service, possibly by deactivating the service in the Windows Service Control.
Then you have to move or rename the following files:

C:\ProgramData\JAM Software\spamdService\Service.config
C:\ProgramData\JAM Software\spamdService\SpamD.config

These are the old configuration files that cause a problem when converting to a new format.

In addition, the "SpamAssassinServiceController.config" file should be deleted as this was probably created with incorrect values.
This file will then be created again by SpamAssassin the next time it is started.

If you now restart the SpamAssassin service, it should work again without any problems.