Al
Wed Feb 07 16:30:13 CST 2007
No, the creation of a routing domain is something you'll do manually.
Secondary proxy addresses and possibly some DNS entries or hard-coded routes
should take care of it.
What you want to have happen is that when a message is sent to a user in
environment A, the MTA looks it up in the directory, sees that it is
responsible for that domain, and then realizes you have a custom recipient
for it that has a secondary address of user@routingdomain.com. It then
sends the message there for final disposition. The reverse is the same: a
user submits a message in environment B and submits it. The transport will
look up the recipient, realize it's authoritative for the domain, and then
realize that it's a contact and send the message to the secondary proxy
address.
To do this, the 200x side has recipient policies which will let you easily
configure the secondary addresses en masse. For 5.5 this is done with CSV
files.
The ADC in that configuration will replicate the contacts and such, but it's
up to you to configure the routing. There should be additional information
about the interorg configuration at
http://www.microsoft.com/exchange/library . Something like scenario or
deployment docs.
Al
"Mike" <no@no.com> wrote in message
news:u3rZJTmSHHA.3428@TK2MSFTNGP04.phx.gbl...
> Thanks for the response, Al.
>
> It would be an InterOrg connection agreement.
>
> How would you create the routing domain? Isn't it automatically created
> once the ADC is in place?
>
> Thanks
>
>
> "Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
> news:%23gZG4vYSHHA.3316@TK2MSFTNGP02.phx.gbl...
>> What type of connection agreement topology is it?
>> Interorg?
>>
>> Generally, the mail will be able to flow as long as there is connectivity
>> and directory entries (i.e. routing information) that enable it. Be
>> careful though, because it's not magic. You'll need to have a routing
>> domain especially if you intend to keep the same domain name. For
>> example, if you have company.com as your primary address space that
>> accepts mail from the internet, you'll want to have an internal routing
>> domain that allows for routing between 5.5 and 2k3. That's regardless of
>> the internet routing being involved. If you don't do that, then you'll
>> have a problem because the first hop would consider itself authoritative
>> for the domain but would not have a destination to send it to.
>>
>> Make sense?
>>
>>
>> "Mike" <no@no.com> wrote in message
>> news:eGTJYUYSHHA.5100@TK2MSFTNGP06.phx.gbl...
>>> I'm planning an upgrade from Exchange 5.5 in an NT4 domain to Exchange
>>> 2k3 in a new 2k3 forest.
>>>
>>> What happens to incoming SMTP email during the migration? Will the ADC
>>> take care of routing mail to the appropriate server and user mailbox if
>>> both servers currently hold mailboxes? I assume SMTP must continue to
>>> flow to the Exchange 5.5 server until all mailboxes have been moved to
>>> the 2k3 server.
>>>
>>> Any help is greatly appreciated.
>>>
>>
>>
>
>