I'm sorry if I have to ask, but we fell victims to this ourselves.... after adding the entry on the first server, did you click on the "Save Settings" button to update the database.

Are you able to reproduce this, or was it a one-time event? There's should be nothing else that is needed in an environment with multiple servers sharing the same database.

Can you please let us know what build of SpamFilter you are using?

We are currently working on a problem reported by one user where they are updating the database directly by running SQL scripts that modify settings for hundreds of domains at once. In that case, we *sometimes* see that the settings are not propagated among servers. This is quite a different scenario from yours, but we're currently beta testing a fix for this, and expect to release it this weekend or early next week.

In the meantime, there should never be the need to restart SpamFilter to activate filter settings. If this is what you have to do, we'd really like to help you finding out the problem. If you can contact us by email, we'd like to see if you can allow us remote access to your server so we can provide faster troubleshooting.