Hi all I have the following situation: There is one company in three different locations - Europe, USA and Asia. Today all three locations have their own forest and their own mail systems. Europe use an Exchange Server 2003 and the smtp namespace company.com USA use an Exchange Server 200x and the smtp namespace company-us.com Asia use a third party email system and the smtp namespace company.hk The goal is that all three locations are using the same smtp namespace which is company.com. Now I know the scenario with contacts: - The mx record points to the Exchange Server in Europe - In Europe I create contacts for every US user with a company.com smtp address and a target address like company-us.com - The same I do for Asian users with a company.hk smtp address and a target address like company.hk. - In Europe I create an smtp connector for USA which sends company-us.com to the US Exchange Server - In Europe I create an SMPT connector Asia which sends company.hk to the Asia Exchange Server - The US Exchange Serverhasthe non authoritative domaincompany.comand a send connector for company.com which is pointing to the Exchange Server in Europe - Assuming for the mail server in AsiaI can set the company.com namespace as non authoritative as well and I can create a send connector for company.com which is pointing to the Exchange Server in Europe Is there another, easier way to achieve the goal? Any hint would be appreciated. Thanks and regardsPeter

If it were up to me I would do a domain collapse for each domain. One empty forest root and then three child domains. Deploy Exchange 2007 in the new environemnt and then mail servers in each child domain. The Exchange servers will all be aware of the other exchange servesr in the entire org.It will be more work but in the long run managment of both Exchange and AD will be easier.SF - MCITP:EMA, MCTS

Hi,Do you see the artile about How to share an SMTP address space in Exchange 2000 Server or in Exchange Server 2003http://support.microsoft.com/kb/321721That is the standard solution without redesign the topology of the current deployment that Bardapony suggested.ThanksAllen

Hi BardaponyThanks for your answer.Toredisign the topology will notbe accepted,so this is not a solution in that case.RegardsPeter

Hi Allen Thanks for your answer.Method 2: "Share the SMTP address space by using contacts to redirect e-mail to a remote e-mail system" is what I was talking about.With method 1 "Share the same SMTP address space with a different e-mail system" - I have a little problem. Let me try to explain how understand it: Like it is described in KB321721, unresolved recipients from the first e-mail system are sent to the next e-mail system and so forth. Lets assume that Europe (mx record) is the first e-mail system in the chain, USA the second, and Asia the last. That means, that Europe and USA must no be authoritative for company.com and Asia has to be authoritative for, because if not, there are no NDRs. OK, now what I dont understand: In my opinion that works fine, if an external e-mail arrives or a user from Europe tries to send an e-mail to a user in USA or Asia. But what happens, if a user from USA tries to send an email to a user in Europe? The US e-mail system cannot resolve the recipient and sends the e-mail to Asia. The e-mail system in Asia cannot resolve the recipient either, and because it is authoritative for company.com it generates an NDR. I guess there is a little part in the puzzle that I am missing. Can you please explain to me how users from Asia are ableto send e-mails to Europe and USA, and USA to Europe? Thanks and regards Peter

Hi,The easiest solution is to deploy a GalSync mechanism such as IIFP, using this approach each company will have the contacts for the other companies and accordingly they will be able to send emails to them, the routing will happen because of the contacts TargetAddress and using the SMTP connectors that you will create for each specific domain.For example if US_USer1 want to send an email to EU_User1, he/she will locate EU_User1 from the GAL to send the email, Exchange will be able to route this email since there is a SMTP connector with an address space of the contact TargetAddress.Same will apply for the rest,Regards,Mohamed Baher...[MSFT]

Hi, I apologize for the delay response. That is indeed the problem. It seems that the method 1 is not the right direction. Regarding the contacts, you can try the ldifde command to export the user, then import the user as contacts into the domain.http://www.petri.co.il/using-csvde-ldifde-export-active-directory-snapshots-windows-server-2008.htmThanksAllen

Hi AllenNo problem. In the meantime I spend a little bit more time on method 2, which will be the one we will use, together with IIFP.Thanks and regardsPeter