Spam Filter ISP Support Forum

  New Posts New Posts RSS Feed - SpamFilter pre-release 4.7.3.222
  FAQ FAQ  Forum Search   Register Register  Login Login

Topic ClosedSpamFilter pre-release 4.7.3.222

 Post Reply Post Reply
Author
LogSat View Drop Down
Admin Group
Admin Group
Avatar

Joined: 25 January 2005
Location: United States
Status: Offline
Points: 4068
Direct Link To This Post Topic: SpamFilter pre-release 4.7.3.222
    Posted: 23 March 2017 at 9:00am
A new pre-release of SpamFilter (v4.7.3.222) is available in the registered user area.

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.

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

// New to VersionNumber = '4.7.3.222';
{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}
{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}
{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}

// New to VersionNumber = '4.7.3.219';
{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}



Edited by LogSat - 01 November 2017 at 10:58pm
Roberto Franceschetti

LogSat Software

Spam Filter ISP
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down



This page was generated in 0.064 seconds.