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.

Uhm. I'm pasting a response to a similar posting today ( 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}
==============================

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.