v-leeli

Dear Ken,

Thank you for posting here.

Based on your description, I understand you use Postfix as gateway to
distribute mails based on the SMTP address: @westE55.company.com or @
eastE55.company.com. Now I can understand you join an Exchange Server 2003
into East coast Site, and host new SMTP address @
eastE2K3.corp.company.com.

According to my knowledge, we could create a Recipient Policy to host SMTP
address eastE2K3.corp.company.com by the instruction in the article below.

317298 XADM: How to Create E-Mail Addresses Based on Recipient Policies
http://support.microsoft.com/?id=317298

After creating Recipient Policy, I think you need to associate SMTP address
eastE2K3.corp.company.com with new Exchange Server 2003 by FQDN or IP
address in Postfix gateway. Please understand Postfix is provided by a
manufacturer independent of Microsoft. Therefore, we cannot guarantee their
performance and reliability. For more information and further suggestions
about configuring Postfix Server, I am afraid that you may need to contact
them directly.

If there is anything I can do regarding Exchange Server, feel free to let
me know. Thanks and have a nice day!

Thanks & Regards,

Lee Li
Microsoft Online Partner Support

Get Secure! - http://www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Subject: Postfix and Exchange 2003
| From: "MR-KEN" <kcarlini@netopia.com>
| Date: Tue, 16 Nov 2004 14:40:16 GMT
| X-Newsreader: News Rover 8.2.2 (http://www.NewsRover.com)
| Message-ID: <OFG1wo#yEHA.3908@TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.exchange.setup
| NNTP-Posting-Host: webmail.cayman.com 141.154.96.162
| Lines: 1
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSFT NGXA01.phx.gbl!TK2MSFTNGP0
8.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.exchange.setup:119220
| X-Tomcat-NG: microsoft.public.exchange.setup
|
| We are converting from E55 to E2K3.
|
| We have two sites, each with one E55 located on the East and West coast.
|
| The E55 servers are in a domain company.com, while the entire company (as
| well as the new E2K3 server) is in the domain corp.company.com.
|
| We have Postfix on the West coast, which via the alias list, points e-mail
| to either the host on the West coast or the host on the East coast. For
| example, and entry in the alias file would read:
|
| bob:bob@westE55.company.com
| joe:joe@eastE55.company.com
|
| With E2K3 no joined to the East coast Site, I would like to start routing
| the e-mails to it and not to the E55's IMC.
|
| To get this to work (and it does work), is to change the alias list to:
|
| joe:joe@eastE2K3.corp.company.com
|
| And to make that same change to the user account alias in AD.
|
| The dilemma is that I see a possible problem pointing the mail to the E2K3
| FQDN (it even warns about this in the E2K3 do***entation. During
testing, I
| also noticed that if I made the change on Postfix, but not to the user
| account, it would create a loop back.
|
| MX records are kind of out of the question, as we want the Postfix to
| deliver directly to the host. I also understand that there may be a way
to
| have postfix query AD.
|
| However, to keep things simple, does anyone have another route or idea on
a
| Best Practices for this?
|
| Thanks so much!
|