New Division email address setup in the existing domain exchange 2007 / Outlook 2010

Hello Experts,
Our company is currently putting out a new product line which and purchased a new domain to go along with it.

I'm trying to incorporate the new brand into our existing company domain.
The way I currently set it up is that the mx records point to our mail server which then has SMTP aliases which I've added to each user who is going to be working as a part of that new company. It works fine for us to receive emails from but that's not enough since we don't seem to be able to send emails from that domain (only receive)

I'm looking for the ideal setup for this.

Here's a quick overview:
Current domain (currently setup in exchange as the default for all users)  
New domain (some of our current domain users will also be a part of this)

So users in also need to have an "" email address which they are able to send and receive from, also it would be a much nicer setup if they also had their own inbox instead of sharing the inbox for al domains.

What do you suggest in order to accomplish this setup?

Any suggestions would be helpful.
Who is Participating?
Jamie McKillopConnect With a Mentor IT ManagerCommented:

Due to the way Exchange routing works, you can only send as the primary SMTP address on an object. My suggestion to accomplish what you want to do is for each user that needs to be able to send as a secondary address, setup a distribution group and move the secondary address as the primary address on the group. You would then add the user as the only member of the group. You would then need to assign the send as right on the group to the user, using the following command:

Add-AdPermission "Group Name" -user "User Name" -AccessRights
extendedright -ExtendedRights "send as"

This is the native Exchange way to do it and I realize it is a bit clunky. There is a third party tool that allow you do do it more elegantly, if you are willing to pay:

ntmyfltAuthor Commented:
Hi JJ,
Thanks  for your post. We've decided to move forward with an Exchange 2013 upgrade since the platform seems to support multi-tenant.
All these workarounds are like you said.. a bit "clunky".

Thanks for your suggestions.
ntmyfltAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for ntmyflt's comment #a39628894

for the following reason:

The only response given from the experts wasn't the solution I used to solve this issue.
Jamie McKillopIT ManagerCommented:
Exchange 2013 doesn't function any differently. Multi-tenant has nothing to do with being able to send as a non-primary SMTP address. My answer #a39616460 provides the solution to the question you posed. Please assign points.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.