LogSat Software

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

Duplicating a SpamFilter installation is rather easy. In the list of steps below, usually only the three tasks highlighted in blue need to be performed if you can install the SpamFilter on the new server in the same directory structure as is currently installed on the old server. If you're using the Enterprise version of SpamFilter, your SpamFilter Enterprise is located in the SpamFilter.ini file under the key named "SFEActivationCode", so if you copy the SpamFilter.ini file (as I describe below) to the new server it will activate the Enterprise functionality on the new server. Do not worry about licensing when installing the other server - you can leave both running for as long as you need to complete the migration. No extra licenses are required.

For the migration:

If
 you're not interested in SpamFilter's icons in the Start Menu and/or having SpamFilter 
appear in the Add/Remove option, you can skip this 1st installation step and proceed to the next paragraph. Install SpamFilter on the new server, accepting all the default values. This will create the icons in the "Start menu" and provide an option to uninstall SpamFilter in the Add/Remove Programs section of the Control Panel.  

Simply copy the whole \SpamFilter directory tree from the old server to the new one, maintaining the same directory tree. under the "Settings - Configuration" tab, click the button to create the SpamFilter service, if you haven't done so using the setup.exe installer above. 

If the server name of the new server is different than the one of the old server, you should also change the following entry in the new SpamFilter.ini file by setting it to 0:   
tblServersServerID=0 
This will allow the new server to also "see" all the quarantined emails that were archived by the old server. 

If the new server will have the same IP as the old one, and the installation drives/directories are the same, then nothing else is required. 

If the servers have different IPs, but you have *not* configured SpamFilter to listen for SMTP traffic on a specific IP address (this is the default setting), then again nothing else is required. 

If the new server will have a new IP, and you have configured SpamFilter to listen on a specific IP address (by default SpamFilter will listen to all IP addresses), then simply assign the new one to the new installation of SpamFilter by going to the "Settings - Configuration" tab in SpamFilter. 

The following is also needed if you change the installation path on the new server, and you are using SpamFilter ISP "standard" (as in SpamFilter Enterprise the filtering settings are stored in a database, this step is not required on the Enterprise version): 
SpamFilter ISP maintains all its filtering settings in text files (all your whitelists and blacklists). If the path to these text files changes on the new server, you simply have to updated SpamFilter's config files to reflect the new path. 

The two config files that contain the path information are: 
\SpamFilter\SpamFilter.ini 
\SpamFilter\Domains\SFI\Filters.ini 

You can thus simply edit those two files, and perform a search&replace to replace all occurrences of the old path and replace it with the new one. 

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
ik8sqi Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 25 January 2005 Status: Offline Points: 14	Post Options Post Reply Quote ik8sqi Report Post Thanks(0) Quote Reply Topic: Migrating SpamFilter to a new server Posted: 30 December 2020 at 4:19pm
	Duplicating a SpamFilter installation is rather easy. In the list of steps below, usually only the three tasks highlighted in blue need to be performed if you can install the SpamFilter on the new server in the same directory structure as is currently installed on the old server. If you're using the Enterprise version of SpamFilter, your SpamFilter Enterprise is located in the SpamFilter.ini file under the key named "SFEActivationCode", so if you copy the SpamFilter.ini file (as I describe below) to the new server it will activate the Enterprise functionality on the new server. Do not worry about licensing when installing the other server - you can leave both running for as long as you need to complete the migration. No extra licenses are required. For the migration: If you're not interested in SpamFilter's icons in the Start Menu and/or having SpamFilter appear in the Add/Remove option, you can skip this 1st installation step and proceed to the next paragraph. Install SpamFilter on the new server, accepting all the default values. This will create the icons in the "Start menu" and provide an option to uninstall SpamFilter in the Add/Remove Programs section of the Control Panel. Simply copy the whole \SpamFilter directory tree from the old server to the new one, maintaining the same directory tree. under the "Settings - Configuration" tab, click the button to create the SpamFilter service, if you haven't done so using the setup.exe installer above. If the server name of the new server is different than the one of the old server, you should also change the following entry in the new SpamFilter.ini file by setting it to 0: tblServersServerID=0 This will allow the new server to also "see" all the quarantined emails that were archived by the old server. If the new server will have the same IP as the old one, and the installation drives/directories are the same, then nothing else is required. If the servers have different IPs, but you have not configured SpamFilter to listen for SMTP traffic on a specific IP address (this is the default setting), then again nothing else is required. If the new server will have a new IP, and you have configured SpamFilter to listen on a specific IP address (by default SpamFilter will listen to all IP addresses), then simply assign the new one to the new installation of SpamFilter by going to the "Settings - Configuration" tab in SpamFilter. The following is also needed if you change the installation path on the new server, and you are using SpamFilter ISP "standard" (as in SpamFilter Enterprise the filtering settings are stored in a database, this step is not required on the Enterprise version): SpamFilter ISP maintains all its filtering settings in text files (all your whitelists and blacklists). If the path to these text files changes on the new server, you simply have to updated SpamFilter's config files to reflect the new path. The two config files that contain the path information are: \SpamFilter\SpamFilter.ini \SpamFilter\Domains\SFI\Filters.ini You can thus simply edit those two files, and perform a search&replace to replace all occurrences of the old path and replace it with the new one.
	Roberto Franceschetti LogSat Software

LogSat Software

Site Navigation[Skip]

Spam Filter ISP Support Forum

Migrating SpamFilter to a new server