NoSpamProxy components

Here you configure the connections between the individual components of NoSpamProxy. Information on the selection of components can be found under Component selection.

Connections to individual components of NoSpamProxy

Intranet Role

The intranet role contains the entire configuration of NoSpamProxy and manages the cryptographic keys. See Intranet Role, Infrastructure recommendations.

Gateway Role

The Gateway Role is the actual core of NoSpamProxy. It can either be installed on the same server as the Intranet Role or on a different server. See Gateway Role, Infrastructure recommendations.

web portal

The Web Portal allows users to store passwords for PDF mail and to write replies to PDF mails. If you have licensed large files, users can transfer large files via the Web Portal. To build a highly available system, the Web Portal can be installed on multiple servers. See Web Portal, Infrastructure recommendations.

NOTE: Content filters are available if NoSpamProxy Encryption or NoSpamProxy Large Files are licensed.

NoSpamProxy Command Center

The NoSpamProxy Command Center is the user interface of NoSpamProxy. The NCC is used for the central management and administration of NoSpamProxy. See NoSpamProxy Command Center.

NoSpamProxy Web App

During setup, the NoSpamProxy Web App is installed as part of the Intranet Role. The Web App offers further functions via a web-based interface, such as additional search options for message tracking. You can also access the Disclaimer configuration. See Web App, Message tracking (Web App).

Further components


Here you make changes to the connection to the database of the corresponding role. See Databases, Infrastructure recommendations.

Configuration files for the roles

The configuration of NoSpamProxy is stored in an XML file on the server. This file can also be backed up using conventional backup software. However, NoSpamProxy writes this file back when the configuration is changed, so that a conflict can occur here during simultaneous backup.

NoSpamProxy creates the new file as a temporary file while writing the configuration, renames the original file, for example to GatewayRole.config.backup. Only then does NoSpamProxy rename the temporary file to GatewayRole.config. With a normal, file-based backup, you have therefore always backed up either the most recent copy or the version of the configuration that was changed shortly before.

NOTE: We recommend that you save this file before making any changes to the configuration. This allows you to return to the previous state at any time.

Default paths of the configuration files

Gateway Role %ProgramData%\Net at Work Mail Gateway\Configuration\GatewayRole.config

Intranet Role %ProgramData%\Net at Work Mail Gateway\Configuration\IntranetRole.config

ServerManagement Service %ProgramData%\Net at Work Mail Gateway\