SpamAssassin in a Box Changelog

• The system service was completely revised.
• The system service now writes the log to the Windows event log "SpamAssassin in a Box".
• Support for 32-bit operating systems has been discontinued.
• Stopping the SpamAssassin service could cause a timeout under certain circumstances. This is now fixed.
• An issue where the SpamAssassin service crashed has been fixed.

2 April 2020

• New Apache SpamAssassin Version 3.4.2
  • Sa-update now uses SHA-256 and SHA-512 hashing for verification.
  • Corrupted HTML-E-Mails do not crash the service anymore.
  • Several new Plugins, Mail::SpamAssassin::Plugin::HashBL and Mail::SpamAssassin::Plugin::Phishing.
  • More security issues have been fixed.
• Errors while loading the configuration file could cause the "SpamAssassin Daemon Controller" system service to crash. This has been fixed.

30 January 2019

• A critical error in the system service has been fixed: In some cases the spam detection stopped working. This is no longer the case.

07 November 2016

• A critical error in DNS-based spam tests (e.g. blacklists) that caused a drop in the spam detection rate has been fixed. All external blacklists are now queried again.

07 June 2016

• SpamAssassin for Windows 3.4.1 (includes Apache SpamAssassin 3.4.1) has been integrated.
• Please note: Support for Windows XP and Server 2003 has been dropped.
• More than one IP address can be specified as a ListenIP in file SpamD.config.
• The service considers open connections to clients. Periodic restarts of the SpamAssassin daemon are delayed accordingly.
• Proxy settings are respected in all cases.
• Several minor improvements and minor fixes have been incorporated.

02 May 2016

• For bayes and rules files SpamAssassin now uses the paths configured in the file "path.config" to access Bayes filter and rules files.
• Several minor improvements and minor fixes have been incorporated.

05 March 2015

• SpamAssassin for Windows 3.4.0.30 (includes Apache SpamAssassin 3.4.0) has been integrated.
• The CPU load of the SpamAssassin daemon was reduced significantly. This was achieved by using a set of native compiled anti spam rules ("Rule2XSBody" plugin).
• A problem that caused the service to stop itself sometimes, has been solved.
• Under certain conditions a wrong scan date was shown in the spam report. This problem has been solved.
• The bayes files are no more persisted in the user profile but in the %programdata% directory instead.
• On certain systems, the service didn't start automatically with the system. This problem was solved.
• The maximum size of the service log file (Service.log) can now be specified in the Service.config.
• Several minor improvements and minor fixes have been incorporated.

18 June 2014

Updated SpamAssassin version

• The integrated SpamAssassin was updated to version 3.4.0 (RC5).

New folder structure and XML file based configuration

• Configuration files, SpamAssassin rules, and log files are no longer written to the installation directory but to a dedicated application data directory
• XML-based files can now be used for configuration instead of the Windows registry.
• The service can now be configured via the "Service.config" file. Please refer to the "Configuration" topic for more information.
• The SpamAssassin daemon is now configured separately via the "SpamD.config" file. Please refer to the "Configuration" topic for more information.

Improved logging

• The log file (SpamD.log) of the SpamAssassin daemon is no longer reset at each restart of the daemon but each day instead.
• In addition to the EventLog, each message from the service is now also written to a separate text file "Service.log" that is located in the application data directory.

Numerous minor changes and improvements

• The batch script "trainbayes.bat" allowing quick and simple training of spam/ham mails in a specific folder has been added.
• The setup now queries for a contact address for users whose mails were identified as false positives.
• A problem has been solved which could lead to a handle leak of the service.
• The firewall rules are now deleted when uninstalling the application.
• A new copy protection was integrated. Please note that old installation keys are no longer valid. You will find your new installation keys in the customer area.
• Numerous further improvements and a few minor bug fixes have been incorporated.

24 March 2014