The WebPort is the port to which the MMC connects when accessing the individual roles. Furthermore, the roles connect via the configured port and count 1. If the WebPort is configured to 6060, the services connect via 6061. You should only change this port if it is necessary.

To change the WebPort, proceed as follows:

First, stop all NoSpamProxy services. The corresponding setting is made in all configuration files. These files can be found in the configuration directory under “C:\ProgramData\Net at Work Mail Gateway\Configuration\”. If you also use the WebPortal, you will find the corresponding configuration files under “%Program Files%\Net at Work Mail Gateway\enQsig Webportal\App_Data\”.

Look for the line that begins with the following characters:
<netatwork.nospamproxy.webservices
Add the following attribute:

port="6060" (the new port value must be entered here).

The line should now look like this:
<netatwork.nospamproxy.webservices serverCertificateThumbprint="xxx" port="6060" />
The attribute serverCertificateThumbprint will look different on each NoSpamProxy server.

Now, change the URL reservation via netssh. The HTTPSYSMANAGER tool from http://httpsysmanager.codeplex.com/ makes this easy. Alternatively, enter the following command on the command line:

netsh http add urlacl url=http://+:8060/NoSpamProxy/ sddl=D:(A;;GX;;;LS)(A;;GX;;;NS)

Restart all services now.

Switch to the new port in the MMC.

Then re-create the role connections.

The default settings are as follows:

  • The first attempt takes place after 5 minutes.
  • The second attempt takes place after 10 minutes.
  • The third attempt takes place after 15 minutes.
  • Each additional attempt is made every 30 minutes.
  • The first delivery delay notification is generated after 6 hours.
  • The delivery is stopped after 1 day.
  1. Stop the gateway role. The corresponding settings are saved in the file “Gateway Role.config” in the directory “C:\ProgramData\Net at Work Mail Gateway\Configuration\” on all your installed gateway roles. S
  2. Search for the following line in the file:
    <netatwork.nospamproxy.proxyconfiguration ... >
  3. Add the following entry directly below this line if it does not already exist in a similar form:
    <queueConfiguration firstRetryInterval="00:15:00" secondRetryInterval="00:30:00" thirdRetryInterval="01:00:00" subsequentRetryInterval="04:00:00" expirationTimeout="3.00:00:00" sendDelayNotificationAfter="12:00:00" />
  4. Adjust the values to the desired value and save the file.
  5. Restart the previously stopped gateway role(s).

This article explains how to check database integrity and repair it if necessary.

Microsoft SQL Server Management Studio is required to do this.

    1. Open Microsoft SQL Server Management Studio.
    2. Expand the Databases menu item.
    3. Click on the database “NoSpamProxyDB” and then on New Query in the upper left area. A white window now appears on the right side. To check a suspicious database for errors, you can use the following command in SQL Management Studio:
      DBCC CHECKDB ('NoSpamProxyDB')

    The next command would then correct these errors. You must set the Restrict Access mode from MULTI_USER to SINGLE_USER under Options in the database's Properties before running the command.
    DBCC CHECKDB ('NoSpamProxyDB', REPAIR_REBUILD)

    The success is checked again with the following command.
    DBCC CHECKDB ('NoSpamProxyDB')

    No red error messages should appear in the output now. If the database could not be successfully repaired and red error messages still appear, execute the more aggressive command
    DBCC CHECKDB ('NoSpamProxyDB', REPAIR_ALLOW_DATA_LOSS)

    You should also check the success with the above command afterwards. If the database cannot be repaired, you can also create a new database via the NoSpamProxy interface. The point can be found under the node “Troubleshooting”.

    If problems with the SQL Server occur often, a defect on the SQL Server is likely.

How to change the SMTP connection properties of the gateway role

This article describes how to change the SMTP connection properties of the Gateway Role. The corresponding settings are made in the file “Gateway Role.config” in the directory “C:\ProgramData\Net at Work Mail Gateway\Configuration\”.
Copy and Paste does not work because invisible control characters are also copied.

  1. Search for the following line in the file:
    <netatwork.nospamproxy.proxyconfiguration ... >
  2. Add the following entry directly below this line:
    <smtpServicePointConfiguration maxActiveConnectionsPerEndPoint="25" maxConnectionIdleTime="00:01:00" isServicePointRecyclingEnabled="false" maximumMailsPerSession="2" />
  3. Now adjust the values to the desired value.

Please note

Before you save the “Gateway Role.config” file, you must stop the “NoSpamProxy – Gateway Role” service. Only then you can save the configuration file properly.