Zuletzt aktualisiert am: February 19, 2019
< zurück

Recommendations regarding upgrade paths

In practice, it is often the case that one or more versions of NoSpamProxy are skipped and the question arises whether an upgrade or even a new installation to the current version makes sense. This article is intended to help you make the right decision based on the experience of our support team and to help you avoid future problems.

Please note that this article does not deal in detail with the individual upgrade steps, for information on this you can find further articles and installation and upgrade instructions in our Knowledge Base under “Update Information”.

General information about 32-bit Windows installations

Since newer versions of NoSpamProxy from version 10 do not support 32-bit Windows installations, these systems must first be migrated to a 64-bit Windows from Windows 2008 R2 or later if an upgrade to the current version is still desired. Windows 2008 SP2 is not sufficient, because this system has some limitations, which stand in the way of an effective operation.

Upgrading from versions older than 7.6

An upgrade from versions older than 7.6 is rarely useful. An upgrade also carries the risk that database errors have crept in, which will lead to problems in later operation. A completely new installation on a new system is recommended. The configuration wizard helps you to create a new set of rules, which you can supplement with a white and black list and other special rules that are still needed. In practice, the new Level of Trust system is formed so quickly that no increase in the false positive rate must be expected.

Upgrading from versions 7.6 to 7.8

If there are no major changes to the rules or if not too many certificates (>200 currently active) are used in the NoSpamProxy encryption component (formerly enQsig), a complete reinstallation is recommended.

If you decide to upgrade, please upgrade to version 8.5 first and then run the article “Error 4503, 5372 or 1213 in the Event Viewer after update to version 7.8 or newer”. You can then upgrade to version 9.2, from which you can seamlessly jump to version 10. Please note the installation and upgrade notes of version 10 and the changes since version 9.0!

Upgrading from version 8.0 to 8.5

Again, a complete reinstall is usually the better choice.

If you have updated from version 7.x to this version and haven’t yet performed the instructions given in the article “Error 4503, 5372 or 1213 in the Event Viewer after update to version 7.8 or newer”, it is recommended to perform this preventive once before upgrading to version 9.2. Please note that you cannot upgrade directly from version 8.0 to version 9.2, but must first perform the 8.5 step. In this case, if you have not already done so, you should carry out the above article after upgrading to 8.5.

Upgrading from version 9.0 to 9.2

Please follow the installation and upgrade instructions for version 10! A few things have changed that require manual intervention or documentation of the previous settings (e.g. for the action “Manage attachments”). Since a direct upgrade to version 11 is not possible, you have to take the intermediate step via the 10.1 offered below. If you are not using 9.2, the system must be upgraded to 9.2 first.

Upgrade from version 10.0

Please pay attention to the installation and upgrade instructions of version 10! There have been some changes which require manual intervention or documentation of the previous settings (e.g. for the action “Manage attachments”). From version 11.0 you need at least SQL Server 2008 R2 Express. Please update it before upgrading.

Upgrading from version 11.1

Before updating, you should make sure that .NET Framework version 4.6.2 is installed and that the SQL Server version is at least 2008 R2.

Required legacy versions for an upgrade

In the Knowledge Base article NoSpamProxy Software Archive you can find all required legacy versions for an upgrade to the current version, should you choose to do so. Please follow the installation and upgrade instructions of the respective old version, as manual intervention may be necessary. If you upgrade from version 7.6 to 8.0, for example, you will also have to make changes if you decide to upgrade from 7.6 to 8.5.