Update recommendations

General Information

NOTE: For more information on updates to version 14 or higher, please visit Updating to version 14.

Update sequence

  1. Update the Intranet Role. This may take some time. Under certain circumstances, a temporary increase in the allocated RAM memory is helpful.
  2. Update the Gateway Role(s). If you use several Gateway Roles, update them one after the other.
  3. Update the Web Portal.

If the Gateway Role and Intranet Role are installed on the same computer

  • In most cases of an update, you must perform manual steps before and after the installation, otherwise the smooth operation of NoSpamProxy is no longer guaranteed.

    NOTE: Please refer to the notes under Upgrade paths.

  • After performing a program update, always check the configuration of NoSpamProxy. In particular, check the licence displayed on the overview page of the NoSpamProxy Command Center. See Actions on the overview page.

Offline installation

For information on installation without access to the Internet, see Offline installation.

Licenses

If you have any questions about your licence, please contact our support team at support@nospamproxy.de.

For the fastest possible processing of your request, please send us the following information:

  • The used version of NoSpamProxy
    You can find the version number in the overview of the NoSpamProxy Command Center in the upper right corner. See NoSpamProxy Command Center.
  • Your existing customer number
    You can find the customer number on the overview page of NoSpamProxy under Manage License or in your license file under <field name="ContactNumber">C12345</field> . See NoSpamProxy Command Center.

Proxy settings

The proxy settings are made in a configuration file. These settings are overwritten with every update and must be adjusted again afterwards. Therefore, copy the corresponding configuration files to a backup directory in advance in order to be able to use them again afterwards.

NOTE: In the case of updates, for example from version 13.1 to version 13.2, the files can continue to be used. For updates from version 13.2 to version 14 or further updates to versions higher than version 14, the changes must be made on the basis of the new files.

Template adaptations

If you are updating from NoSpamProxy 10.x or lower to a newer version, you must still back up the template files of NoSpamProxy manually. Under Changing the design of the NoSpamProxy Web Portal in version 10 and How to customise NoSpamProxy notifications, the adaptation of the respective files is described. These are overwritten with every update to version 10.x and must be saved in advance. After the update you can copy the files back into the original directory. With version 11.x a template designer is integrated in NoSpamProxy. This step will no longer be necessary unless you have adjusted the texts in the templates.

NOTE: In the case of updates, for example from version 13.1 to version 13.2, the files can continue to be used. For updates from version 13.2 to version 14 or further updates to versions higher than version 14, the changes must be made on the basis of the new files.

Upgrade paths

Depending on which previous version you upgrade from to the current version of NoSpamProxy, different steps must be performed. You do not need a new license file if the software maintenance is still valid.

Update from version 13.2 to version 14

When updating to version 14, please refer to the notes under Changes and recommendations as of version 14.

Update from version 13.1 to version 13.2

When upgrading from version 13.1 to version 13.2, all settings and user information are retained.

Update from version 13 to version 13.1

When upgrading from version 13 to version 13.1, all settings and user information are retained.

Update from version 12.2 to version 13

When upgrading from version 12.2 to version 13, all settings and user information are retained. Make sure that the .NET Framework version 4.7.2 is installed and that the SQL Server version is at least 2008 R2, better 2012 or newer. With version 13.0 we have changed the license integration from license file to license key. Please refer to the Knowledge Base article Installing a new license.

Update from version 12.1 to version 12.2

When upgrading from version 12.1 to version 12.2, all settings and user information are retained.

Update from version 12 to version 12.1

Level-of-Trust Hash values are written as SHA-2 instead of MD5 starting with version 11.1. Starting with the following version (version 12.0) the support for reading MD5 will be dropped. The upgrade from a version before 11.1 to a version after 11.1 has to be done via version 11.1 and version 11.1 has to run for one week so that all required hash trusts are converted to SHA-2.

Otherwise, all settings and user information will be retained when upgrading from version 12 to version 12.1.

Update from version 11.1 to version 12

Version 12 of NoSpamProxy requires at least a SQL Server 2008R2 or later. For performance reasons, it is recommended to switch to SQL Server 2016. When updating from version 11.1 to version 12, all settings and user information are retained during the update.

Update from version 11 to version 11.1

With version 11.1, the SQL Server version 2008 is required. Please update your SQL Server 2005 to at least version 2008 before you start the NoSpamProxy Update. When upgrading from version 11 to version 11.1, all settings and user information are retained during the update.

Update from version 10.1 to version 11

When upgrading from version 10.1 to version 11, all settings and user information are retained during the upgrade. The NoSpamProxy Disclaimer Administrators group is added for the use of the NoSpamProxy Disclaimer. Please add all users who should manage the templates and rules of the disclaimers to this user group.

Update from version 10 to version 10.1

When upgrading from version 10 to version 10.1, all settings and user information are retained during the upgrade. Upgrades from older versions For information on upgrades from older versions, please refer to our Knowledge Base.