Version 3.4.1.38: (07 Juni 2016)
•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".
Version 3.4.1.37: (20 April 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".
Version 3.4.1.36: (03 March 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".
Version 3.4.0.30: (06 June 2014)
•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".
Version 3.4.0.28: (04 April 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".
Version 3.4.0.26: (06 February 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".
Version 1.2.1: (16 February 2012)
•Bugfix: SPF checks are now performed without any warnings.
•Bugfix: Dissolving the temporary directory for Windows Vista and Windows 7 has been improved.
•A few minor fixes 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".
Version 1.2: (29 December 2011)
•Apache SpamAssassin Version 3.3.2 was integrated.
•Bugfix: Mail-SPF plugin is now loaded correctly.
•Bugfix: Razor is now able to create its home directory when necessary.
•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".
Version 1.1: (16 September 2010)
•Added Razor plugin, collaborative, spam detection and filtering network.
•Added RelayCountry plugin (exposes the countries that a mail was relayed from).
•Added SPF plugin, to allow prevention of source address spoofing.
•SpamAssassin for Windows is now installed via setup wizard.
•SpamAssassin for Windows will attempt to download the latest anti spam rules after installation now.
•Improved the application stability of the spamfilter.
•Replaced WinSpamC.exe for an improved variant (spamc.exe).
•Bugfix: SpamD may fail on a 64-bit environment when under heavy load (IPHLPAPI.DLL error).
•Bugfix: There was a problem where conflicting DLL versions may causing an application error.
•Several minor bug fixes and 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".
Version 1.0: (02 June 2010)
•First release of "SpamAssassin for Windows".
•Based on SpamAssassin Version 3.3.1.
•Integrated Perl runtime "ActivePerl".
•Provided components:
ospamassassin
osa-update
osa-learn
ospamd
ospamc (compiled in WinSpamC)
•Optional SpamAssassin modules that are not part of JAM Software binary build:
oRazor2 (collaborative filtering network)
oMail-SPF (DNS Sender Policy Framework)
oIP-Country (determines domain country codes)
oNet-Ident (required for the SpamD --auth-ident option (deprecated))
oIO-Socket-SSL (SSL support of SpamD/SpamC)
oIO-Socket-INET6 (IPv6 support for nameserver configuration)
•Known issues:
oIn some rare cases SpamD may terminate itself unexpectedly.
oSpamD has a memory leak which will force a periodical reboot of the application.
