Morten,

Duplicating a SpamFilter installation is rather easy.

You can 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. if you're not interested in the icons, you can skip this step and proceed to the following.

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 new server will have the same IP as the old one, then nothing else is required.
 
If 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.
 
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.

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. 

Ed_K,

We would have said "it is as easy as installing 4.1.2.806 on the new server, then following these instructions", if it weren't for the fact that between v4.0.1.785 and v.4.1.2.806 there has been an addition of two fields in the tbl_filtersettings table. SpamFilter will automatically patch the database when upgrading to the new version, and records the fact that the patch was successful by adding an entry to the following value in the SpamFilter.ini file (the last one - 4.1.2.794):

DBPatchesApplied=3.5.3.690,3.5.3.696,4.0.0.767,4.0.0.770,4.0.1.780,4.1.2.794

If you follow the instructions to the letter, your new server, running the latest v4.1.2.806 will automatically update the database schema of SpamFilter's database that would be currently in use by your older version 4.0.1.785. This will not affect your older version.

If however at some point your new server is configured to use a different, non-live database, you risk that the database patches are applied to the wrong database, and will have problems when switching to the live production database. In this case, the fix is as simple as stopping your new SpamFilter, deleting ***the entire*** line:
           DBPatchesApplied=

from the SpamFilter.ini file, and restart SpamFilter. This will cause the patches to be re-applied.

MBorik,

If you are a licensed user, you may download SpamFilter ISP v3.5.4.730 from our website after logging in.