Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm in the process of moving two law firms to hosted Exchange 2007, a service that the consulting company I work for offers. Let's call these two firms Crane Law and Poole Law. These two firms were ONE firm just six months ago, but split. So they have three email domains:

Old Firm: New Firm 1: New Firm 2:

Both Firm 1 & Firm 2 use email addresses, as for the other two domains, only people who work at the respective firm use that firm's domain name, natch.

Currently these two firms are still using the same pre-split internal Exchange 2007 server, where MX records for all three domains point.

Here's the problem. I'm not moving both companies at the same time. I'm moving Crane Law two weeks before Poole Law. During this two weeks, both companies need to be able to:

  1. Continue to receive emails addressed to
  2. Send emails between firms, using and accounts

I also have a third problem:

  1. I'd like to setup all three domains in my hosting infrastructure way ahead of time, to make my own life easier

What would solve all my problems would be, if there is some way I can tell Exchange 2007, even though this domain exists locally forward on the message to the outside world using public MX record as a basis for where to send it (or if I could somehow create a route for it statically that would work too).

If this doesn't work, to address points #1 when I migrate Crane Law, I will delete all references locally to on their current Exchange server, and setup individual forwards for each of their mailboxes to forward to our hosted exchange server. This will also take care of point #2, since the won't be there locally, when tries to send to, public MX records will be used for mail routing decisions and go to my hosted exchange. The bummer of that though is, I won't be able to setup ahead of time in hosted Exchange, will have to wait to do it day of :(

Sorry for the long and confusing post. Just wondering if there is a better or simpler way to do what I want? Three tier forests and that kind of thing are out, this is just a two week window where they won't be in the same place.

share|improve this question

migrated from Nov 18 '11 at 8:51

This question came from our site for computer enthusiasts and power users.

Hi DomoDomo. Welcome to Super User. Your question is interesting but, as it's worded, is quite specific to a particular scenario and risks being closed as "too localised". Any chance you can make it generic and thus useful to others for future reference. All the best. – Linker3000 Nov 17 '11 at 22:55
Do you control the hosted Exchange server completely or are you reselling for someone else? – Driftpeasant Nov 18 '11 at 20:33
Yea saw sorry the concepts here are generic, but I thought being specific would make them easier to understand. – DomoDomo Nov 19 '11 at 0:51
@Driftpeasant I have complete Exchange server control, can write any crazy transport rules or anything else I need to. – DomoDomo Nov 19 '11 at 0:51

Point your Mx record of so that mails will be delivered to that domain.

Create an accepted domain for the other two domains and with internal relay.

Create a send connector with addressspace * and another sendconnector with addressspace *

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.