Thanks Stoic Joker. You put out a few facts I didn't understand. I did know that it "...only controls my personal domain with a small number of mailboxes..."
You wrote that "...a full blown Exchange implementation because it would cut too far into what I have available for experimentation. ...," but later you wrote that "It really is amazing how few resources a server OS requires when it isn't having to futz with the hardware." I'm sure you're happy with hMailServer, but I'm wondering hypothetically if Exchange is feasible for you if you ignore the modest (for a few years old setup) cost and curtail or batch erase the logs on a small home setup like this.
You wrote that "...a full blown Exchange implementation because it would cut too far into what I have available for experimentation. ...," but later you wrote that "It really is amazing how few resources a server OS requires when it isn't having to futz with the hardware." I'm sure you're happy with hMailServer, but I'm wondering hypothetically if Exchange is feasible for you if you ignore the modest (for a few years old setup) cost and curtail or batch erase the logs on a small home setup like this.
Quote
That must be one hell of a calendar! cheesy I do believe it is safe to say that Virtualization is by far my favorite technology to play with.I ended up with the system mostly to have fun with virtualization. I've become addicted to the Calendar since, even though it's just keeping my doctor's appointments and reminding me when to eat my health foods mostly. If something goes wrong I'm going to buy a subscription to Exchange email somewhere. Like you, my setup is strictly for my home network lab, but definitely no MSDN subscriptions connected. Maybe a deploy or two every few years, or a network tool to try, and my WSUS (Windows Updates).
Quote
I don't think there is any MS OS that can't be run on Hyper-V - I've got a copy of DOS v6.22...Wow! I always thought those compatibilities lists at Microsoft were the Tablets of Moses, Volume 3, especially after reading forums on different hurdles after a bunch of searches over the years.
Quote
... a list of caveats a mile long with self hosting..., ...your ISP allows it...I doubt I'd consider a mail server without a static IP, which requires a Business package from my provider. There's at least one way around that with DynDns, but again my novice senses tell me to go with the true static in this case.




...And that distinction will have a huge effect on the log size. This is one of a multitude of reasons why Exchange tends to require a lot of system resources.



