Running multiple SpamFilters |
Top Previous Next |
SpamFilter is easily implemented in a load-balanced environment. SpamFilter can be installed on multiple servers, all sharing the same quarantine database. Each instance of SpamFilter will "know" which quarantined spam emails it own, and will process them accordingly.
To have multiple SpamFilters connect to the same database, simply configure each SpamFilter to point to the same database. Each instance will add itself, automatically, to the database so it can share it with the others. That's all...
SpamFilter ISP SpamFilter ISP maintains all its configurations in local text file. The file SpamFilter.ini contains the main settings for SpamFilter. When using multiple SpamFilters, the SpamFilter.ini file will be the same on all servers. The only exception is if you configure one or more SpamFilter to listen for SMTP traffic on a specific IP on the server., rather than the default "bind to all IPs". In this case, the ini files would be different.
The various blacklist / whitelist / keyword entries are stored in individual, user-defined files. We recommend placing these files in a subdirectory for better organization. In a load-balanced environment, these files will usually be the same for all servers. Having them in a separate directory allows them to be more easily replicated across the multiple servers.
SpamFilter continuously monitors all its configuration files, and if any of them is changed by an external application, SpamFilter will automatically reimport all the settings within a few seconds.
SpamFilter Enterprise SpamFilter Enterprise maintains all its configurations in a database, making it simpler for multiple SpamFilter servers to share the same data. Simply configure each instance of SpamFilter to use the same database as described in the section Quarantine Database - SpamFilter Enterprise. When SpamFilter Enterprise is started, it will be automatically added to the list of servers in the database, no other configurations are necessary.
|