Print Page | Close Window

Multiple SFI servers, single DB

Printed From: LogSat Software
Category: Spam Filter ISP
Forum Name: Spam Filter ISP Support
Forum Description: General support for Spam Filter ISP
URL: https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=5975
Printed Date: 14 July 2025 at 9:00am


Topic: Multiple SFI servers, single DB
Posted By: yvesp
Subject: Multiple SFI servers, single DB
Date Posted: 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


Replies:
Posted By: LogSat
Date 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.


-------------
Roberto Franceschetti

http://www.logsat.com" rel="nofollow - LogSat Software

http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP

Posted By: yvesp
Date 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

Posted By: LogSat
Date 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.


-------------
Roberto Franceschetti

http://www.logsat.com" rel="nofollow - LogSat Software

http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP


Print Page | Close Window