Spam Filter ISP Forums : SpamFilter pre-release 4.7.3.222

// 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}