<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Sharing a domain between two Exchange orgs</title><link>http://blogs.technet.com/dlemson/archive/2004/03/03/83304.aspx</link><description>Luke asks : I am in the process of migrating from Exchange 5.5 to Exchange 2003 for a company that has multiple small (less than 5 users) branch offices. They want to migrate slowly, so here's my dilemma: The current Exchange 5.5 will still be active</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Using IIS SMTP Server as a generic mail receiver</title><link>http://blogs.technet.com/dlemson/archive/2004/03/03/83304.aspx#83315</link><pubDate>Wed, 03 Mar 2004 20:30:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:83315</guid><dc:creator>You Had Me At EHLO...</dc:creator><description /></item><item><title>re: Sharing a domain between two Exchange orgs</title><link>http://blogs.technet.com/dlemson/archive/2004/03/03/83304.aspx#83324</link><pubDate>Wed, 03 Mar 2004 17:42:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:83324</guid><dc:creator>Mike</dc:creator><description>Unfortunately this KB isn't totally accurate.  Step 6 states:  &amp;quot;...Because the main SMTP-address of the Windows 2000 contacts is @organization.org, recipients in the Organizations B through D appear outbound with this SMTP address.&amp;quot;  This doesn't appear to be true.&lt;br&gt;&lt;br&gt;Mail from &amp;quot;Organization B&amp;quot; routes through Org A, but the from address still ends up as user@subb.organization.org for internet recipients.  Very bad if either subb.organization.org does not have a valid MX record on the internet or you need to have a unified e-mail address presented to the public.&lt;br&gt;&lt;br&gt; </description></item><item><title>re: Sharing a domain between two Exchange orgs</title><link>http://blogs.technet.com/dlemson/archive/2004/03/03/83304.aspx#83336</link><pubDate>Wed, 03 Mar 2004 17:56:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:83336</guid><dc:creator>Luke Edson</dc:creator><description>David,&lt;br&gt;&lt;br&gt;Wow, thanks for such a speedy answer, I had looked at that MSQ article, but let me explain further: &lt;br&gt;&lt;br&gt;There are two domains, A, &amp;amp; B. They have a two way trust between them. - The current Exchange 5.5 server is receiving all mail for domainA.com, the Exchange 2003 server is receiving all mail for domainB.com - I am collapsing domainA into domainB; that means the recipients of domainA will end up with two SMTP addresses, @domainA.com &amp;amp; @domainB.com&lt;br&gt;&lt;br&gt;The clients will be migrated over from domain A to B over time, so there will be a period where the Exchange 2003 server will be receiving mail for domainA only for a couple of recipients, &amp;amp; needs to forward all the rest of the recipients (for domainA) to the Exchange 5.5 server.&lt;br&gt;&lt;br&gt;What I'm looking for is some way of the SMTP service to say, &amp;quot;oops, user3@domainA.com has to get forwarded to the Exchange 5.5 server&amp;quot; (They are both accepting &amp;amp; sending domainA.com emails, but only the Exchange 2003 server has the external MX record pointing to it.)&lt;br&gt;&lt;br&gt;In other words, the Exchange 2003 server is hosting the mailboxes of user1@domainA.com &amp;amp; user2@domainA.com. The Exchange 5.5 server is hosting the mailboxes of user3@domainA.com &amp;amp; user4@domainA.com. Since they’re not in the same domains, I can’t set them up to be able to talk to each other to let each other know which one is hosting a specific mailbox.&lt;br&gt;</description></item><item><title>re: Sharing a domain between two Exchange orgs</title><link>http://blogs.technet.com/dlemson/archive/2004/03/03/83304.aspx#83358</link><pubDate>Wed, 03 Mar 2004 18:31:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:83358</guid><dc:creator>Luke Edson</dc:creator><description>Thanks David,&lt;br&gt;&lt;br&gt;I had a mental block as to what my problem was, &amp;amp; how to fix it, but after reading the MSQ 315511 article more in depth, &amp;amp; trying it out, that's solved the problem!&lt;br&gt;&lt;br&gt;Thanks again.</description></item><item><title>re: Sharing a domain between two Exchange orgs</title><link>http://blogs.technet.com/dlemson/archive/2004/03/03/83304.aspx#83986</link><pubDate>Thu, 04 Mar 2004 19:22:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:83986</guid><dc:creator>Ralf</dc:creator><description>The more wider used KB-Article for SMTP Address Sharing is &lt;a target="_new" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;321721"&gt;http://support.microsoft.com/default.aspx?scid=kb;en-us;321721&lt;/a&gt; (mainly method 1)&lt;br&gt;&lt;br&gt;and Mike is correct - if the sub-Org does not have org.com as the primary SMTP Address for its recipients - then either Address rewriting like for Exchange 2003 in &lt;a target="_new" href="http://www.microsoft.com/downloads/details.aspx?FamilyId=C29487EE-EF0A-49F6-A205-F23E0A98F794&amp;amp;displaylang=en"&gt;http://www.microsoft.com/downloads/details.aspx?FamilyId=C29487EE-EF0A-49F6-A205-F23E0A98F794&amp;amp;displaylang=en&lt;/a&gt; or You will have to setup MX records for the subdomains</description></item><item><title>re: Sharing a domain between two Exchange orgs</title><link>http://blogs.technet.com/dlemson/archive/2004/03/03/83304.aspx#84025</link><pubDate>Thu, 04 Mar 2004 20:27:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:84025</guid><dc:creator>Mike</dc:creator><description>Hmmm, didn't realize that rewrite tool existed, thanks for the link.  I'm assuming it won't work on Exchange 2000.&lt;br&gt;</description></item></channel></rss>