We have released a new version of SpamFilter ISP which supports the new SPF (Sender Policy Framework) open standard. This latest build also features a new auto-whitelisting behavior as follows:

When an end-user goes in their web quarantine and forces the delivery of an email that was mistaken for spam, that sender is automatically added to an internal whitelist that is connected with that specific recipient. From then on, when that sender emails that recipient, they will be whitelisted since the recipient already established that they wish to receive email from them. This feature should reduce the number of subsequent false positives greatly for those users who access their web quarantine. The file used to store this whitelist is AutoWhiteListForceDelivery.txt. Anytime this file is modified, either by SpamFilter or by an external tool, SpamFilter will notice and will reload it in memory with the updated data.

Roberto F.
LogSat Software

Kevin,

Look in the SpamFilter.ini file.  The path is there and can be changed. My path is non standard and I did change it with no issues.

Dan S.

Alan,

If you upgraded without doing a fresh install (likely the case), the additional entries do not get written to the ini file until you click on the "Save Settings" button. Until then, default values are used, and as soon as the ini file is updated for any reason, these defaults are written to it.

Roberto F.
LogSat Software

George,

Do you have your filters in the default path?  I have all my filters in a non-default folder.  I actually have a script that does my upgrades but the steps were:  Stopped the service, copied the new files over, started the service.  I then went into the ini and modified the path of the new filter to be my default path and did a service restart so that SpamFilter would read the ini back in.  As soon as I then hit the "Save Settings" button, the file was created.  I did this in several installations and it acted the same in all cases.  One difference with this list is that the file path is set directly in the ini file along with the "AutoWhiteListForceDelivery=1" setting rather than through the GUI.   Did your install add the "AutoWhiteListForceDelivery=1" ini setting?  If not, add it manually.

I am probably not giving you any info you do not already know but it can't hurt to post it anyway.

Regards,

Dan S.

Problem solved. Path was not entered in the ini properly.

Thanks to Dan for the quick fix.

g