SMTP Connectors for Inter-Organisational Migration

Posted on 2007-11-19
Last Modified: 2008-07-03
I have to perform an Inter-organisational migration from Exchange 5.5 to Exchange 2003.  My initial testing allowed me to get message flow working but with each org had a different SMTP namespaces.  I have realised the in place migration will actually have the same SMTP namespace in each Org. Microsoft documentation talks loosely about creating an SMTP connector to allow message flow between the organisations but I cannot see how I am meant to distinguish routing between Orgs. Has anyone tried this or can advise want I need to configure....the model is One NT domain  connected to a New AD domain with then the 5.5 Org part of NT Dom and the new 2003 Org part of AD?  Thanks
Question by:edsp8
  • 3
  • 2
LVL 12

Expert Comment

ID: 20314376
your need to use a x.400 conector to route the messages from 5.5 to exchange 2003

Author Comment

ID: 20316389
Thanks for that, however I had already specified x500 and SMTP in ADSIEdit as directed by some MS docs. I seem to have got shared namespace working by adding routing rule for 5.5 IMS for the domain to deal with users that are in the 2003 Org.  Then in the 2003 Org applied the shared namespace to the default recipient policy.  

Expert Comment

ID: 20326488
Just about to carry out an inter-org migration.  Could you briefly list the steps that you carried out to configure the shared namespace.  My 5.5 skills are now unfortunately very rusty.  I've already created 2 subdomains and configured the relevant MX records for each Exchange Org so that they can be addressed uniquely.  I've also assigned one SMTP subdomain address to the 2003 Exchange Org with a recipient policy but at the moment am unsure where to configure this in the 5.5 Org.

I new that I shouldn't have let the Mrs ditch all my old technical books to the charity shops!

Many thanks

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Accepted Solution

edsp8 earned 0 total points
ID: 20326845
Hi Mark

Presumably you are planning a period of co-existence?   The shared namespace testing I've done is admittedly in a virtual environment so I'm currently unable to test the routing for incoming external mail between the two Exchange Orgs; some tweaking is going to be necessary and the routing of emails to 5.5 Distrubution lists from 2003 Org still needs some work.  Check this link also, 2003 focused but should help with understanding things.

On the Internet mail connector for the 5.5 server, under Connections, how are you routing outgoing mail? Via DNS or forwarding to a Smarthost?   Regardless of that, I've put in a rule or route for the shared namespace that forwards mail to the Exchange 2003 box by full FQDN, this is added on the same tab > Message Delivery > Specify by Email Domain.  I think because 5.5 internally doesn't use SMTP, if it can't send an email to because bob isn't homed on that server, it then will forward to the IMC, then because of the above rule, it routes the email to the Exchange 2003 box.   There is a need for an SMTP connector on the 2003 server,  because the recipient policy here also has as the authoritative namespace for this sever, if it can't find  in AD because she's on the 5.5 box, it will then try to use the SMTP connector to forward email.  Here the rule tells it to route to the 5.5 server.  

My setup isn't perfect yet but I 'm  pleased that I can at least deliver emails between the two.  It does also appear that the ADC needs to be stopped before running the Migration wizard to actually move a mailbox to 2003 from 5.5 and then delete the 5.5 mailbox otherwise you end up with two mailboxes representing the same person in both Directories.  You can then restart ADC for coexistence to work, the new mailbox user on 2003 should then get a contact created by your ADC connection agreement in Exch 5.5 directory.

You have probably already seen the slightly vague MS doc:   

Here there is talk of the following requirement, again you may already have seen this so appologies if telling you how to suck eggs!  

Configure the inter-organizational connection agreement whose target container is in Active Directory to include X500 addresses with replicated objects. By default, Active Directory Connector does not include X500 addresses with user objects. Use either the Active Directory Administration Tool (Ldp.exe) or the ADSI Edit snap-in to assign the values SMTP,X500 to the msExchInterOrgAddressType attribute on the connection agreement object in Active Directory.

I think it's also important to have 2 one-way connection agreements, the above doco discusses this too.

hope  that helps



Expert Comment

ID: 20329257
Thanks for the quick response mate.  I'm doing pretty much what you have been doing with VM's and am nearly at the same point as you.  I'd left off the 'E-Mail Domain' on the 'Internet Mail' tab.

Sucking eggs takes me back to my cabbage days!


Author Comment

ID: 20732665
This Question can be closed.

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

MS Outlook is a world-class email client application that is mainly used for e-communication globally.  In this article, we will discuss the basic idea about MS Outlook, its advanced features, and types of MS Outlook File formats.
In-place Upgrading Dirsync to Azure AD Connect
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question