Print Page | Close Window

Auto whitelist issue

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=6120
Printed Date: 09 May 2025 at 3:24am


Topic: Auto whitelist issue
Posted By: corymckee
Subject: Auto whitelist issue
Date Posted: 26 June 2007 at 3:28pm

My autowhite list does not seem to be working. I checked one of the several domains that we have set up and none of the email that the user has unjunked are showing up. Also the things in the list are not for their domain, but for the other domains that are setup.

Please advise.


Replies:
Posted By: LogSat
Date Posted: 26 June 2007 at 10:36pm
It is possible that the ini settings that specify the AutoWhiteListForceDelivery.txt file name do not specify the full path to the file.

The ini file above depends on the version of SpamFilter you are using.

In SpamFilter version *prior* to v3.5, the entry will be in the SpamFilter.ini file.

In SpamFilter ISP 3.5.x "Standard", the entry is in the file \SpamFilter\Domains\SFI\Filters.ini

In SpamFilter Enterprise 3.5.x the entry is hardcoded in the application, and the problem should not occurr...

The entry name is:
WL_AutoWhiteListForceDeliveryFileName

Can you please ensure that the value indicated for that entry has a full path name (drive and directory) to the file, and does not contain just a file name?

If for some reason, the "AutoWhiteListForceDeliveryFileName" entry does not specify a path, Windows will load whatever file it finds in the path. If you scan your hard drives, most likely you'll find a "AutoWhiteListForceDelivery.txt" file that is not in the SpamFilter directory. This file is the one that may be loading, not the one you intended to use in the SpamFilter directory. Specifying a full path name in the ini file should solve all your troubles.



-------------
Roberto Franceschetti

http://www.logsat.com" rel="nofollow - LogSat Software

http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP

Posted By: corymckee
Date Posted: 27 June 2007 at 12:31am

We are using the enterprise edition.

Please advise on our next course of action.

Thank you.

Posted By: LogSat
Date Posted: 27 June 2007 at 6:02pm
Uhm. I'm pasting a response to a similar posting today ( http://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=6122#10391 - www.logsat.com/spamfilter/forums/forum_posts.asp?TID=6122#10 391 ). It's possible the problem may be the same.

=================
For the second half, going back to your problem, before we continue with the troubleshooting, could you please let us know what build of SpamFilter you are using? There was a bug that could have caused a similar impact in an earlier version of SpamFilter:

// New to VersionNumber = '3.5.3.677';
{TODO -cNew : SpamFilter Enterprise was deleting and re-inserting the entire AutoWhiteListForceDelivery list in the database when appending a new entry, possibly causing data loss in high traffic scenarios. This process was rewritten to append the new individual records only}
==============================



-------------
Roberto Franceschetti

http://www.logsat.com" rel="nofollow - LogSat Software

http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP

Posted By: corymckee
Date Posted: 03 July 2007 at 12:38pm
I thought I had replied to this but I guess not. Its the latest version and it is a new installation.

Posted By: LogSat
Date Posted: 04 July 2007 at 9:25am
Could you please contact us via email? We'd like to see if it's possible to have access to your server so we can better troubleshoot this.

-------------
Roberto Franceschetti

http://www.logsat.com" rel="nofollow - LogSat Software

http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP

Posted By: corymckee
Date Posted: 04 July 2007 at 12:58pm

Thank you for the quick response. It turns out that the latest version did indeed fix this issue.

Regards


Print Page | Close Window