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.

Here you can find all versions that are required to upgrade to the current version. When upgrading, be sure to follow the installation and upgrade instructions for the respective version, as you may need to make manual changes. Also note that changes that you must make when upgrading from version 7.6 to 8.0, for example, are also required for a direct upgrade from 7.6 to 8.5.

The current version is available under Software Download.

Microsoft Report Viewer

Since the download has been officially discontinued, but it is needed for setups up to NoSpamProxy version 13.2 you can download it here

13.1 (Schneller Kanal)
13.1 (Regulärer Kanal)
13.0 (Schneller Kanal)
13.0 (Regulärer Kanal)
12.2 (Schneller Kanal)
12.2 (Regulärer Kanal)
12.1 (Fast Channel)
12.1 (Regular Channel)
12.0
11.1
11.0
10.1
9.2
8.5

General information concerning NospamProxy updates

Whenever you install an update of NoSpamProxy, you need to consider the following points, regardless of whether it is an update within a version or a larger version jump.

Proxy settings

The proxy settings are done in a configuration file. In the How Tos category you will find the article How to configure a web proxy for NoSpamProxy Version 9.2 or higher with the exact procedure. Unfortunately these settings are overwritten with each update and must be carried out again afterwards. Therefore, copy the corresponding configuration files into a backup directory in advance in order to be able to use them again afterwards.

IMPORTANT: For updates within e.g. 10.1 or 10.0 the files can be used 1:1. For updates from 9.x to 10.x, the changes must be made on the basis of the new files. Please refer to the above mentioned article.

Template adaptations

If you update from NoSpamProxy 10.x or earlier to a newer version, you still have to save the template files of NoSpamProxy manually. The articles on customising the Web Portal theme and the notification theme describe how to customise each file. These are overwritten for version 10.x with each update and must be saved in advance. After the update, copy the files back to the original directory. With version 11.x a template designer is integrated in NoSpamProxy. From this point on, this step is no longer necessary, unless you have adapted the texts in the templates.

Please note: For updates within e.g. 10.1 or 10.0 the files can be used 1:1. For updates from 9.x to 10.x, the changes must be made on the basis of the new files. Please refer to the above mentioned articles.

Web Portal

If the Web Portal was installed on a server without the Gateway Role, the configuration link https://<server-url>/enqsig/admin/configurecyren must be called again after the update. The NoSpamProxy CYREN Service service must then be restarted on the Web Portal.

Updating from version 12.0

Please pay attention to the notes in the installation manual and the general update notes here in the Knowledge Base.

Before updating make sure that .NET Framework 4.6.2 or later is installed and the SQL Server version corresponds to at least 2008 R2.

Upgrade NSP

When updating from version 12.0 to version 12.1, all settings and user information are retained. Only the proxy settings and content adjustments of the template files must be saved as usual and reinstalled after the update. This procedure is described in the general update notes.

Outlook Add-In

The update of the gateway and the Web Portal also requires an update of the Outlook Add-In; otherwise the communication with the Web Portal is no longer possible.

Updating from version 11.1

Please pay attention to the notes in the installation manual and the general update notes here in the Knowledge Base.

Before updating make sure that .NET Framework 4.6.2 or later is installed and the SQL Server version corresponds to at least 2008 R2.

Upgrade NSP

When updating from version 11.1 to version 12.1, all settings and user information are retained during the update, with one small exception. Only the proxy settings and content adjustments of the template files have to be saved as usual and reinstalled after the update. This procedure is described in the general update notes.

Upgrading the content filter settings

The settings made so far for the content filters are fully adopted and converted to the new format. For this, the actions configured in 11.1 are migrated to the new “Content filter actions” and then linked in the content filters. The new actions have the function in their name so that they are easy to identify. Please check the correct configuration after the successful setup.

There is now an option to distinguish between an SMTP action and a Web Portal action. This makes it possible to distinguish whether a file attached to an SMTP email arrives at the NoSpamProxy gateway or is to be sent directly via the Web Portal. After the update, only SMTP actions are available. As long as nothing else is configured, the same settings apply to attachments that arrive via the Web Portal.

Note: Content filtering can be switched on/off on a rule basis in the rule settings on the “General” tab. If no content filter is configured and in use, this should be set to off.

Upgrading message tracking

The format of message tracking in the database has changed fundamentally. Only after the successful update to version 12.1, the Intranet role will migrate the old data into the new format. This means that the message tracking data created before the update will only be available about 15 minutes after the update. This time varies strongly and depends essentially on the available data and the load capacity of the machine. If the migration fails, a warning is displayed on the initial page.

New “Reputation Filter” Filter

NoSpamProxy 12.1 introduces the reputation filter for the first time. This new system has a total of 9 different checks, all of which focus on the origin of the email. After the update to version 12.1 this filter is not activated. Please add the “Reputation filter” filter manually to your ruleset and ideally adopt the pre-set values.

Outlook Add-In

The update of the gateway and the web portal also requires an update of the Outlook Add-In, because otherwise the communication with the web portal is no longer possible.

NoSpamProxy Management Console

As of version 12.1, it is necessary to additionally enable port 6061/HTTPS on the intranet role for the access of the management console from another system.

Please follow the instructions in the installation manual and the general update instructions here in the Knowledge Base.

Before updating make sure to install .NET Framework version 4.7.2 and SQL Server version 2008 R2 or later.

Important note for update version 12.2.18253.1152 and later

As of version 12.2.18253.1152 (Fast Channel), a script for cleaning up message tracking is included. This script deletes orphaned entries in the database. It causes an increased disk space requirement on the drive with the database NoSpamProxyAddressSynchronization (Intranet roles database). Please check beforehand if there is at least five times as much storage space available on the drive as the current database.

The database file can be found in the installation folder of the Microsoft SQL Server. The default directory is “C:\Program Files\Microsoft SQL Server\<<<SQL Version.SQL Instance>>MSSQL\DATA\”.

This may also result in the setup not responding for a long time. The setup must not be aborted and must run until it is completed. Please allow a longer update period for this.

Upgrade from version 11.1

When updating from version 11.1 to version 12.2, consider the Knowledge Base article “What to consider when updating to version 12”.

Upgrade NSP

When updating from version 12.x to version 12.2, all settings and user information are retained. Only the proxy settings and content adjustments of the template files must be saved as usual and reinstalled after the update. This procedure is described in the general update notes.

Outlook Add-In

The update of the gateway and the Web Portal also requires an update of the Outlook Add-In; otherwise the communication with the Web Portal is no longer possible.