The tagging/not tagging is a very confusing option, especially considering that adding a ":tag" or a ":tagsubject" suffix to unfiltered emails must cause a different behavior than the "tag spam and deliver" options in the general configuration settings.. There have been many slight modifications to these tagging options in the past weeks. This is a current list of changes since build 704:

// New to VersionNumber = '3.5.4.710';{TODO -cFix : When a recipient was whitelisted, in some cases SpamFilter would also whitelist additional, separate emails that could have been sent during the same SMTP session}{TODO -cFix : If a recipient was whitelisted, additional "regular" recipients would be correctly rejected, but an incorrect logfile entry was added stating that they were being also whitelisted (which in fact they were not) }

// New to VersionNumber = '3.5.4.709';{TODO -cFix : Reduced the number of memory leaks in PDF scans if documents use Cross-reference-Streams}{TODO -cFix : When forwarding emails to the destination SMTP server, if such server rejected the emails due to a mailbox full error, SpamFilter would instead send an NDR with the incorrect bounce message "The following recipients are unknown"}{TODO -cFix : Introduced bug in build 700 - If any filter is configured to "tag spam and deliver", SpamFilter was not processing spam with the following filters: keywords, Bayesian, images/PDF, SURBL. All other filters were applied correctly}{TODO -cFix : Exception occurred during TestForReject: Access violation at address 0063F52E}

// New to VersionNumber = '3.5.4.707';{TODO -cNew : Added option in SpamFilter.ini file: HideXSFWhiteListedReasonHeader}{TODO -cNew : In SFE, SpamFilter is able to now startup even if the database server is unavailable}{TODO -cFix : If a spam email is split so that it is delivered for whitelisted recipients but blocked for the rest, it was still being stored in the quarantine database for all receipients, including the whitelisted ones}{TODO -cFix : The HTML parser used to detect blank html emails was expecting legitimate opening and closing html tags to define text, and was ignoring any text outside these tags. This could cause very short html emails to appear blank if they were not following correct html syntax. We are now auto-fixing the invalid html code to be less restrictive}

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot delete your posts in this forumYou cannot edit your posts in this forumYou cannot create polls in this forumYou cannot vote in polls in this forum