Lee,

The error is actually most likely caused by our SFDB database server itself, when your SpamFilter attempted to retrieve the total number of IPs currently blacklisted in our SFDB.

That number is displayed underneath the navigation bar on the left hand side of our website, and also appears in SpamFilter under the tab "Settings - SFDB Settings", near the label "Current IPs listed in the SFDB". That number should match (plus or minus a few hundred entries, as we receive several hundreds of spam reports each second....) the number displayed on the website.

If you see a handful of such errors (in the order of 10 - 100 per day) it's not an issue to be concerned. If there are more, and/or if your SpamFilter is not able to display the number of IPs listed in the SFDB as described above, then
yes, we'll need to look into it.

As a side-note, this weekend we've made some changes to our network by moving operations to a different facility. Could you please verify that your DNS server has not cached our old IP addresses? To do so, please try pinging:
sfdb.logsat.com
from the server running SpamFilter. That should resolve to 66.181.198.8.
If it resolves to 209.26.140.8 then you may have some caching issues with  either your DNS server and/or the DNS client on the SpamFilter server, as they did not pick up the new IP address. You may want to recycle the DNS services or clear their cache to see if that helps.