Mike,
We feel your pain.. you're talking about an IMail limitation that has
bugged countless admins for years. IMail will bind all IPs on the machine
to listen to the port you set for web messaging, so if you're forced to
dual-purpose a machine, you've got no choice but to serve IMail's web
messaging on a non-standard port.
As a way to prevent confusion for your users, you can easily configure a
web site for each domain, like "mail.domain.com", in IIS under the Home
Directory tab of the site properties, that redirects to a URL, like
"http://mail.domain.com:8383";, so that your users will never know the
difference unless a)they look at the resulting URL, or b)they're behind a
firewall that blocks the nonstandard port.
Ron Hornbaker
President/CTO
. . . . . . . . . . . . http://humankindsystems.com
. . . . . . . . . . . . w e c o d e. w e c a r e.
. Come say Hi to us at ISPCON in Las Vegas, October 9-11, booth #3620!
. http://www.ispcon.com/fall2001/attend-exhibitordetail.asp?X_ID=1792
. http://AnswerTrack.com - eCRM email tracking solution
. http://KillerWebMail.com - the name says it all
. http://hksi.net/products - EZSignUp, You'veGotIMail!, etc...
. http://hksi.net/testimonials - 1,698 admins can't be wrong
> -----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/
