This can happen if SpamAssassin is overloaded. To fix the problem you can increase the MaxChildren and/or MaxSpare settings in the "C:\ProgramData\JAM Software\spamdService\SpamAssassinServiceController.config". Increasing MaxChildren allows SpamAssassin to use more processes, which allows it to scan more emails in parallel. Increasing MaxSpare allows SpamAssassin to keep more idle processes on reserve to react faster to load peaks.

Direct link to the entry

Please stop the Application that uses the required port, or change its port.

To find out which process is using the required port, execute the following command in a PowerShell console:

• Get-Process -Id (Get-NetTCPConnection -LocalPort <port>).OwningProcess

Make sure that you replace <port> with the port that is used by the other application.

After the port is free, please restart the service of our software.

Direct link to the entry

During your maintenance period, they are located at Downloads/Updates -> Older versions in the customer area, if you are logged in to your customer account.

You should be able to find the installation files and keys of the two last major versions there.

Direct link to the entry

None of our applications depend on Java Spring or any other Java library and are thus not affected by this vulnerability.

All of our products are being developed in Delphi or C#. Although we use Spring4D(elphi) with some of the components, they are safe to use, because the reported vulnerability applies to Java Spring framework only.

This applies to all versions and editions of our applications (TreeSize, SpaceObServer, SpaceObServer WebAccess, HeavyLoad, SmartPOP2Exchange, Exchange Server Toolbox, SpamAssassin in a Box, SpamAssassin for Windows, SmartCallMonitor, SEPA-Transfer, ServerSentinel, and ShellBrowser). It is recommended to always use the latest available versions though to benefit from the latest patches, improvements, and features.

Direct link to the entry

1. Open a Windows Command Terminal (cmd.exe)
2. Enter this command:
• "c:\Program Files\JAM Software\SpamAssassin in a Box\LicenseManager.exe" /query
3. Enter your new license key and press Next

Direct link to the entry

All of our products are being developed in Delphi or C#. Although we use Log4Net with some of the components, they are safe to use, because the reported vulnerability applies to Log4J only.

None of our applications depend on Log4J or any other Java library and are thus not affected by this vulnerability.

This applies to all versions and editions of our applications (TreeSize, SpaceObServer, SpaceObServer WebAccess, HeavyLoad, SmartPOP2Exchange, Exchange Server Toolbox, SpamAssassin in a Box, SpamAssassin for Windows, SmartCallMonitor, SEPA-Transfer, ServerSentinel, and ShellBrowser). It is recommended to always use the latest available versions though to benefit from the latest patches, improvements, and features.

Direct link to the entry

Rebooting the system fixes this error. To prevent it entirely run the SpamAssassin service with administator privileges.

Direct link to the entry

In general adding whitelist entries in SpamAssassin can be done by creating a custom SpamAssassin cf

For whitelisting a single address you may use one of the following syntax

whitelist_from user@domain.tld

or

whitelist_from *@domain.tld

to whitelist all senders from a single domain.

We recommend to create a new cf-file at  C:\ProgramData\JAM Software\spamdService\sa-config

and name it e.g. xWhitelist.cf. That way your custom whitelist will be parsed quite late during startup, thus preventing that any of your settings gets overridden by another config file. Please note that you

have to manually restart SpamAssassin Daemon control service to apply your changes.

You'll find a lot of information on the official docs or SpamAssassin Wiki.

Direct link to the entry

Please run the setup of the licensed full version.
Please do not uninstall the previous installed trial version.
All settings will be retained.

Direct link to the entry

The SpamAssassin used checks SPF records. The default settings for SPF can be found in 25_SPF.cf or the corresponding scores in 50_scores.cf under "C:\ProgramData\JAM Software\spamdService\sa-rules\updates_spamassassin_org".

If you are using the Exchange Server Toolbox or SmartPOP2Exchange the best way to set your own scores is to use the built-in editor for creating custom SpamAssassin config files which you can find under Spam Options.

For more information about the options, see:
https://cwiki.apache.org/confluence/display/SPAMASSASSIN/

Alternatively, you can manually create your own .cf file in which you define your "rules", this should only come last alphabetically, since SpamAssassin will evaluate the cf files in numerical-alphabetical order. (For example XMySettings.cf).

Please note that you should add the SPF records to your MX record.

Direct link to the entry