Waht you are asking for is called Exchange Hosting...
This is possible...
Raghu
Main Topics
Browse All TopicsHello,
I would like to host mutiple seperate SMTP domains on my exchange 2003 server. These are not child domains, but TLDs. I need each to be completely seperate, i.e. each domain's users need to perceive that they're on their own server. Is that possible? How?
Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: SembeePosted on 2006-07-02 at 07:55:03ID: 17026840
Almost impossible to do.
ehost.net will not work.
There are three issues.
1. The major issue is outbound SMTP. You cannot control which SMTP virtual server is used for outbound email.
2. Windows domain name choice. This will always appear in the Outlook configuration.
3. OWA access. No self respecting hoster will do OWA without SSL. That would mean a virtual web site for each domain. However you can't move RPC over HTTPS to another web site easily, so it would be a moot point.
What most hosters will do is use a generic domain name - one that isn't attached to any client.
The Windows domain will be domain.local
The external domain name for MX records etc will be something general.
Remember that if you are going to support Windows Mobile devices, you can't use wildcard SSL certificates, so even doing something like https://clientname.exchang
Simon.