We have made available in the registered user area the pre-release version of the new SpamFilter v2.6.3.473.

There are no major additions for this version, except for bug fixes. If no problems are reported with this beta build, it will likely be released officially within a few days.

The changes from the last official release are as follows:

// New to VersionNumber = '2.6.3.473';
{TODO -cFix : 100% CPU usage with certain RegEx keywords caused by certain malformed MIME messages}
{TODO -cFix : SPF bug - mx tests where A records have multiple IPs would sometimes incorrectly fail }
{TODO -cFix : SPF bug introduced in build 456 caused some SPF test to pass even though the "A" identifier should have caused them to fail }
{TODO -cFix : New per-domain filter GUI grid was being reloaded while the user was interactively making changes to it}
{TODO -cFix : New per-domain filter can get out-of-sync with the local domains list}

// New to VersionNumber = '2.6.3.467';
{TODO -cNew : New tab allows to enable/disable any filter on a per-domain basis, allowing further customizations for your local domains}

// New to VersionNumber = '2.5.2.462';
{TODO -cFix : Logfile was not flushed to disk until SpamFilter terminated or the log rotated - bug was introduced in build 461}

// New to VersionNumber = '2.5.2.461';
{TODO -cNew : Added RealtimeDiskLogging option in SpamFilter.ini file to have log being flushed to disk with every entry}
{TODO -cNew : Added DoNotAddIPToHoneypot option to SpamFilter.ini file to prevent certain trusted IPs from being blacklisted by the honeypot filter}
{TODO -cNew : Changed the logging on screen performance to increase reliability and have a smoother scroll}

// New to VersionNumber = '2.5.2.459';
{TODO -cFix : SURBL Do Not Quarantine setting was saving, but the mail was still not being quarantined}

// New to VersionNumber = '2.5.2.458';
{TODO -cFix : Could save the SURBL Do Not Quarantine setting}
{TODO -cFix : Could not empty the SURBL list, the default multi.surbl.org list was re-added automatically}
{TODO -cFix : AutoWhiteList was not always case-insensitive}

It would have been much easier for us as well.. however there are too many customers who are *not* using a database, and would thus not be able to use the feature. Due to this, there's no plans for that option in the near future.

Having the list both in the databse and on the filesystem would create too many complications, sorry. As all local lists are now file based, we'll be keeping it that way for continuity.

An option we're eamining is to have some kind of sync utility so that if the lists are added to the database, they would be sync'd to the file-based lists. We'll be looking into it more in the near future.