<?xml version="1.0" encoding="utf-8" ?>
<?xml-stylesheet type="text/xsl" href="RSS_xslt_style.asp" version="1.0" ?>
<rss version="2.0" xmlns:WebWizForums="http://syndication.webwiz.co.uk/rss_namespace/">
 <channel>
  <title>Spam Filter ISP Forums : Announcements</title>
  <link>https://www.logsat.com/spamfilter/forums/</link>
  <description><![CDATA[This is an XML content feed of; Spam Filter ISP Forums : Announcements : Last 10 Posts]]></description>
  <pubDate>Wed, 11 Nov 2026 17:45:50 +0000</pubDate>
  <lastBuildDate>Mon, 02 Nov 2026 18:06:20 +0000</lastBuildDate>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>Web Wiz Forums 11.04</generator>
  <ttl>30</ttl>
  <WebWizForums:feedURL>https://www.logsat.com/spamfilter/forums/RSS_topic_feed.asp?FID=3</WebWizForums:feedURL>
  <image>
   <title><![CDATA[Spam Filter ISP Forums]]></title>
   <url>https://www.logsat.com/spamfilter/forums/forum_images/web_wiz_forums.png</url>
   <link>https://www.logsat.com/spamfilter/forums/</link>
  </image>
  <item>
   <title><![CDATA[Announcements : SpamFilter 4.7.6.301 is officially released]]></title>
   <link>https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7177&amp;PID=14982&amp;title=spamfilter-476301-is-officially-released#14982</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.logsat.com/spamfilter/forums/member_profile.asp?PF=8">LogSat</a><br /><strong>Subject:</strong> SpamFilter 4.7.6.301 is officially released<br /><strong>Posted:</strong> 02 November 2026 at 6:06pm<br /><br />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.&nbsp;<br><br>As always, this upgrade is free for all users with a current software maintenance.<br><br>The full list of changes since the latest official release (4.7.4.276) is as follows:<br><br><font size="1">// New to VersionNumber = '4.7.6.301';<br>{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"}<br><br>// New to VersionNumber = '4.7.6.300';<br>{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}<br>{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"}<br><br>// New to VersionNumber = '4.7.6.298';<br>{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 }<br><br>// New to VersionNumber = '4.7.6.297';<br>{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}<br>{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}<br><br>// New to VersionNumber = '4.7.6.295';<br>{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') }<br><br>// New to VersionNumber = '4.7.6.294';<br>{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 }<br><br>// New to VersionNumber = '4.7.6.293';<br>{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}<br><br>// New to VersionNumber = '4.7.6.292';<br>{TODO -cFix : Fixed a bug in the handling of the SPF macro %{ir}<br><br>// New to VersionNumber = '4.7.6.291';<br>{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}<br>{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}<br><br>// New to VersionNumber = '4.7.6.290';<br>{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}<br><br>// New to VersionNumber = '4.7.6.288';<br>{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}<br><br>// New to VersionNumber = '4.7.6.287';<br>{TODO -cFix : Fixed a logging bug where entries that log a whitelisted IP with "Bypassed all rules for .......&nbsp; ( Whitelisted Peer IP)" would contain a suffix with an inaccurate "matched" string that would log a random entry from a random whitelist file}<br><br>// New to VersionNumber = '4.7.6.286';<br>{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}<br>{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}<br>{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 }<br>{TODO -cFix : Greatly improved the rate with which remote servers are disconnected when under a DDoS attacks}<br><br>// New to VersionNumber = '4.7.6.285';<br>{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}<br><br>// New to VersionNumber = '4.7.6.284';<br>{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}<br><br>// New to VersionNumber = '4.7.6.283';<br>{TODO -cNew : We're now adding to the logfile which specfic entry in the WL_AutoWhiteListForceDelivery.txt file triggered the email to be whitelisted}<br>{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}<br><br>// New to VersionNumber = '4.7.6.281';<br>{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}<br>{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}<br><br>// New to VersionNumber = '4.7.6.280';<br>{TODO -cFix : When `disconnecting connections that exceeds MaxInboundConnection, these dropped connection attempts were not being logged}<br><br>// New to VersionNumber = '4.7.6.279';<br>{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}<br><br>// New to VersionNumber = '4.7.6.278';<br>{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&nbsp; in the UDP reply}<br><br>// New to VersionNumber = '4.7.6.277';<br>{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}<br></font><br><span style="font-size:10px"><br /><br />Edited by LogSat - 02 November 2026 at 6:07pm</span>]]>
   </description>
   <pubDate>Mon, 02 Nov 2026 18:06:20 +0000</pubDate>
   <guid isPermaLink="true">https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7177&amp;PID=14982&amp;title=spamfilter-476301-is-officially-released#14982</guid>
  </item> 
  <item>
   <title><![CDATA[Announcements : SpamFilter pre-release 4.7.6.265]]></title>
   <link>https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7162&amp;PID=14921&amp;title=spamfilter-prerelease-476265#14921</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.logsat.com/spamfilter/forums/member_profile.asp?PF=8">LogSat</a><br /><strong>Subject:</strong> SpamFilter pre-release 4.7.6.265<br /><strong>Posted:</strong> 06 February 2019 at 10:09pm<br /><br /><div>A new pre-release of SpamFilter (v4.7.6.265) is available in the registered user area.</div><div><br></div><div>Since the latest official release (v4.7.6.264), this version contains a just a one minor bug fix as follows:</div><div><br></div><div><div>// New to VersionNumber = '4.7.6.265';</div><div>{TODO -cFix : With SpamFilter ISP Standard, when using the Custom Domain Filters to disable the SPF filter for individual domains, the SPF filter was still being used to check the "From:" header in an email if the option to scan the "From:" headers is enabled in the general settings}</div><div><br></div></div><div><br></div><span style="font-size:10px"><br /><br />Edited by LogSat - 02 November 2026 at 6:03pm</span>]]>
   </description>
   <pubDate>Wed, 06 Feb 2019 22:09:36 +0000</pubDate>
   <guid isPermaLink="true">https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7162&amp;PID=14921&amp;title=spamfilter-prerelease-476265#14921</guid>
  </item> 
  <item>
   <title><![CDATA[Announcements : SpamFilter 4.7.6.262 is officially released]]></title>
   <link>https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7161&amp;PID=14917&amp;title=spamfilter-476262-is-officially-released#14917</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.logsat.com/spamfilter/forums/member_profile.asp?PF=8">LogSat</a><br /><strong>Subject:</strong> SpamFilter 4.7.6.262 is officially released<br /><strong>Posted:</strong> 09 January 2019 at 10:25pm<br /><br />We have officially released the new SpamFilter ISP and SpamFilter Enterprise v4.7.6.262. 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.&nbsp;<div><br></div><div>As always, this upgrade is free for all users with a current software maintenance.</div><div><br></div><div>The full list of changes since the latest official release (4.7.4.254) is as follows:</div><div><br></div><div><div><font size="1">// New to VersionNumber = '4.7.6.262';</font></div><div><font size="1">{TODO -cNew : Replaced the GeoIP.dat country lookup with a new database format - geoip.sqlite. This should improve misdetected Countries when perfoming lookups under heavy inbound loads. Requires the inclusion of the appropriate x32/x64 sqlite3.dll file included in both the binary-only and the full installer distributions}</font></div><div><font size="1">{TODO -cFix : The Blacklist Country blacklist was showing a "0" instead of the correct, real-time number of email blocked for each country}</font></div><div><font size="1">{TODO -cFix : Disabled the reporting of log events from the external AV updater SpamFilterAVUpdate.exe to SpamFilter as they were causing Access Violations. Logs from SpamFilterAVUpdate.exe are still being logged in their own logfiles}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.5.258';</font></div><div><font size="1">{TODO -cFix : Fixed a regression error introduced back in 2016 for these errors that might appear in the logfiles and that could in some rare cases crash SpamFilter: "Access violation at address 000000000040EBDF"}</font></div><div><font size="1">{TODO -cNew : Added a new "X-SF-SPF-Result" header in the emails indicating the result (pass/none/neutral/fail/softfail/error) of the SPF checks. It's to be noted that sometimes SPF checks are not performed if other filters have already detected the email to be spam before the SPF test is executed, or if the email is whitelisted}</font></div><div><font size="1">{TODO -cNew : Added a new "X-SF-SPF-Result-From-Header" header in the emails indicating the result (pass/none/neutral/fail/softfail/error) of the SPF checks performed on the email address specified in the "From:" header. It's to be noted that sometimes SPF checks are not performed if other filters have already detected the email to be spam before the SPF test is executed, or if the email is whitelisted}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.5.257';</font></div><div><font size="1">{TODO -cNew : Added a new "forcedelete" suffix to prevent spam emails from being quarantined anywhere the "nondr" and "null" suffixes are supported}</font></div><div><font size="1">{TODO -cNew : SpamFilter is now scanning emails that are being force-delivered out of the quarantine for viruses. If SpamFilter detects a previously undetected virus in the archived email, the email will not be delivered. Instead the database quarantine record for that email will be updated to show it was stopped becuase of a virus. If at that point the user really wants the email force-delivered, they can re-request delivery. If an email is quarantined due to a virus, but the user decides to force-deliver it, it will be delivered}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.4.255';</font></div><div><font size="1">{TODO -cFix : The SURBL filter was not checking URLs starting with https}</font></div><div><font size="1">{TODO -cNew : Eliminated an extra redundant scan of the email for domains while checking the SURB and the 0-day filters}</font></div><div><font size="1">{TODO -cFix : Resolved issue with MySQL (MS SQL Server is not affected) when quarantining emails having emojii or other encoding if the SpamFilter database server has a default character set/collation of utf8mb4 }</font></div></div><div><br></div><span style="font-size:10px"><br /><br />Edited by LogSat - 02 November 2026 at 6:03pm</span>]]>
   </description>
   <pubDate>Wed, 09 Jan 2019 22:25:30 +0000</pubDate>
   <guid isPermaLink="true">https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7161&amp;PID=14917&amp;title=spamfilter-476262-is-officially-released#14917</guid>
  </item> 
  <item>
   <title><![CDATA[Announcements : SpamFilter 4.7.4.254 is officially released]]></title>
   <link>https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7158&amp;PID=14909&amp;title=spamfilter-474254-is-officially-released#14909</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.logsat.com/spamfilter/forums/member_profile.asp?PF=8">LogSat</a><br /><strong>Subject:</strong> SpamFilter 4.7.4.254 is officially released<br /><strong>Posted:</strong> 23 September 2018 at 9:00am<br /><br />We have officially released the new SpamFilter ISP and SpamFilter Enterprise v4.7.4.254. 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.&nbsp;<div><br></div><div>As always, this upgrade is free for all users with a current software maintenance.</div><div><br></div><div>The full list of changes since the latest official release (4.7.4.246) is as follows:</div><div><br></div><div><div><font size="1">// New to VersionNumber = '4.7.4.254';</font></div><div><font size="1">{TODO -cNew : Added header in emails tracking the country of the IP connecting to SpamFilter: X-SF-OriginatingCountry}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.4.253';</font></div><div><font size="1">{TODO -cFix : SpamFilter is unable to quarantine a spam email and will retry indefinitely leaving it in the \SpamFilter\quarantine folder if both of these conditions are true: (1) Your database is offline or unavailable when SpamFilter tries to quarantine the email, and the email is thus queued for a later re-try. (2) The subject line has a NULL character in it</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.4.252';</font></div><div><font size="1">{TODO -cFix : SpamFilter Enterprise was monitoring for changes every 60 seconds all files in the \SpamFilter\Domains directory structure. This monitoring process was redundant as changes in settings in the database changes automatically trigger a reload of the affected files, and was causing high CPU usage in installations hosting thousands of domains. This redundant safety check is now performed only once per hour}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.4.250';</font></div><div><font size="1">{TODO -cFix : Outbound TLS connections were only being made with TLS 1.0, even if TLS 1.1 and TLS 1.2 were configured and in use correctly for inbound emails}</font></div><div><font size="1">{TODO -cFix : Due to a regression error since v4.5, the AUTH LOGIN appeared in the welcome banner even if authentication was disabled in SpamFilter}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.4.247';</font></div><div><font size="1">{TODO -cFix : Under a very unusual scenario, if using the new feature in 4.7.2.210 (the "FROM Emails" blacklist now supports the syntax: sender@domain.com|recipient@yourdomain.com), and the FROM emails blacklist also contains a wildcard entry (*@domain.com) where "domain.com" is also one of your own local domains (thus SpamFilter is configured to block all emails FROM your own domain), SpamFilter would incorrectly also block all emails addressed TO your domain}</font></div><div><font size="1">{TODO -cFix : If using the :NULL suffix for the FROM Emails of the Domains blacklists, and the option to also check the various filters against the "From:" header in addition to the MAIL FROM, the :NULL suffix was being ignored if the filter is triggered on the "From:" header. This bug does not affect SpamFilter if the match was made on the MAIL FROM email address}</font></div></div><div><br></div><span style="font-size:10px"><br /><br />Edited by LogSat - 09 January 2019 at 10:25pm</span>]]>
   </description>
   <pubDate>Sun, 23 Sep 2018 09:00:16 +0000</pubDate>
   <guid isPermaLink="true">https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7158&amp;PID=14909&amp;title=spamfilter-474254-is-officially-released#14909</guid>
  </item> 
  <item>
   <title><![CDATA[Announcements : SpamFilter 4.7.4.246 is officially released]]></title>
   <link>https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7155&amp;PID=14892&amp;title=spamfilter-474246-is-officially-released#14892</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.logsat.com/spamfilter/forums/member_profile.asp?PF=8">LogSat</a><br /><strong>Subject:</strong> SpamFilter 4.7.4.246 is officially released<br /><strong>Posted:</strong> 15 May 2018 at 10:04am<br /><br /><span style=": rgb251, 251, 253;">We have officially released the new SpamFilter ISP and SpamFilter Enterprise v4.7.4.246. 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.&nbsp;</span><div><br></div><div>As always, this upgrade is free for all users with a current software maintenance.</div><div><br></div><div>The full list of changes since the latest official release (4.7.4.241) is as follows:</div><div><br></div><div><div><font size="1">// New to VersionNumber = '4.7.4.246';</font></div><div><font size="1">{TODO -cNew : Fixed a typo in the settings GUI for the Keyword ::NULL option}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.4.245';</font></div><div><font size="1">{TODO -cFix : Added new setting in the SpamFilter.ini file - MaxDomains_SF0Day_MaxEmails_SFDE - Limits the number of domains to perform lookups for the SF0Day filter, and the max number of email addresses to collect from an email when checking the SFDE filter. Useful to prvent overloads when filtering email chains with hundreds/thousands of recipient where everyone clicks on "Reply to all"}</font></div><div><font size="1">{TODO -cNew : Added extra details when logging SpamFilter's routine maintenance tasks}</font></div></div><span style="font-size:10px"><br /><br />Edited by LogSat - 23 September 2018 at 9:00am</span>]]>
   </description>
   <pubDate>Tue, 15 May 2018 10:04:23 +0000</pubDate>
   <guid isPermaLink="true">https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7155&amp;PID=14892&amp;title=spamfilter-474246-is-officially-released#14892</guid>
  </item> 
  <item>
   <title><![CDATA[Announcements : SpamFilter 4.7.4.241 is officially released]]></title>
   <link>https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7153&amp;PID=14888&amp;title=spamfilter-474241-is-officially-released#14888</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.logsat.com/spamfilter/forums/member_profile.asp?PF=8">LogSat</a><br /><strong>Subject:</strong> SpamFilter 4.7.4.241 is officially released<br /><strong>Posted:</strong> 01 November 2017 at 11:00pm<br /><br />We have officially released the new SpamFilter ISP and SpamFilter Enterprise v4.7.4.241. 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.&nbsp;<div><br></div><div>As always, this upgrade is free for all users with a current software maintenance.</div><div><br></div><div>The full list of changes since the latest official release (4.7.3.217) is as follows:</div><div><br></div><div><div><font size="1">// New to VersionNumber = '4.7.4.241';</font></div><div><font size="1">{TODO -cNew : Added entries in activity logfiles to indicate when SpamFilter starts the routine process of removing old emamils from quarantine database (Starting TDeleteExpiredQuarantineThread) }</font></div><div><font size="1">{TODO -cFix : Added support for BIGINT data type for the fields tblQuarantine.QuarID, tblQuarantine.MsgID, and tblMsgs.MsgID. This is needed if admins experience would experience an overflow when using the default INT data type for those fields}&nbsp;</font></div><div><font size="1">{TODO -cFix : If the Blacklist Cache IP blocking filter is enabled, disabling it would still cause SpamFilter to check new inbound connection against the IPs present in the cache until they eventually age out a few minutes later (IPs for new connections will however not cause the IPs to be blacklisted in the cache - there was no bug in this behavior) }&nbsp;</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.4.239';</font></div><div><font size="1">{TODO -cFix : Disabled the advertising of BINARYMIME in the EHLO banner as that extension can only be used with CHUNKING (which is not available in SpamFilter)}</font></div><div><font size="1">{TODO -cFix : Issue introduced in 4.7.4.232 - Running the standalone version of SpamFilter.exe did not automatically launch SpamFilter with elevated privileges - users had to manually "launch as administrator" the standalone version for it to work properly}</font></div><div><font size="1">{TODO -cNew : Changed the behavior of the filter order - if a recipient is not in the "Authorized TO Emails", that recipient will be rejected even if a whitelist is active since that adddress is non-existent. If however the connection is being whitelisted, the DisconnectOnNonAuthorizedTO=1 option in the SpamFilter.ini will be ignored and the connection will not be forcefully disconnected}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.4.236';</font></div><div><font size="1">{TODO -cFix : Resolved issue during Active Directory and LDAP SMTP Authentication for this error: Account failed: Error Opening Connection to Server}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.4.235';</font></div><div><font size="1">{TODO -cFix : Undid this change in 4.7.3.235, as it may have been causing access violation errors: &nbsp; ---&gt; 4.7.4.234: Increased the max stack size per thread from 1MB to 10MB to help reducing risk of stack overflows}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.4.234';</font></div><div><font size="1">{TODO -cNew : To help troubleshooting, added log entries for when SpamFilter starts and finishes checking an email for keywords}</font></div><div><font size="1">{TODO -cFix : Complex RegEx expressions that caused a large number of recursions can cause SpamFilter to crash abruptly with stack overflows errors which prevent any logging of the cause of the problem}</font></div><div><font size="1">{TODO -cNew : Added new SpamFilter.ini option MaxRegExLimitRecursion to prevent stack overflow crashes when using complex RegEx expressions}</font></div><div><font size="1">{TODO -cFix : Increased the max stack size per thread from 1MB to 10MB to help reducing risk of stack overflows}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.4.232';</font></div><div><font size="1">{TODO -cFix : Starting from v4.7.3.217 a bug was introduced that prevented SpamFilter from looking at the "text/plain" section of the email, and only examined the html and decoded sections}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.4.231';</font></div><div><font size="1">{TODO -cFix : Added an option in the "Customized Items" tab to specify a custom reject notice for emails blocked by the attachment filter. Previously the same rejection notice used by the keyword filter was also used by the attachment filter}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.4.230';</font></div><div><font size="1">{TODO -cFix : Added SpamFilter.ini option SkipSPFWhenCheckingFromHeader - allows to optionally skip the SPF test of the From: header if using the option (disabled by default) to also test the email in the "From:" header in addition to the MAIL FROM against all blacklists/whitelistss/SPF (the SPF standard only recommends to test the MAIL FROM, not the From: header)}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.3.225';</font></div><div><font size="1">{TODO -cFix : Regression error bug introduced in 4.7.2.184 that re-introduced a bug fixed in 4.7.1.150: If a DNS server is offline, SpamFilter will not cause a timeout and switch to a backup DNS server if one was specified}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.3.224';</font></div><div><font size="1">{TODO -cNew : Included the testing of the SPF filter even for addresses specified in the "From:" header, if the new option in 4.7.2.217 is selected (Added an option to include the email address in the "From:" header) }</font></div><div><font size="1">{TODO -cFix : Bug introduced in 4.7.3.219. The SPF test to incorrectly fail under one scenario: The sender specifies the "mx" mechanism in the SPF TXT record, and the IP address of the sender does not match the IP of the host in the MX record (thus failing the MX record check in SPF). The bug causes the entire SPF check to fail if the above scenario occurs, even if other entries in the SPF test would cause it to pass.}</font></div><div><font size="1">{TODO -cFix : Some database errors while editing the filtering settings using SpamFilter's GUI could cause application crash screen to appear on screen even if they are harmless-non-critical}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.3.222';</font></div><div><font size="1">{TODO -cNew : When using the option to include the email address in the "From:" header introduced in v4.7.3.217, we are now also comparing the From: header when testing the entries in the AutoWhitelistForceDelivery file}</font></div><div><font size="1">{TODO -cFix : When using the option to include the email address in the "From:" header introduced in v4.7.3.217, SpamFilter was not logging the fact that the email was being whitelisted when the sender matched due to the From: hedaer}</font></div><div><font size="1">{TODO -cFix : During an SPF filter TXT record check, if the TXT record is longer than 255 characters, and the DNS server used by SpamFilter has a bug that causes it to respond with a malformed packet (which will be flagged as such during a Wireshark capture), this can cause SpamFilter to max out the CPU and freeze after a few such queries}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.3.219';</font></div><div><font size="1">{TODO -cFix : During an MX filter record check, if a DNS server does not allow SpamFilter to query it, SpamFilter incorrectly treats the error "DNS Server Reports Query Refused Error" as a "DNS Server Reports Query Name Error". As the latter (Query Name Error) indicates a non-existent record, the "Query Refused Error" makes SpamFilter think the MX record does not exist and thus the email is incorrectly rejected}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.3.218';</font></div><div><font size="1">{TODO -cFix : Fixed issue with Bayesian filter introduced in 4.7.3.217: Exception occurred during GetMessageTokens: Error in regular expression at offset 2: unrecognized character after (? or (?- 00b2da8e SpamFilterSvc.exe System.RegularExpressionsCore}</font></div></div><div><br></div><span style="font-size:10px"><br /><br />Edited by LogSat - 15 May 2018 at 10:04am</span>]]>
   </description>
   <pubDate>Wed, 01 Nov 2017 23:00:15 +0000</pubDate>
   <guid isPermaLink="true">https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7153&amp;PID=14888&amp;title=spamfilter-474241-is-officially-released#14888</guid>
  </item> 
  <item>
   <title><![CDATA[Announcements : SpamFilter pre-release 4.7.3.222]]></title>
   <link>https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7149&amp;PID=14870&amp;title=spamfilter-prerelease-473222#14870</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.logsat.com/spamfilter/forums/member_profile.asp?PF=8">LogSat</a><br /><strong>Subject:</strong> SpamFilter pre-release 4.7.3.222<br /><strong>Posted:</strong> 23 March 2017 at 9:00am<br /><br />A new pre-release of SpamFilter (v4.7.3.222) is available in the registered user area.<div><br></div><div>This version contains a just a few minor bug fixes, along with the option to include the email address specified in the "From:" header when checking entires in the AutoWhitelistForceDelivery filter.</div><div><br></div><div><span style=": rgb251, 251, 253;">The full list of changes since the latest official release (4.7.3.218) is as follows:</span></div><div><span style=": rgb251, 251, 253;"><br></span></div><div><div><font size="1">// New to VersionNumber = '4.7.3.222';</font></div><div><font size="1">{TODO -cNew : When using the option to include the email address in the "From:" header introduced in v4.7.3.217, we are now also comparing the From: header when testing the entries in the AutoWhitelistForceDelivery file}</font></div><div><font size="1">{TODO -cFix : When using the option to include the email address in the "From:" header introduced in v4.7.3.217, SpamFilter was not logging the fact that the email was being whitelisted when the sender matched due to the From: hedaer}</font></div><div><font size="1">{TODO -cFix : During an SPF filter TXT record check, if the TXT record is longer than 255 characters, and the DNS server used by SpamFilter has a bug that causes it to respond with a malformed packet (which will be flagged as such during a Wireshark capture), this can cause SpamFilter to max out the CPU and freeze after a few such queries}</font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.3.219';</font></div><div><font size="1">{TODO -cFix : During an MX filter record check, if a DNS servers does not allow SpamFilter to query it, SpamFilter incorrectly treats the error "DNS Server Reports Query Refused Error" as a "DNS Server Reports Query Name Error". As the latter (Query Name Error) indicates a non-existent record, the "Query Refused Error" makes SpamFilter think the MX record does not exist and thus the email is incorrectly rejected}</font></div><div><br></div></div><span style="font-size:10px"><br /><br />Edited by LogSat - 01 November 2017 at 10:58pm</span>]]>
   </description>
   <pubDate>Thu, 23 Mar 2017 09:00:56 +0000</pubDate>
   <guid isPermaLink="true">https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7149&amp;PID=14870&amp;title=spamfilter-prerelease-473222#14870</guid>
  </item> 
  <item>
   <title><![CDATA[Announcements : SpamFilter 4.7.3.217 is officially released]]></title>
   <link>https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7147&amp;PID=14864&amp;title=spamfilter-473217-is-officially-released#14864</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.logsat.com/spamfilter/forums/member_profile.asp?PF=8">LogSat</a><br /><strong>Subject:</strong> SpamFilter 4.7.3.217 is officially released<br /><strong>Posted:</strong> 30 January 2017 at 6:56pm<br /><br /><span style=": rgb251, 251, 253;">We have officially released the new SpamFilter ISP and SpamFilter Enterprise v4.7.3.217. 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.&nbsp;</span><div><br></div><div>As always, this upgrade is free for all users with a current software maintenance.</div><div><br></div><div>The full list of changes since the latest official release (4.7.2.209) is as follows:</div><div><br></div><div><div><font size="1">// New to VersionNumber = '4.7.3.217';</font></div><div><font size="1">{TODO -cNew : Added an option to include the email address in the "From:" header, in addition to the real envelope email address specified in the MAIL FROM command, when checking the sender's email agains the "FROM Emails" blacklist, the "Domains" blacklist, the "Excluded FROM Emails" whitelist, and the "Excluded Domains / IPs" whitelist}</font></div><div><span style="font-size: x-small;"><br></span></div><div><span style="font-size: x-small;">{TODO -cNew : Replaced the internal RegEx library to improve speed and stability for keyword searches. RegEx search speed has dramatically increased by 16x. Sites using tens of thousands of RegEx expressions or more can see a tenfold reduction in CPU usage}</span></div><div><font size="1"><br></font></div><div><font size="1">{TODO -cNew : Simiarly to how it's done for the "Subject:" header, added support for keyword blacklist/whitelist searches targeted specifically to the "From:" and the "To" headers by prefixing the keywords with "EmailFrom:" or "EmailTo", as well as to search thru ALL the headers by prefixing the keyword with "Headers:". For ex a RegEx keyword of EmailFrom:(test&#091;1,2&#093;.com) will search for the RegEx expression "test&#091;1,2&#093;" in the email's "From:" hedaer}</font></div><div><font size="1"><br></font></div><div><font size="1">{TODO -cFix : Some RegEx expressions with greedy serch options could cause stack overflows in SpamFilter if searching thru email content that casues the RegEX to peform a huge number of recursions to find the text.}</font></div><div><font size="1"><br></font></div><div><font size="1">{TODO -cFix : A bug was introduced in build 4.7.2.210 that prevented SpamFilter from starting up unless a database connection had been established}</font></div><div><font size="1"><br></font></div><div><font size="1"><br></font></div><div><font size="1">// New to VersionNumber = '4.7.2.210';</font></div><div><font size="1">{TODO -cFix : In the 64bit version of SpamFilter, under high traffic scenarios (&gt; 750,000 emails/day) SpamFilter could had times identify the wrong country when performing the IP-to-country database lookups}</font></div><div><font size="1"><br></font></div><div><font size="1">{TODO -cNew : The "FROM Emails" blacklist now supports the syntax: sender@domain.com|recipient@yourdomain.com. Wildcards are supported for both the sender and the recipient. This will cause the sender (sender@domain.com) to be blacklisted only if one of the recipient in the email is recipient@yourdomain.com}</font></div><div><br></div></div><span style="font-size:10px"><br /><br />Edited by LogSat - 01 November 2017 at 11:01pm</span>]]>
   </description>
   <pubDate>Mon, 30 Jan 2017 18:56:30 +0000</pubDate>
   <guid isPermaLink="true">https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7147&amp;PID=14864&amp;title=spamfilter-473217-is-officially-released#14864</guid>
  </item> 
  <item>
   <title><![CDATA[Announcements : New antivirus plugin update]]></title>
   <link>https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7145&amp;PID=14861&amp;title=new-antivirus-plugin-update#14861</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.logsat.com/spamfilter/forums/member_profile.asp?PF=8">LogSat</a><br /><strong>Subject:</strong> New antivirus plugin update<br /><strong>Posted:</strong> 16 December 2016 at 10:06am<br /><br />We have just released a new version of the optional CYREN antivirus plugin - v5.4.30. This update resolves a memory leak in the previous versions.<div><br></div><div>The previous version was 5.4.23. You can verify which version of the antivirus plugin you are running by looking in the Anti Virus tab in SpamFilter as in the screenshot below.</div><div><br></div><div>To upgrade, simply stop SpamFilter's service, run the antivirus installer selecting SpamFilter's installation directory as the destination for the antivirus plugin, and restart SpamFilter.</div><div><br></div><div><img src="uploads/8/SpamFilter-antivirus-SDK-Versi&#111;n.png" height="573" width="689" border="0" align="left" /><br></div><span style="font-size:10px"><br /><br />Edited by LogSat - 02 November 2026 at 6:04pm</span>]]>
   </description>
   <pubDate>Fri, 16 Dec 2016 10:06:46 +0000</pubDate>
   <guid isPermaLink="true">https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7145&amp;PID=14861&amp;title=new-antivirus-plugin-update#14861</guid>
  </item> 
  <item>
   <title><![CDATA[Announcements : SpamFilter pre-release 4.7.2.210]]></title>
   <link>https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7143&amp;PID=14858&amp;title=spamfilter-prerelease-472210#14858</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.logsat.com/spamfilter/forums/member_profile.asp?PF=8">LogSat</a><br /><strong>Subject:</strong> SpamFilter pre-release 4.7.2.210<br /><strong>Posted:</strong> 11 December 2016 at 10:14pm<br /><br />A new pre-release of SpamFilter (v4.7.2.210) is available in the registered user area.<div><br></div><div>Starting from this version we are extending the existing "FROM Emails" blacklist to support the syntax:</div><div><br></div><div>sender@domain.com|recipient@yourdomain.com</div><div><br></div><div>This will cause the sender (sender@domain.com) to be blacklisted only if one of the recipient in the email is recipient@yourdomain.com.&nbsp;Wildcards are supported for both the sender and the recipient's email addresses</div><div><br></div><div>The full list of changes since the latest official release (4.7.2.209) is as follows:</div><div><br></div><div><div><font size="1">// New to VersionNumber = '4.7.2.210';</font></div><div><font size="1">{TODO -cFix : In the 64bit version of SpamFilter, under high traffic scenarion (&gt; 750,000 emails/day) SpamFilter could had times identify the wrong country when performing the IP-to-country database lookups}</font></div><div><font size="1">{TODO -cNew : The "FROM Emails" blacklist now supports the syntax: sender@domain.com|recipient@yourdomain.com. Wildcards are supported for both the sender and the recipient. This will cause the sender (sender@domain.com) to be blacklisted only if one of the recipient in the email is recipient@yourdomain.com}</font></div></div><div><br></div>]]>
   </description>
   <pubDate>Sun, 11 Dec 2016 22:14:32 +0000</pubDate>
   <guid isPermaLink="true">https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7143&amp;PID=14858&amp;title=spamfilter-prerelease-472210#14858</guid>
  </item> 
 </channel>
</rss>