Print Page | Close Window

SpamFilter 4.5 beta available

Printed From: LogSat Software
Category: Spam Filter ISP
Forum Name: Announcements
Forum Description: Announcements for SpamFilter ISP and SpamFilter Enterprise
Printed Date: 20 February 2019 at 6:08am

Topic: SpamFilter 4.5 beta available
Posted By: LogSat
Subject: SpamFilter 4.5 beta available
Date Posted: 16 January 2012 at 2:05pm
We have just made available a beta for the new upcoming SpamFilter 5.0. Our major plans for SpamFilter were to completely redesign the internal SMTP engine and the management GUI.

The new SMTP engine provides more features (like TLS, and an easier upgrade to IPv6), and better performance by using fibers rather than threads. This upgrade has been completed, and we are pre-releasing it in a beta version of SpamFilter v4.5.

The new GUI is still a work in progress that will be released with SpamFilter 5.0. The new GUI will allow an easier management of SpamFilter's service under Windows 7 and non-console sessions under Windows 2003.

Please feel free to use this thread to provide us any feedback on this release.

Roberto Franceschetti" rel="nofollow - LogSat Software" rel="nofollow - Spam Filter ISP

Posted By: LogSat
Date Posted: 12 February 2012 at 10:45pm
An updated beta has been pre-released ( to address minor issues with and to add a new options. Release notes are as follows:

// New to VersionNumber = '';

{TODO -cFix : SpamFilter crashes when application minimized if running as a service (does not affect standalone mode) }

{TODO -cFix : Old pre-beta bug - the "Tag Spam in Subject and Deliver" option was not adding the spam tag in the Subject line }

{TODO -cFix : was not performign the IP-to-Country lookups correctly, idenifying as N/A most countries }

{TODO -cFix : was corrupting the display of the antivirus definition files timstamps on the "Antivirus" tab. This issue affected the GUI display only, not the A/V functionality }

{TODO -cNew Added option to add a [WHITELISTED] prefix in whitelisted emails (prefix is customizeabled via WhitelistTagPrefix parameter in SpamFilter.ini file)}

{TODO -cNew During the live view of the Activity Log, we are skipping the display of some lines of scrolling text in case of large concurrent connections or if the CPU is high, as to not needlessly overload the server with GUI updates. The logfile on disk will always contain the full log activity anyways}

Roberto Franceschetti" rel="nofollow - LogSat Software" rel="nofollow - Spam Filter ISP

Posted By: LogSat
Date Posted: 31 March 2012 at 11:37am
An updated beta has been pre-released ( The release notes are as follows:

// New to VersionNumber = '';
{TODO -cNew : Removed option SpoolQueueFilesToMemory from SpamFilter.ini to improve memory usage. Messages won't be spooled in RAM enymore as performance on disk was very similar and RAM usge much lower}
{TODO -cNew : Changed logging of SSL connection errors (usually due to client using older unsafe SSL v2) to be indicated as generic harmless errors rather than "exceptions"}
{TODO -cNew : Greatly improved the memory usage and lowered the CPU load when processing large emails}
{TODO -cNew : Added experimental support for SQL Azure by using a modified \SpamFilter\Database\MicrosoftSQL.sql script}
{TODO -cFix : Better detection of SQL Server databases, i.e. SQL Azure}
{TODO -cFix : Minor GUI font fixes in Database settings tab}
{TODO -cFix : If the SpamFilter.ini option DoNotQueueIfReadTimeout was set to false, it was also affecting the option QueueIfDestinationError400 by overriding it and setting it to false as well}
{TODO -cFix : Unusual circumstance - If an email is detected as spam, and if it was whitelisted, and it had multipe recipients, and one or more recipients are rejected by the deestination SMTP server (forcing SpamFilter to send a 550 as it's undeliverable to some recipients), if all this is true SpamFilter adds the original rejection noticed in the SMTP response that includes the list of undeliverable email addresses}
{TODO -cFix : When rejecting an email with mutliple recipients because some of the recipients are rejected by the destination SMTP server, SpamFilter was only listing the first rejected email in the rejection notice - the others were sent on different lines separated by <CRLF> sequences that some SMTP servers were not recognizing}
{TODO -cNew : Improved the debug view to see the complete SMTP transactions with selected remote locations, including timestamps and thread IDs}

// New to VersionNumber = '';
{TODO -cFix : The Euro symbol was substituted by a ? in some specific email encodings}
{TODO -cFix : Rare crash that contains the following events being logged last:  "Listen Exception occurred:" & "Warning - Error! Removing Listener threads"}

// New to VersionNumber = '';
{TODO -cNew : Added parameter EnableTLSSupport=1 in SpamFilter.ini file to enable/disable TLS support (enabled by default)}
{TODO -cFix : Same issue fixed in was affecting the email's Subject as well}
{TODO -cFix : SpamFilter could crash with high volume traffic when writing to the logfile/greylistforcedelivery text files}

// New to VersionNumber = '';
{TODO -cFix : If an email's headers and/or content are not RFC-comliant, especially in regards to 7bit/8bit char encodings (affecting accents) and the Content-Type and Content-Transfer-Encoding headers, SpamFilter was auto-fixing them. However we should not alter the original email's format for any reason, so this issue was fixed}

// New to VersionNumber = '';
{TODO -cFix : SSL connections were not working on the SSL port (if configured)}
{DONE -cFix : Corrupt attachments - Emails that had a <CRLF>. sequence were not replaced by <CRLF>.. following RFC rules}
{TODO -cFix : If a malformed email with 8bit char encodings (affecting mainly accented characters in other languages) was missing the Content-type header, SpamFilter was adding the header "Content-Type: text/plain; charset=us-ascii" as RFC requires that Content-Type if not indicated otherwise. However SpamFilter is not supposed to alter the original messages, so this was considered a bug}
{DONE -cFix : Incorrectly adding two similar "Received" headers when processing incoming emails}
{DONE -cFix : The "From:" header was being re-written if improperly formatted. As in the attachment issue above, SpamFilter is not supposed to alter the original email no matter what}
{DONE -cFix : If the activity logfile was being locked by an external process, SpamFilter could crash}

Roberto Franceschetti" rel="nofollow - LogSat Software" rel="nofollow - Spam Filter ISP

Posted By: LogSat
Date Posted: 23 June 2012 at 6:10pm
The release candidate of SpamFilter v4.5.0.30 is now available. The changes from the previous versions as are follows:

// New to VersionNumber = '';
{TODO -cNew : Re-added external madExcept exception handling to automate creation of reports for crashes and to automatically restart SpamFilter in case of failures. This was disabled during the beta period}
{TODO -cNew : Added logging for exceptions that could occur in the SMTP session before SpamFilter could process an email, as for example when a received line is over 16,384 characters long (RFC imposes a limit of 1,024 characters...)}

// New to VersionNumber = '';
{TODO -cNew : Added support for accented characters in keywords}

// New to VersionNumber = '';
{TODO -cFix : The recent memory optimizations prevented SpamFilter from searching for keywords the various extra "X-SF-" headers that SpamFilter adds to emails (assuming the option to scan email headers has been enabled) }
{TODO -cFix : The antivirus plugin caused SpamFilter to crash severely without even logging entries in the event log if attachments had specific filename formats}

// New to VersionNumber = '';
{TODO -cFix : If a 3rd party application placed an email for delivery in the SpamFilter\queue folder, instead of the 5 characters "<CR><LF>.<CR><LF>" end-of-email indicator, SpamFilter incorrectly sent only the last 3 characters ".<CR><LF>" . As this is not the correct end-of-email indicator, this would result in a timeout if the 3rd party email did not contain an extra <CR><LF> before the <CR><LF>.<CR><LF>}

// New to VersionNumber = '';
{TODO -cFix : If an SMTP server used the CHUNKING extension to send an email, the sequence <CR><LF>. (which is legitimate when using CHUNKING) was not replaced by <CR><LF>.. (with an extra dot) when forwarding the email to the destination SMTP server}
{TODO -cFix : Removed support for the CHUNKING extension to solve the issue above, as fixing the bug would require re-decoding every line nullifying the benefits of CHUNKING}
{TODO -cFix : A memory leak was likely present when using CHUNKING with large emails}
{TODO -cNew : Added better support for detecting SQL Azure databases}
{TODO -cFix : Improved detection of pre-existing database patches when reinstalling SpamFilter using an existing database}

Roberto Franceschetti" rel="nofollow - LogSat Software" rel="nofollow - Spam Filter ISP

Posted By: yapadu
Date Posted: 24 June 2012 at 6:38am
I have not yet tested the BETA's that have been coming out, but had a question about this new whitelisted feature.  Does it add the prefix to any email that is classified as whitelisted, or only messages that would have been stopped as spam?

If I get an email from my mother (who is whitelisted) but nothing about the specific message would have stopped it, does it still get the prefix added?

{TODO -cNew Added option to add a [WHITELISTED] prefix in whitelisted emails (prefix is customizeabled via WhitelistTagPrefix parameter in SpamFilter.ini file)}

I am a user of SF, not an employee. Use any advice offered at your own risk.

Posted By: BigRedN
Date Posted: 08 October 2012 at 8:30pm
I just tried 4.5.053 and the activity log window does not populate. The log file does update but there is no display. I also tired this version with AD Authentication, via LDAP, however it seems to be broken in this version. I received a "no connection to server" error, but nothing had changed except the spf exe, so I think there may be an issue. And when I revert the files back to the version it all started working again. Please let me know if you need a log file or spamfilter.ini.


Print Page | Close Window