SpamAssassin in a Box logo

SpamAssassin in a Boxv2.2

Service-Based high performance spam filter

Changes in V2.2.1 (07.06.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.

 

Changes in V2.2 (02.05.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.

 

Changes in V2.1.1 (05.03.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.

 

Changes in V2.1 (18.06.2014)

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.

 

Changes in V2.0 (24.03.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.

 
 

Changes in V1.1.1 (18.06.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.

 

 

Changes in V1.1: (17.05.2012)

SpamAssassin for Windows 1.2.1 (contains Apache SpamAssassin 3.3.2) has been integrated.

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.

 

 

Version 1.0: (05.11.2010)

First release of SpamAssassin in a Box.

Based on SpamAssassin for Windows Version 1.1 (Apache SpamAssassin Version 3.3.1).

Provides SpamAssassin as a Windows service that can easily be controlled via Windows Service Control Manager.

Monitors the SpamAssassin daemon 'SpamD' for automatic restart in case of failure.

Periodically updates the SpamAssassin anti-spam rules.

SpamAssassin related actions (eg. updates, restarts, etc.) are directly logged into Windows Event Log

Properly shuts down SpamD by sending a signal instead of killing the process (which can cause temporary files to be left on the system).

To consider possible changes in SpamAssassin configuration and to prevent potential memory leaks, SpamAssassin in a Box periodically restarts the daemon.

SpamAssassin default rules plus several additional anti-spam rules included.

Fully configurable via the Windows registry.