Installing NoSpamProxy on a cloud service

NOTE: You must have a valid software maintenance contract to use the TCP Proxy.

It is possible that for cloud-based systems, e.g. Microsoft Azure, port 25 is blocked by the provider. However, port 25 is required for sending emails, and port 25 being blocked prevents NoSpamProxy from operating on such a system.

We offer a solution in the form of our TCP proxy. This system can be activated in NoSpamProxy as described below. Each outbound connection is routed to a routable IPv4 address on the TCP level through the TCP proxy for NoSpamProxy. The emails will be sent from the server via port 443 to the TCP proxy and from there via port 25 to the recipient system.

NOTE: Before you activate the TCP proxy via PowerShell, you must remove the old TCP proxy to be activated via the configuration file (if you have used it). See Removing the "old" TCP proxy.

1. Place the Root CA certificate in the Microsoft certificate store in the computer account under Trusted Root Certification Authorities > Certificates on the server with the Gateway Role.
2. Enter the following command in PowerShell:
   Copy

   Ignoring certificate errors

   Connect-Nsp -IgnoreServerCertificateErrors -Credential (Get-Credential)

3. Depending on your environment, enter the following commands in PowerShell:

   • If you wish to send emails directly to external recipients:

     Copy

     Outbound connector (direct)

     Set-NspOutboundSendConnector -Smtp -TcpProxyMode UseCustom -TcpProxyHost "proxy.nospamproxy.com" -TcpProxyPort 443 -Name "Standardkonnektor für ausgehende E-Mails"

     Copy

     Inbound connector (direct)

     Set-NspInboundSendConnector -Smtp -TcpProxyMode UseCustom -TcpProxyHost "proxy.nospamproxy.com" -TcpProxyPort 443 -Name "Standardkonnektor für eingehende E-Mails"

   • If you wish to send emails to external recipients via Office 365:

     Copy

     Outbound connector (Office 365)

     Set-NspOutboundSendConnector -Office365 -TcpProxyMode UseCustom -TcpProxyHost "proxy.nospamproxy.com" -TcpProxyPort 443 -Name "Office 365"

     Copy

     Inbound connector (Office 365)

     Set-NspInboundSendConnector -Office365 -TcpProxyMode UseCustom -TcpProxyHost "proxy.nospamproxy.com" -TcpProxyPort 443 -Name "Office 365"

   NOTE: The name of the connector may vary; if necessary, you can look up the name via the NoSpamProxy Command Centre.

   NOTE: The TcpProxyMode parameter has been available since version 15.5.

4. In the NoSpamProxy Command Center under Configuration > NoSpamProxy components > Gateway Roles edit the appropriate Gateway Role and change the value for SMTP Server Name to the value outboundproxy.nospamproxy.com.

Set-NspAdvancedSettings -GlobalOutboundTcpProxyHost "proxy.nospamproxy.com" -GlobalOutboundTcpProxyPort 443

Set-NspOutboundSendConnector -Smtp -TcpProxyMode UseGlobal -Name "Standardkonnektor für ausgehende E-Mails"

Removing the "old" TCP proxy

To remove the old TCP proxy to be activated via the configuration file, proceed as follows:

1. Stop the Gateway Role via the NoSpamProxy console or the Windows services
2. Open a text editor using administrative rights on the system where the Gateway Role is installed.
3. Open the configuration file "Gateway Role.config" from the directory C:\ProgramData\Net at Work Mail Gateway\Configuration.
4. Search the file for <smtpServicePointConfiguration.
5. Delete the following attribute from it:
   Copy

   Attribute to be deleted

   isProxyTunnelEnabled="true" proxyTunnelAddress="

6. Save the file and close the editor.
7. Start the Gateway Role.