SpamAssassin for Windows Changelog

• Bugfix: A critical error in DNS-based spam tests (i.e. blacklists) that caused a drop in the spam detection rate has been fixed. All external blacklists are now queried again.
• Known issue: The installation path and arguments added to the command prompt must only contain ASCII characters.
• Known issue: Due to a memory leak in the SpamAssassin Daemon (SpamD), a periodical reboot of the process is required. For professional use we recommend our service-based solution "SpamAssassin in a Box".

07 June 2016

• Bugfix: SpamD used to display warnings on startup. This did not affect its operation. The cause has been found and fixed.
• Bugfix: Previously missing modules of the SPF plugin have been added.
• Bugfix: The executables can now be launched from any directory on all operating system environments.
• Bugfix: The module File::Temp was missing and has now been added.
• Known issue: The installation path and arguments added to the command prompt must only contain ASCII characters.
• Known issue: Due to a memory leak in the SpamAssassin Daemon (SpamD), a periodical reboot of the process is required. For professional use we recommend our service-based solution "SpamAssassin in a Box".

20 April 2016

• Apache SpamAssassin version 3.4.1 has been integrated.
• ActivePerl 5.8 has been replaced by Strawberry Perl 5.22.
• Native 64 bit support has been integrated.
• Support for Windows XP and Server 2003 has been dropped.
• A subfolder runtime, containing the Perl scripts sa-learn, sa-update, spamassassin, spamd, and their dependencies has been added.
• Known issue: The installation path and arguments added to the command prompt must only contain ASCII characters.
• Known issue: Due to a memory leak in the SpamAssassin Daemon (SpamD), a periodical reboot of the process is required. For professional use we recommend our service-based solution "SpamAssassin in a Box".

03 March 2016

• The "taint mode" has been disabled for the executable files. This mode could potentially cause the application to abort execution if there was a path specified.
• Solved: Under certain conditions the scan date mentioned in the spam report was wrong.
• Known issue: Due to a memory leak in the SpamAssassin Daemon (SpamD), a periodical reboot of the process is required. For professional use we recommend our service-based solution "SpamAssassin in a Box".

06 June 2014

•  Apache SpamAssassin version 3.4.0 has been integrated.
• The paths for rules and configuration files can now be adjusted globally in the "path.config" file.
• Some minor improvements have been incorporated.
• Known issue: Due to a memory leak in the SpamAssassin Daemon (SpamD), a periodical reboot of the process is required. For professional use we recommend our service-based solution "SpamAssassin in a Box".

04 April 2014

• The version number of "SpamAssassin for Windows" now corresponds to the version number of the Apache SpamAssassin project.
• Apache SpamAssassin version 3.4.0-RC5 ("release candidate" of the major version 3.4.0) has been integrated. For a complete list of changes, please click here.
• The batch script "trainbayes.bat" allowing quick and simple training of spam/ham mails in a specific folder has been added.
• Several minor improvements have been incorporated.
• Known issue: Due to a memory leak in the SpamAssassin Daemon (SpamD), a periodical reboot of the process is required. For professional use we recommend our service-based solution "SpamAssassin in a Box".

06 February 2014