Using a Proxy Server with the Hurricane MTA Server

Applies to HMS Version: 1.0+

When a Hurricane MTA Server is sitting behind a proxy server, a
configuration change is required for it to actually use that proxy.
This issue is often first noticed when initially placing an HMS behind
a proxy server and running into issues with contacting our licensing
server. In this scenario, communications between the Hurricane MTA and
our licensing server are blocked since the Hurricane MTA is not
configured to send through the proxy, and one or more
licensing-related error messages or alerts are generated.

Solving the issue is a two-step approach:

CONFIGURING THE HMS CONTROL PANEL

In the Hurricane MTA Server installation directory, update the
www/web.config file with the same setting:

<system.net>
<defaultProxy>
<proxy proxyaddress="http://127.0.0.1:8888" />
</defaultProxy>
</system.net>

In this example, the configuration points to a local Fiddler proxy
server [http://www.telerik.com/fiddler] (great for testing). Configure
the proxy address appropriately for the proxy server you want to use.
Once the change is made, restart the Hurricane HTTP Service or restart
the control panel web application in IIS. This will load the proxy
settings, and the licensing page should now work in the Hurricane MTA
control panel.

CONFIGURING THE HMS CORE SERVICES

In the Hurricane MTA Server installation directory, update the
bin/HurricaneServer.exe.config file with this:

<system.net>
<defaultProxy>
<proxy proxyaddress="http://127.0.0.1:8888" />
</defaultProxy>
</system.net>

Again, this configuration points to a local Fiddler proxy server
[http://www.telerik.com/fiddler] and you will want to change this to
the address for your own proxy server. Once the change is made,
restart all Hurricane services in order to load the proxy settings. On
the next licensing check, the MTA should be able to reach our server
successfully.

NOTICE: UPGRADING OR REINSTALLING THE HMS

Please note that currently changes to the app.config and web.config
files for the Hurricane MTAs do not persist between installations,
since these files are overwritten during the installation or upgrade
process. Keep a copy of your customized app.config or web.config files
elsewhere and make reapplying those customizations part of your
upgrade process.