I would suggest you use host-headers to manage the redirect. - Create a web site in IIS that runs on the IP of the domain you want to have web mail on. You can create it on the same IP and the one the actual web site is on (if you host both). Specify host header mail.thedomain.com - and let it run on port 80. It will answer to calls on port 80, but only if they are for mail.thedomain.com. - Go to the properties of this web site and on the Home Directory tab, choose A Redirect to a URL: Now type 'http://mail.thedomain.com:8383' and run your I-Mail web access on port 8383. - No need to create any pages, just point into a blank folder. - Now your users can still use mail.theirdomain.com to get to their mail. -dave ----- Original Message ----- From: "Todd Holt" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, September 26, 2001 11:45 AM Subject: RE: [IMail Forum] Help on Web Interface port problems One solution I found for this problem: Run the web server on port 80 Run the IMail server on port 8383 Create a virtual web site: www.mydomain.com/mail which has a single static page this performs a redirect to the IMail server at port 8383. Then when the users want their mail, they remember www.mydomain.com/mail which ultimately ends up at the correct place. Further, if they bookmark the webmail login page it will be the IMail server and they won't need to wait for the redirect to occur. Todd -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Anderson Sent: Wednesday, September 26, 2001 11:24 AM To: [EMAIL PROTECTED] Subject: [IMail Forum] Help on Web Interface port problems Importance: High Hello all, I decided to move our e-mail server onto the same server as our websites run on. We needed to consolidate our machines - so I had no choice but to do this. Before, our users had the enjoyment of having the ability to check their e-mail using the default port 80 which the e-mail web interface ran on previously. Our users got very accustom to using http://mail.theirdomain.com to check their e-mail. People are not used to using any other port number - furthermore, it will confuse many. The problem is, when Imail's web interface service starts, it binds port 80 to ALL the IP numbers on that server. So because of this, the IIS service cannot start - because port 80 is already bound to those remaining IP numbers. I desperately want to run our web interface on port 80 - and I don't see any reason why I can't - as each mail domain has it's own dedicated IP number. Why isn't the web interface strictly binding port 80 to THOSE particular numbers, rather than grabbing everything in sight? Thanks for any advice you all can give, Mike P.S. Running the web interface on a different port number is the very last option I want to exercise. I need to get this working on port 80. Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
