[ExchangeList] Re: Sharing same SMTP address between two Exchange Org

  • From: <ChongJa@xxxxxxxxxxxxxxxx>
  • To: <exchangelist@xxxxxxxxxxxxx>
  • Date: Sat, 1 Apr 2006 10:19:53 -0500

This setup looks good. I had a similar setup before where we has to forward 
unknown recipients to a smarthost since Exchange did not host all accounts, so 
we forwarded out to a unix box. We didn't have recipient filtering enabled 
during the migration, was a new feature that we were unaware of at the time and 
created a big loop. Looks like your recipient filtering config is correct. The 
only thing I'm wondering is if you're going to need to use secondary smtp 
proxies for this scenario.
 
________________________________

From: exchangelist-bounce@xxxxxxxxxxxxx on behalf of Irwan Hadi
Sent: Sat 4/1/2006 3:08 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Sharing same SMTP address between two Exchange Org



http://www.msexchange.org
-------------------------------------------------------After thinking for a 
couple hours and found that connector solution
will not work, I think I got a good solution.

At First Org:
There are 3 servers, say: 192.168.1.2 (FE), 1.3 (BE), and 1.4 (BE)
At Second Org:
There are 2 servers, say: 172.16.1.2 (FE), 1.5 (BE)

So,
at First Org:
1. Set all the servers to forward emails to non-existent users to
[172.16.1.5]. Make sure recipient filter to only accept emails for
valid recipients is applied at 172.16.1.5
2. Apply recipient filter to only accept emails for valid recipients
is applied at 192.168.1.3.
3. do not apply the recipient filter to only accept emails for valid
recipients at 192.168.1.2, so that emails from Internet can still flow
in.

at Second Org:
1. Set all the servers to forward emails to non-existent users to [192.168.1.3]
2. Apply recipient filter to only accept emails for valid recipients
is applied at 172.16.1.5

Now if joe@xxxxxxxx at first org wants to send email to nancy@xxxxxxxx
at second org.
1. Exchange at first org can't find nancy@xxxxxxxx, so it forwards the
email to [172.16.1.5]
2. 172.16.1.5, found that nancy@xxxxxxxx exists, so it accepts the
email, and deliver it internally.

If joe@xxxxxxxx at first org sends an email to barry@xxxxxxxx, and
barry@xxxxxxxx doesn't exists at neither org:
1. Exchange at first org can't find barry@xxxxxxxx, so it forwards the
email to [172.16.1.5]
2. 172.16.1.5, due to recipient filter, reject email to barry@xxxxxxxx
during SMTP transaction, which causes the 192.168.1.3 server to
generate an NDR to joe@xxxxxxxxx

Somebody that has misconfigured Outlook Express, has an email of
asdf@xxxxxxxx, and sends an email to qwert@xxxxxxxxx Neither email
exists in either orgs:
1. Exchange at first org can't find qwert@xxxxxxxx, so it forwards the
email to [172.16.1.5]
2. 172.16.1.5, due to recipient filter, reject email to qwert@xxxxxxxx
during SMTP transaction, which causes the 192.168.1.3 server to
generate an NDR to asdf@xxxxxxxxx
3. asdf.com doesn't exists, so the email goes to bitbucket since the
badmail folder is history as of exchange 2003 SP1.




On 3/31/06, Irwan Hadi <ihblist@xxxxxxxxx> wrote:
> We are going to migrate our current Exchange 2003 Organization (first
> org) to a different Exchange 2003 Organization (second org). First org
> currently has around 300 users, and second org will have around 250
> users (migrated from Lotus Notes in a few weeks). We will migrate
> users from the first org to the second org after the 250 users have
> been migrated from Notes.
>
> First org currently has 1 front end, and 2 back end, while second org
> current has 1 front end and 1 back end.
> 2 back end more servers will be aded to the second org, before we
> remove first org forever.
>
> The challenges now are:
> - Both organizations will need to use the same primary email address 
> (@corp.com)
> - During migration, people in the first org will need to be able send
> email to people in the second org, and vice versa.
>
> What is the best solution to accomplish this? These are my thoughts.
> Do you think this will work?:
>
> At first org.
> 1. Setup an SMTP connector with address space @corp.com. One of the
> backend server will be the bridghead. This SMTP Connector will smart
> host email to the second org's backend server.
> 2. Set all Exchange servers at first org to forward non-existing
> account to the second org's backend server.
> 3. Make sure there is no recipient filter at any of the servers that
> will reject email sent to non-existent account.
>
> At second org.
> 1. Put a recipient filter at the backend server to reject email sent
> to non-existent account to prevent loop.
> 2. Setup an SMTP connector with address space @corp.com. The backend
> server will be the bridghead. This SMTP connector will smart host
> email to the first org's backend server.
> 3. Set the Exchange server to forward non-existing account to the
> first org's backend server.
>
> TIA
>
-------------------------------------------------------
List Archives: http://www.freelists.org/archives/exchangelist/ 
MSExchange Newsletter: http://www.msexchange.org/pages/newsletter.asp
MSExchange Articles and Tutorials: http://www.msexchange.org/articles_tutorials/
MSExchange Blogs: http://blogs.msexchange.org/
-------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
-------------------------------------------------------
To unsubscribe visit http://www.msexchange.org/pages/exchangelist.asp
Report abuse to listadmin@xxxxxxxxxxxxxx



Other related posts: