We have officially released the new SpamFilter ISP and SpamFilter Enterprise v4.7.6.301. This release is available for download in the registered user area of our website. A free Evaluation copy is also available for all other users. 

As always, this upgrade is free for all users with a current software maintenance.

The full list of changes since the latest official release (4.7.4.276) is as follows:

// New to VersionNumber = '4.7.6.301';
{TODO -cNew: Added SpamFilter.ini option RejectEmailsOverLineLength16384 - By default emails having a linve over 16834 characters in length are marked as spam (per RFC the max line length is 1,000 chars). Set this to 0 to accept them anyways"}

// New to VersionNumber = '4.7.6.300';
{TODO -cFix: Rolled back the behavior introduced in 4.7.6.294 due to a mis-interpretation of RFC 7208. The setting for MaxSPFLookupErrors in the SpamFilter.ini is no longer active}
{TODO -cNew: The SPF filter is unable to fallback to using TCP instead of UDP when TXT records in DNS lookups exceed the size allowed by UDP. In this case SpamFilter will skip the SPF check for the specific inbound email and log the event with "Received Truncated flag in DNS qTXT reply for"}

// New to VersionNumber = '4.7.6.298';
{TODO -cFix: If SpamFilter is configured with a quarantine database but the database server is offline when SpamFilter is started, SpamFilter did not check to see if/when the DB come back online. So even if the database server came back online, the quarantine functionality was disabled until SpamFilter was restarted. This only affected the scenario where the DB was offline when SpamFilter started - if the DB went offline *after* SpamFilter was launched, SpamFilter would automatically resume the quarantine functionality when the DB came back online }

// New to VersionNumber = '4.7.6.297';
{TODO -cFix: When using the feature in the bl_emailsfrom to block emails in the format spammer@badactor.com|victim@logsat.com, SpamFilter was not checking the email in the "From:" header if the option to check the From: headers was enabled. This is fixed now}
{TODO -cFix: SpamFilter wasn't logging the "From:" header email address that matched the EmailsFrom blacklist when there was a match on the From: header}

// New to VersionNumber = '4.7.6.295';
{TODO -cNew : Appended reason for disconnect to log entry "aaa.bbb.ccc.ddd - john@spammer.com will be disconnected " to identify emails that were force-deleted and why ('Attempted rela', or 'EmailTO is not in AuthorizedTOEmail', or 'ForceDelete was specified in a filter') }

// New to VersionNumber = '4.7.6.294';
{TODO -cFix : Fixed compliancy with RFC 7208 sec 4.6.4 - the SPF filter was marked as failed after one single DNS error while the RFC recommended allowing two failures. Added new parameter in the SpamFilter.ini file to customize the number of allowed DNS failures (defaults to 2) - MaxSPFLookupErrors=2 }

// New to VersionNumber = '4.7.6.293';
{TODO -cFix : Fixed a regression error introduced in 4.7.6.263 which caused a spam email to be delivered to all recipients if one of them had the sender matched to just one of the recipients in the AutoWhiteListForceDelivery whitelist. Normally the email would be blocked for all recipients and just delivered to the one who had whitelisted the sender}

// New to VersionNumber = '4.7.6.292';
{TODO -cFix : Fixed a bug in the handling of the SPF macro %{ir}

// New to VersionNumber = '4.7.6.291';
{TODO -cFix : If using option to check SPF record using domain in "From:" header, SpamFilter was needlessly repeating the SPF check if the MAIL FROM and From: email addresses matched}
{TODO -cFix : When performing SPF checks, if a DNS look failed SpamFilter could add an invalid/needless header after the X-SF-SPF-Result: header}

// New to VersionNumber = '4.7.6.290';
{TODO -cNew : Added support for "body:" prefix in keyword filter to specify that the keyword(s) specified should be searched for in the body/text portion of the email}

// New to VersionNumber = '4.7.6.288';
{TODO -cFix : Bug affecting the forced delivery of emails from quarantine introduced in v4.7.6.275 affecting SpamFilter when using a MySQL database ruunning on a Linux system, with the MySQL option lower_case_table_names=0}

// New to VersionNumber = '4.7.6.287';
{TODO -cFix : Fixed a logging bug where entries that log a whitelisted IP with "Bypassed all rules for .......  ( Whitelisted Peer IP)" would contain a suffix with an inaccurate "matched" string that would log a random entry from a random whitelist file}

// New to VersionNumber = '4.7.6.286';
{TODO -cFix : If there is a critical error/access violation logged as "Critical error - FilterObject is nil", or as "Error occurred during RECEIVEMESSAGE: Not enough memory", or as " message is malformed and not RFC compliant (headers too long)", SpamFilter was accepting the email from the remote server but not deliver it to destination}
{TODO -cFix : If AUTH LOGIN is not enabled, even though support for AUTH LOGIN is not being advertised in the EHLO banner, SpamFilter was still accepting AUTH LOGIN requests from remote clients which tried to authenticate regardless. The authentication attempt would fail, it would get logged and the remote client would be disconnected after 3 attempts, but that consumed needless etra resources. We are now rejecting the SMTP AUTH command unless authenticatoi has been enabled}
{TODO -cFix : Bug in SpamFilter ISP Standard (not Enterprise). In a rare case the AllowedDomainFilterMatrix used to customize filters for domains, is being corrupted when loaded under very specific cases. (1) If the AllowedDomainFilterMatrix.txt file has duplicate entries with for a domain that has different destination SMTP servers, or (2) if there is a duplicate entry with the same domain which are *immediately* followed by a domain that starts with the same letter but has a dash "-" in the name }
{TODO -cFix : Greatly improved the rate with which remote servers are disconnected when under a DDoS attacks}

// New to VersionNumber = '4.7.6.285';
{TODO -cNew Added a (BL) or (WL) suffix to the entry in the logfile that logs the blacklisted or whitelisted keywords that triggered the match to identify which of the two lists (BL/WL) was used}

// New to VersionNumber = '4.7.6.284';
{TODO -cFix : When added feature in 4.7.6.283 to log the matched keyword in the WL_AutoWhiteListForceDelivery.txt, we were also adding the logging of that keyword in the X-SF headers which is not desireable. We are now only logging the keyword to the logfile}

// New to VersionNumber = '4.7.6.283';
{TODO -cNew : We're now adding to the logfile which specfic entry in the WL_AutoWhiteListForceDelivery.txt file triggered the email to be whitelisted}
{TODO -cNew : Added a new option (DisableTLSOutbound) in the SpamFilter.ini file to optinally disable TLS when forwarding outbound emails to the destination SMTP servers}

// New to VersionNumber = '4.7.6.281';
{TODO -cNew : Added the logging of the tblQuarantine.QuarID for each email that is being quarantined, and logging the tblQuarantine.QuarID whenever an email is being force-delivered from quarantine}
{TODO -cFix : When an email is being forced-delivered from the quarantine, it is always being re-scanned for viruses. If an email passed the antivirus scan at the time it was quarantined, but now with updated A/V signatures SpamFilter detects the email has a virus, SpamFilter was correctly preventing the email from being re-delivered, but it wasn't logging this fact (that is wasn't being delivered as it was infected). This is being logged now}

// New to VersionNumber = '4.7.6.280';
{TODO -cFix : When `disconnecting connections that exceeds MaxInboundConnection, these dropped connection attempts were not being logged}

// New to VersionNumber = '4.7.6.279';
{TODO -cFix : When performing a whitelisted keyword check, the new header "X-SF-SPF-Result" added in v4.7.5.258 was not being included in the keyword scan. Not that the header X-SF-SPF-Result-From-Header will however not be scanned as that is added *after* the whitelist keyword check is performed}

// New to VersionNumber = '4.7.6.278';
{TODO -cFix : When performing DNS TXT queries for SPF records, SpamFilter was processing only the first 512 bytes of the UDP response, without repeating the query using TCP (which has no limit) or without supporting EDNS which allows for larger responses. We now support EDNS and read up to 8192 bytes  in the UDP reply}

// New to VersionNumber = '4.7.6.277';
{TODO -cFix : Modified query that adds emails to quarantine by removing a redundant WHERE clause in a SQL statement that was hampering performance on MySQL databases}



Edited by LogSat - 4 hours 32 minutes ago at 6:07pm