Hello Jay.

03 Dec 02 00:11, you wrote to me:

 MG> SH>> I'm inclined to agree with Microsoft.  We have at least 50
 MG> SH>> systems running Wiundows 2000 at my employer's workplace and
 MG> SH>> it does not have these problems.

 MG>> And I run NT 4.0 here, and run web, e-mail and FTP servers with it.
 MG>> It's a /very/ secure system.

 JF> Which email server do you run with nt-4... ?  Exchange?

I don't run IIS, so I use the Mercury/Win32 e-mail server. It's completely
free, the author only charges for the manuals and technical support, but
there's plenty of online help available as well. It's a pretty decent
e-mail server, with a lot of features, but it won't run as a service,
unless you use a utility (which came with the NT Resource kit) called
SRVANY that allows you to run any program as a service. I don't have remote
users on my NT system, and I don't have any trouble just running it in the
background, so I didn't bother looking for that utility yet.

It will work with a dynamic IP, provided you use a DNS subdomain/IP
redirection service, and enter your subdomain in the config. It will also
support multiple domains.

 JF>  Also, how do you feel about the discontinued support for nt-4 ?

Well, since Win 2000 is in reality Win NT v5.0, I guess it was inevitable.
I must say, for it's age (released in 1996) it sure was advanced for it's
time. After struggling with mail hubbing and 24/7 BBS stuff for a few years
with Win 95 and then Win 98, I now sure wished I'd started out with NT in
the first place. I tried Linux along the way, and I liked it, but BBSing
under it can pretty get complicated, while NT is a little more familiar,
and older BBS stuff will still work under it.

The way Microsoft does things, I'd say we've been pretty lucky that they've
supported it for as long as they did...


--- GoldED/386 3.0.1-dam3