> you can't put imail on port 80 if you also have IIS running (and > want websites on 80 as well).
Okay, have a seat, because you can, but only on Win2K+. (This is previously undiscovered info, as far as I know.) The general overview: add a new IP address *after* IWEBMSG has started and bind IIS to that IP. This process can certainly be scripted, though I did it ad hoc. 1. Set socket pooling off in IIS (one-time change, very important): cscript adsutil.vbs set w3svc/disablesocketpooling true 2. Set up IIS to selectively bind to an IP that is not yet on the machine. Do not start the IIS web service. 3. Start IWEBMSG. 4. Using netsh (my preference; you could probably use the GUI, too, but that won't be scriptable), add the new IP address to the machine. 5. Start the IIS web service. It is CRUCIAL that you NOT double-check for the presence of IWEBMSG on the new IP address before starting IIS! That seemingly innocent step will make IWEBMSG dynamically bind to the new IP address. Don't do it! Start IIS, *then* feel free to check that IIS owns that socket. Obviously, those that restart IWEBMSG every night will need to have a more robust startup/shutdown procedure, but the steps will work again during the same session. YMMV, but I think this one's a keeper. Oh, and it also works for MS SMTP, with a little more trickery--I'm pretty psyched about that one. Now go tell the world. -Sandy 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 the Knowledge Base for answers to frequently asked questions: http://www.ipswitch.com/support/IMail/
