Multiple SFI servers, single DB |
Post Reply 
|
| Author | |
yvesp 
Newbie 
Joined: 13 February 2007 Status: Offline Points: 4 |
 Post Options
 Thanks(0)
 Quote Reply
 Topic: Multiple SFI servers, single DBPosted: 13 February 2007 at 10:13am |
|
Hi, I was wondering, if I install a second SFI server, configure it to be server number 2, and store its spam in the same DB as the first one. If a user frees a mail from SenderA that was received on server 1, will the autowhitelist by updated only on server 1 ? Does that mean that users will have to free mails twice (if received on server 2) for every sender they wish to whitelist ? If so, storing the autowhitelist in the db would fix the problem... any plans for that on the non-enterprise version ? Thanks, Yves |
|
 |
|
|
LogSat
Admin Group 
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 13 February 2007 at 4:30pm |
|
Yves,
In many installations, each separate SFI will handle different domains, which means that the same SFI will handle emails for a specific domain. In this case, the issue you mention is non-existent. If you have multiple SFI load-balanced, then yes, the behavior you describe is correct. In those cases, we suggest admins configure Windows File Replication so that the directories containing the blacklist/whitelist files are replicated between the servers. If a file is updated on one server, the change will be replicated onto the other server. When a file is modified outside of SpamFilter, SpamFilter will see the change automatically within 60 seconds, and will re-import the settings without user intervention. |
|
|
|
|
yvesp
Newbie
Joined: 13 February 2007 Status: Offline Points: 4 |
Post Options
Thanks(0)
Quote Reply
Posted: 21 February 2007 at 11:51am |
|
Roberto, What about storing the file in the db ? That would be a great way to solve the problem, and that would also add the possibility to do some form of house-cleaning based on the last time the rule was used. For example, a LastUsed colum that would be updated everytime a rule is used to whitelist a mail could be used to remove unused entries after say 1 year. Since you are already storing most data in a db in the enterprise version, moving this file to the db in the standard version would be a great feature. Yves |
|
|
|
|
LogSat
Admin Group
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 22 February 2007 at 4:23pm |
|
Yves,
In SFI, we always avoided placing configuration files in the DB, both for performance (the DBs are *much* slower that accessing text files) and for reliability reasons (if the DB goes offline, SFI could stop processing emails). In the new SpamFilter Enteprise beta we are storing the settings in the database, however they are automatically dumped to text files, and SpamFilter then reads them from the text files. This allows us to have both flexibility in using the DB, and reliability as ultimately we're reading the settings from text files. The AutoWhiteListForceDelivery setting in SFE is indeed in the database, so that should help in your case. |
|
|
|
Topic Options|
Post Reply
|
|
Tweet
|
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
This page was generated in 0.293 seconds.