Print Page | Close Window

New SpamFilter ISP v2.1.1.367 with SPF support is available

Printed From: LogSat Software
Category: Spam Filter ISP
Forum Name: Spam Filter ISP Support
Forum Description: General support for Spam Filter ISP
URL: https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=3996
Printed Date: 12 March 2025 at 7:09am


Topic: New SpamFilter ISP v2.1.1.367 with SPF support is available
Posted By: LogSat
Subject: New SpamFilter ISP v2.1.1.367 with SPF support is available
Date Posted: 19 July 2004 at 12:03am

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




Replies:
Posted By: kspare
Date Posted: 19 July 2004 at 11:49am

Roberto, is it possible to either pick where the .txt file for the autowhitelist resides or else have the data for the whitelist sit in the database? This would be helpful for people with redundant mx's

Kevin



Posted By: Desperado
Date Posted: 19 July 2004 at 12:00pm

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.

 



Posted By: Guests
Date Posted: 20 July 2004 at 11:41am
Dan I looked in my .ini file and don't see an entry in there that refers to this new AutoWhiteListForceDelivery.


Posted By: LogSat
Date Posted: 20 July 2004 at 11:50am

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



Posted By: Guests
Date Posted: 20 July 2004 at 9:58pm

Roberto,
After installing v2.1.1.367 and saving the setting I found that the "AutoWhiteListForceDelivery.txt" file was not created even after i forced a few email to be delivered. I have created the file but still have not seen any entries added.

Why would this happen. And yes I have read all the threads related to this.

Thanks for any info,

 

g



Posted By: Desperado
Date Posted: 21 July 2004 at 12:38am

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.



Posted By: Guests
Date Posted: 21 July 2004 at 1:01am

Yes to all. It just is not adding any entries to the file.

 

g



Posted By: Guests
Date Posted: 21 July 2004 at 2:31am

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

Thanks to Dan for the quick fix.

 

g




Print Page | Close Window