That sounds like a fine patchwork solution for the time being, but I wouldn¹t suggest you plan to rely on it for long. Using CSVDE on a regular basis will eventually evolve into users calling for problems with missing recipient, which will lead to running your imports nightly, or even more often. Eventually imports and exports wind up breaking / masing / missing something and lead to grief you probably don¹t need. If you put a trust in place, you could then look at migrating mailboxes to a single org (presumably DEF.COM) and continue to use the same user IDs by using the associated external account flag. See http://www.microsoft.com/technet/prodtechnol/exchange/guides/WorkingE2k3Stor e/8c4befe3-3815-4b6b-a759-1e5a2878499d.mspx?mfr=true This still isn¹t a long term solution (nor was it ever intended to be) but it gets around all sorts of potential problems with GAL syncs, repliability, and delegation. Eventually, though, you need to consider a long-term approach, unless you are anticipating a quick divestiture. Rick From: MAHADEVAN Subramanyan <SMahadevan@xxxxxxxxxxxx> Reply-To: <exchangelist@xxxxxxxxxxxxx> Date: Thu, 9 Nov 2006 12:39:40 +0530 To: <exchangelist@xxxxxxxxxxxxx> Conversation: [ExchangeList] Re: Exchange Multiple forest scenario... Subject: [ExchangeList] Re: Exchange Multiple forest scenario... Hi Prabhakar, Thanks for your input? Yep? It is Win2k3 Native mode? But do we need trust for this? If so why is it needed? We have just planed to use the Exchange in a Hub & Spoke topology for relaying the mail for multiple organizations. We can export and import the users using CSVDE tool on regular basis or in future we have plans to use IIFP? Regards, Mahadevan From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Prabhu Kamuni Sent: Thursday, November 09, 2006 11:56 AM To: exchangelist@xxxxxxxxxxxxx Subject: [ExchangeList] Re: Exchange Multiple forest scenario... Maha, It seems u r not missing, but i have a Question ? Is it Win2k3 Native ? is there any trust relationships between forests? (ABC &def) you mean to say you will be creating all the ABC.com user objects as contacts in DEF.com? Yes everything should work in this case....(MX record is there,Receipnent policy is in place,conatcts info is there) Please correct me experts if am wrong ? Thanks in adv Thanks Prabhakar,Banglore. INDIA. ----- Original Message ---- From: MAHADEVAN Subramanyan <SMahadevan@xxxxxxxxxxxx> To: exchangelist@xxxxxxxxxxxxx Sent: Thursday, November 9, 2006 11:12:35 AM Subject: [ExchangeList] Exchange Multiple forest scenario... Hi, I have a question... Assume that a company is acquiring another company which has its own Forest and Separate Exchange organization. The SMTP domain ID for the acquired company is @ABC.COM and the Existing SMTP domain ID in this company is @DEF.COM. We have added DEF.COM to ABC.COM through Recipient Policies and have set DEF.COM as the primary address so that all the Reply to address will be DEF.COM. Now the requirement is all the mails which are sent to users in the recently acquired company should be relayed through the Mail Server at DEF.COM. After setting up the proper MX records, is it enough if we have the contact objects for the ABC.COM users and a SMTP connector which will forward the mails to the mail server in the ABC.COM domain? Plz advise if I am missing out something? Regards, Mahadevan Confidentiality Statement: This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by return email. Everyone is raving about the all-new Yahoo! Mail. <http://us.rd.yahoo.com/evt=42297/*http:/advision.webevents.yahoo.com/mailbe ta> Confidentiality Statement: This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by return email.