We have officially released the new SpamFilter ISP v2.5.1.441, it is available for download in the registered user area of our website. The major addition to this version is the support for an optional antivirus plugin to block email viruses.

This version also contains a small number of fixes and minor enhancements from the previous versions as follows below.

// New to VersionNumber = '2.5.1.441';
{TODO -cFix : Antivirus plugin-related dates were not decoded correctly in non-US locale date formats}
{TODO -cNew : Trial activation codes are requested via a built-in browser control within SpamFilter's GUI}

// New to VersionNumber = '2.5.0.435';
{TODO -cFix : Access Violations in "aa.bb.cc.dd - No Data Received" log entry. IP address was removed from logline}

// New to VersionNumber = '2.5.0.434';
{TODO -cNew : A current antivirus Activation Code is required to enable antivirus plugin}
{TODO -cNew : Added automatic hourly virus definition updates}
{TODO -cNew : Added custom response for SPF filter}
{TODO -cNew : Added custom response for antivirus filter}
{TODO -cNew : Added "aa.bb.cc.dd - No Data Received" log entry if remote server is disconnected without receiving any data from it (probes, port scanners, etc)}

// New to VersionNumber = '2.5.0.431';
{TODO -cFix : Removed trailing spaces in the "Found SPF Record" logfile entry }
{TODO -cNew : Implemented support for Norman's antivirus plugin}

// New to VersionNumber = '2.1.2.410';
{TODO -cFix : Force-delivery of quarantined emails with a NULL "Mail From" or "Mail To" would cause repeated exception entries in the log and creation of tmp files in queue directory}
{TODO -cNew : Added "SPF Test" button to SPF settings page to manually test user-defined criteria}
{TODO -cNew : Moved the retrieval of data in the quarantine view to a separate thread to improve performance for slow database links}

// New to VersionNumber = '2.1.2.406';
{TODO -cFix : When a recipient in an email with multiple recipients is whitelisted, the email is not supposed to be blocked. This was not working as expected in all cases}

// New to VersionNumber = '2.1.2.405';
{TODO -cFix : Changed the way hostnames and domains are checked for SPF records to better respect the SPF guidelines}

// New to VersionNumber = '2.1.2.404';
{TODO -cFix : The "Received by" header added by SpamFilter was not RFC compliant. Added the FQDN (host name) to the "by" section}

// New to VersionNumber = '2.1.2.403';
{TODO -cFix : DNS requests to a ping-able IP that is not running DNS were not causing SpamFilter to rotate DNS's to next available DNS server}

George,

Did you get that before?  I logged in no problem.

Dan

Roberto,
I sent you the order number.

I got the same error

/sfi-login.asp, line 356

 

Werner Schneider

Roberto,
Is there any way to "not quarantine" (just dump them) virus infected emails? Is there a parameter I am missing in the ini file?

It would be really great if we didn't have to keep the virus' infected emails in quarantine, ready for the silly end user to forward it to them selves even though the reason it is quarantined is in plain site on the webpage.

It doesn't do much good to block a virus, only to have it forwarded in the end anyway.

Luckly the AV on the pop server catches them.

g

Not right now, but we'll be adding that option shortly.