Question Locked

Subdomain Windows

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
My company has a partner organization that resells our service. They have requested that it appears to their customers that they are contacting them and not us. I need to setup a sub-domain I think. They are mostly concerned about email and are happy to have something like partner.mydomain.com for email addresses. To me, that doesn't really do much to disguise what company people are contacting, but it is what they asked for. I have an AD 2003 and Exchange 2003 setup for my primary domain and I want to avoid any hardware or licensing costs whenever possible. What are my options here? Any suggestions are appreciated as I have no experience setting up a subdomain.

5 replies

by churdoo

You don't have to set up a subdomain or child domain if all you're asking about is email, and especially if it's mainly inbound email.

What you're talking about is merely updating your Recipient Policies (ESM / Recipients / Recipient Policies) to add the new email domain @partner.mydomain.com to your exchange organization, Rebuild the Recipient Update Service, and make the requisite DNS changes of the mydomain.com zone, i.e. adding MX records for partner.mydomain.com directing inbound email to your exchange server.

Since you're not adding mailboxes, there's no licensing implication.

Check this article http://support.microsoft.com/kb/319201 and also check out http://www.msexchange.org as a great resource for MS Exchange. Keywords related to what you're asking are "Exchange Recipient Policies"

by billc124

I do need to do outbound email as well. Actually the majority of the mail we send is outbound but inbound is very important as well. What does that do to the complexity.

by churdoo

Well I may have been unclear about the inbound versus outbound part. You can do as much inbound or outbound email that you want.

The Recipient Policy which I mentioned earlier, has several jobs:
a) defines what email domains your exchange organization receives email for
b) defines any number of automatically generated email addresses and/or alias' for a given mailbox
c) defines the "primary email address" which appears as the sender email address of outbound email

So the comment relative to inbound/outbound is pertinent in this way: you can have any number of email domains and/or alias' for which inbound email will wind up in a given mailbox, however, of course an outbound email will only advertise one email address as the sender, and in exchange this is called the Primary email address.

In your situation, I'm assuming that you have your own comany domain that you use as your email domain, call it @yourcompany.com. Per your partner company request however, presumably they would want replies to inbound partner requests have a sender email address of @partner.theircompany.com, if that makes sense.

So in Exchange, although the same user mailbox can RECEIVE email addressed either way, that mailbox user will send OUTBOUND email as johndoe@yourcompany.com OR johndoe@partner.theircompany.com, whichever is set as the Primary email address, not both. There is no way in Exchange to toggle, say a "send as" setting as you may have seen in some email clients.

To manage Exchange in your environment so that your company does not lose its own identity to the partner email domain, you would have to
a) use separate email boxes for partner email use, and manage the multiple mailboxes either with OWA or separate Outlook profiles, etc.
b) assign a team of users that assume the partner identity and have them handle all partner communication.

Hope this clears things up.

by billc124

I did know about the Primary Email Address and you confirmed what I was telling the person who asked this from the beginning, that we would need two mailboxes in order to accomplish what they are asking. I appreciate your input.

This discussion is closed to new replies.