Seems like everyone is putting a "web interface" on their utilties lately! This, of course, requires that IIS be installed for it to work correctly. Well the new GFI mailsecurity 9 (still in Beta) does just that. Here is my story:
My guess is I am in a pretty unusual situation right now. However, as a long time ISA user, I am guessing that this problem will come up more often in the future. Here goes:
I am running ISA 2004 SP1 on W2K3 SP1. It is trihomed. I have numerous sites published from my external IP address to the DMZ etc.
When IIS is installed on a W2K3 box it attaches itself to every IP with regard to http on port 80. This effectively wrecks any publishing performed on ISA. It also stops the autodetect via DNS (which require port 80 on the private side IP).
So, to fix it one must use the httpcfg util to disable the socket pooling and then use httpcfg to enable port 80 listening on an IP address that will not interfere with the published sites and/or the autodiscovery.
IT WORKS! Except: 1. When an email form is sent from the quarantine it references the NetBIOS name, which, since we disabled http listening on the internal IP, fails. Thus the form fails when an option is chosen (approve, delete etc.).
2. When you click on the link to the URL as it is installed in the start menu and/or the desktop (http://netbiosname/mailsecurity it fails. This is easy to get around by simply changing the url to http://listeningIP/mailsecurity
Being able to define the Host name during the install to be something other than the hostname of the server would fix it. OR is there a single place that I can force the Host name referenced by Mailsec to affect it across the board, post install?