What's new in SpamAssassin in a Box 2.7.0.38
Oct 24, 2023
- The service no longer needs to be stopped before making changes to the configuration file now no longer needs to be terminated.
- The demo can now be converted to the full version key to convert the demo to the full version. A new installation is no longer necessary.
- A problem that caused the SpamAssassin in a Box service to stop responding under certain circumstances has been fixed.
New in SpamAssassin in a Box 2.6.0.36 (Mar 27, 2023)
- New version of SpamAssassin v4.0.
- Support for Windows Server 2022 (64-bit) has been added.
- Support for Windows 11 (64-bit) was added.
- Windows Server 2008 R2 is no longer supported.
- Windows 7 is no longer supported.
- Shortcircuit rules "USER_IN_WHITELIST" has been replaced with "USER_IN_WELCOMELIST" and "USER_IN_DEF_WHITELIST" has been replaced with "USER_IN_DEF_WELCOMELIST".
- Shortcircuit rules "USER_IN_BLACKLIST" has been replaced by "USER_IN_BLOCKLIST" and "USER_IN_BLACKLIST_TO" has been replaced by "USER_IN_BLOCKLIST_TO".
- A problem with restarting the SpamD process has been fixed.
New in SpamAssassin in a Box 2.5.1 (Mar 22, 2022)
- Added new options to configure SSL: Ssl, SslKey, SslCertificate.
- Fixed a problem in DNS whitelisting and blacklisting.
- An error when stopping the SpamD process was fixed.
- An error when changing the ListenIP or ListenPort settings was fixed.
- Changed compatibilities:
- SmartPOP2Exchange now requires .NET Framework 4.8.
New in SpamAssassin in a Box 2.4.0 (Apr 2, 2020)
- The system service was completely revised.
- 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.
New in SpamAssassin in a Box 2.3.0 (Feb 19, 2019)
- New Apache SpamAssassin Version 3.4.2
- OSa-update now uses SHA-256 and SHA-512 hashing for verification.
- OCorrupted HTML-E-Mails do not crash the service anymore.
- OSeveral new Plugins, Mail::SpamAssassin::Plugin::HashBL and Mail::SpamAssassin::Plugin::Phishing.
- OMore 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.
New in SpamAssassin in a Box 2.2 (Feb 19, 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.
New in SpamAssassin in a Box 2.2.1 (Jul 6, 2016)
- An 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.
New in SpamAssassin in a Box 2.2.0 (Jul 6, 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.
New in SpamAssassin in a Box 2.1.1 (Mar 12, 2015)
- 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.
New in SpamAssassin in a Box 2.1 (Jun 20, 2014)
- 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.
New in SpamAssassin in a Box 2.0 (Mar 29, 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
New in SpamAssassin in a Box 1.1.1 (Jun 27, 2012)
- The spam reports generated by SpamAssassin in a Box are now compatible to hMailServer.
- Mails that have been parsed by SpamAssassin are now correctly displayed in mail clients like Windows Live Mail.
- When starting up, the service now checks if the required ports for the Razor module are open.
- Numerous further improvements and a few minor bug fixes have been incorporated.
New in SpamAssassin in a Box 1.1 (May 31, 2012)
- SpamAssassin for Windows 1.2.1 (contains Apache SpamAssassin 3.3.2) has been integrated. Please refer to the following sites for more information:
- The service now adapts to the CPU usage: if this value is too high, the SpamAssassin daemon will not reboot.
- The automatic update of SpamAssassin rules has been improved.
- Setup will now add exceptions for SpamAssassin and SpamD at the Windows firewall.
- Improved the Windows Event Log functionality.
- Numerous further improvements and a few minor bug fixes have been incorporated.