Was wondering if anyone who is using SFE and has a couple hundred domains and a lot of autowhitelistdelivery entries (we have about half a million) was experiencing issues where customers say that they keep seeing emails trapped by SF t in quarantine hat the users were sure were already whitelisted and that they have repeatedly whitelisted a sender but still have stuff show up in quarantine. I was ignoring these complaints myself until recently and have put a test in place to verify if entries that are being removed from quarantine already had an entry in autowhitelistdelivery table or not. 1 customer complaint I ignore, but more then 5 I start getting concerned.

A reboot of SFE1 seems to have cleared it up and both are working again. Whats wierd is that SFE1 was doing it job of stopping spam, but the part that checked the reload table was no occuring and had not all day until I rebooted.

After restarting the service, its working ok now. I am putting some logging in place to monitor so when someone retrieves an item from quarantine I can verify a reload event occurs.

As an FYI, releasing an item from the quarantine will cause SpamFilter to add it to the "tblwl_autowhitelistforcedelivery". When this happens, database triggers will add an entry to the "tblReloadTableInfo". When any of your SFE see new entries in this "tblReloadTableInfo" (this table is checked every 5 seconds), then SFE will know that the data in the other tables (tblwl_autowhitelistforcedelivery in this case) has changed, and will force an export of the affected table to the relative text file. SpamFilter will then reload the contents of the text file reloading the updated settings.

We added the extra complexity of duplicating the database settings to text files as we ultimately wanted to make SFE use text files for holding the actual configuration files, as we do not want SpamFilter to have any issues whatsoever in case the database server is unavailable.