blank

Behaviour:

The event viewer repeatedly shows the following message:

---------------
Gateway Role 1088:
Could not secure an inbound connection with the host 192.168.0.100:53627.
Die angegebenen Daten konnten nicht entschlüsselt werden
Error type:
System.ComponentModel.Win32Exception
Error number:2147500037
Program location:
---------------

As a result, an SChannel error will appear in the Windows applications event viewer. It may look like this:
---------------
SChannel 36887:
Es wurde eine schwerwiegende Warnung vom Remoteendpunkt empfangen. Die schwerwiegende Warnung hat folgenden für das TLS-Protokoll definierten Code: 51.
---------------

Please note that ID and code may differ.

Explanation:

Windows 2008 R2 and later does not support older, weak cipher suites, which are considered cracked. Therefore, a TLS connection is not established if the delivering server can only process these. As a result, the above-mentioned warnings and errors are logged. The delivering server must then perform a fallback to plain text. For this it is necessary that the delivering server establishes a new connection, since the old connection, where no TLS connection could be established, must be closed.

blank

Error:

In some cases the reply link created by NoSpamProxy Large Files cannot be inserted into emails.

Solution:

Please check whether the following security setting is effective via GPO:

GPO Einstellung für Antwortlink

If so, please set the activated security setting to “Disabled”.

blank

Important: Since NoSpamProxy requires Framework 4.6.2, the workaround described below no longer works because Exchange 2010 is not compatible with Framework 4.6.2 (https://technet.microsoft.com/library/ff728623(v=exchg.150).aspx).

If NoSpamProxy version 7.7 or later and Exchange 2010 are installed on the same server, the Exchange Management Console no longer works properly. The reason for this is the .NET Framework 4.0. The Exchange Management Console requires the Framework version 2.0 as the default handler, while the NoSpamProxy Management Console only works with version 4.0. To use the correct .NET Framework version by default, the NoSPamProxy setup 7.7 creates an environment variable called “COMPLUS_ApplicationMigrationRuntimeActivationConfigPath”.

This variable refers to a path where a config file with the appropriate settings is stored. When any MMC is called, the corresponding variable, and thus the configuration file, is used. This causes the known problems when opening the Exchange MMC. To be able to use the Exchange MMC again, there is only the following workaround:

The environment variable is permanently deleted and the NoSpamProxy MMC must be called via a batch file in which the corresponding environment variable is defined beforehand. The advantage is that in this case the environment variable is only used for programs that are called from the context of the batch file.

To work around the problem, do the following:

First, open Windows Explorer.

Right-click Computer and select Properties.

In this window, click Advanced System Settings. The following window opens:

Click “Environment Variables” here.

Managment Konsole Umgebungsvariablen setzen

In the “Environment Variables” window, select “COMPLUS_ApplicationMigrationRuntimeActivationConfigPath” in the “System Variables” section and then click “Edit”. Copy the path in the “Value” field to the clipboard. Then delete the complete entry. Click on OK, Apply and again on OK.

Now open Notepad. Paste the currently copied path from the clipboard into Notepad. In addition, add the following lines:

set COMPLUS_ApplicationMigrationRuntimeActivationConfigPath=
mmc.exe "C:\Program Files\Net at Work Mail Gateway\NoSpamProxy Management Console\Net at Work Mail Gateway Configuration Console.msc"

Copy the path from the clipboard behind the first line. The Notepad file should then be structured as follows:

set COMPLUS_ApplicationMigrationRuntimeActivationConfigPath=C:\ProgramData\ComPlus Activation Configurations\
mmc.exe "C:\Program Files\Net at Work Mail Gateway\NoSpamProxy Management Console\Net at Work Mail Gateway Configuration Console.msc"

Please note that the file names of the console may differ depending on the version used. Make sure to find the .msc file in the target directory.

Also, please note that the display of the batch file in this article may be distorted by automatic line breaks.

Finally, adjust the path to the Net at Work Mail Gateway Configuration Console.msc if necessary and save the Notepad content as NoSpamProxy-MMC.bat. If you call the BATCH file, the NoSpamProxy MMC should open successfully. Starting with Windows 2008 with UAC enabled, however, you must always run the batch file as administrator. The Exchange MMC should now also open without errors.

Error:

If smartcard readers are used that are controlled via a network USB port, either the smartcard or the token on the smartcard itself is not displayed.

Status:

This error occurs whenever the connection is established in an RDP session.

Solution:

The smartcard connection via a network-based USB connection should be established via the Hyper-V Manager or the VMWare Manager via a direct connection to the VM.

blank

Error:

The NoSpamProxy Management Console can be started, but crashes if a submenu is opened. This problem does not occur with another or new users.

Status:

The NoSpamProxy Management Console creates temporary files in the temporary folder of the user directory. However, this folder contains more than 65,535 files, which leads to problems in the NTFS file system.

Solution:

The affected user executes the following command via Start -> Run:

rmdir /s /q %temp%

When the operation is complete, the console will function properly again.

blank

Error:

Without a noticeable reason, the services of NoSpamProxy no longer start. Re-installation does not work. The following error is displayed in the event display:

Log name: System
Source: Microsoft-Windows HttpEvent
Date: 14.03.2012 14:42:55
Event ID: 15005
Task Category: None
Level: Error
Keywords: Classic
User: Not applicable

Description:

The underlying transport for [::]:6060 cannot be bound. The list may contain a reference to an interface that may not be present on this computer for IP listening purposes only. The data field contains the error number.

Status:

This problem occurs in conjunction with IPv6. The “Net TCP Port Sharing” service will then be disconnected. The exact cause is still unknown.

Solution 1:

Enter the following command on the command line:

netsh http add iplisten ipaddress=0.0.0.0

Then the services of the Net at Work Mail Gateway will restart.

Solution 2:

Enter the following command on the command line:

netstat -ano >netstat.txt

Check in the netstat.txt whether a process may occupy port 6060. If this is the case, the corresponding PID (Process ID) is displayed. You can then use task manager to find out to which process the PID belongs. Then it is necessary to clarify whether the process can be adjusted accordingly or not.

Error:

When establishing the connection between the intranet role and the gateway role the error message “The security protocol cannot verify the incoming message” is displayed. The dialog terminates in an error message and the connection object is not created afterwards.

Status:

This problem occurs if the two roles were installed on different servers and the times differ by more than 5 minutes.

Solution:

Adjust the times on both systems.

blank

Error:

When receiving and decrypting a 5MB email, the email is rejected and the error “ASN1 not enough memory” is displayed. The same error is also displayed in message tracking.

Status:

This problem occurs because a buffer size is not properly increased by the .NET framework. This problem is known to Microsoft and can be fixed with the hotfix below.

Solution:

To resolve this problem, install the following Microsoft hotfix: http://support.microsoft.com/kb/2480994/de

http://support.microsoft.com/kb/2480994/de