There's actually an easier way...as long as the policy for @msmail isn't the default Enterprise RUP address, just uncheck the box in the RUP entry that reads 'Exchange is authoritative for this domain' - Exchange will then go back to DNS and try MX records...for any address on that domain not listed in the directory.
So the MX would have to still point to Postfix for internal resolution...but that might be less complex to changing the Postfix MTA... --James -----Original Message----- From: "Fred Skrotzki" <[EMAIL PROTECTED]> To: "Exchange Discussions" <[email protected]> Sent: 5/11/07 1:55 PM Subject: RE: Migration (2000->2003) issue. Ok here is the EXACT deal. Initial environment: Linux box using postfix, doing av and spam scanning then forwarding on to internal exchange box; Exchange box running exchange 2000; Upgrade time, current exchange box sucks and we are replacing the hardware so look at doing a half swing approach to install a new box running exchange 2003 on new hardware. Exchange 2000 box is called msmail New exchange 2003 box is called mail1 So outside mail comes in to the Linux box, which accepts e-mail in for <user>@examples.com AV scan and spam ranking, then was forwarding to <user>@msmail.example.com (this is sending e-mail to the SERVER address which is allowed). Now in the ESM (before adding 2003) the previous admin created the following e-mail address policies smtp: example.com, smtp:msmail.example.com. So the server was accepting mail that was addressed as either which is what we needed. Now when you add in exchange 2003. So it picked up on this policy and said I'll accept for both also. Problem is once I moved a mailbox from msmail to mail1 I could also get mail delivered to the accounts using mail1 just not from mail1 to msmail. (See the issue yet?). The default e-mail policy was saying you are msmail and when it checked the account didn't exist localy but was forwarding back localy... That was my issue. So we had to go into postfix and change how it was forwarding mail from using a internal e-mail address to a site redirect which preserved the external e-mail address of <user>@example.com and then removed the use of msmail.example.com from the e-mail address properties and things now work the way they are supposed to. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fred Skrotzki Sent: Friday, May 11, 2007 2:07 PM To: Exchange Discussions Subject: RE: Migration (2000->2003) issue. Ok I have it fixed and I'll document it up in a bit and send it to the list so everybody understands. I'll tell you it is interesting and makes since once you understand it all (Linux front end and a exchange upgrade using swing method to move).. So look for a update on it when I can get 15 minutes to write it up. I now have to rush and do the moves I promised to have done last night and this morning... -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fred Skrotzki Sent: Friday, May 11, 2007 8:51 AM To: Exchange Discussions Cc: [email protected] Subject: RE: Migration (2000->2003) issue. no it is a external to internal ateway that does AV and spam scanning for inbound only. The two exchange servers can talk directly. -----Original Message----- From: "Wells, James Arthur" <[EMAIL PROTECTED]> Date: Friday, May 11, 2007 8:13 am Subject: RE: Migration (2000->2003) issue. To: "Exchange Discussions" <[email protected]>Reply-To: "Exchange Discussions" <[email protected]> I can't remember if you mentioned...but is mail routing through the Linux box for either of the two mailbox servers outbound delivery? Or are there security restrictions for SMTP delivery on the Exch 2000 server? --James -----Original Message----- From: "Fred Skrotzki" <[EMAIL PROTECTED]> To: "Exchange Discussions" <[email protected]> Sent: 5/11/07 5:52 AM Subject: RE: Migration (2000->2003) issue. Ok our firewall is doing the NAT for each box (Pix 515e). Each box has a Single NIC with a Single assigned IP that is a internal Private IP (172.18.0.x). -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Crowley [MVP] Sent: Friday, May 11, 2007 1:22 AM To: Exchange Discussions Subject: RE: Migration (2000->2003) issue. I recommend using one NIC. While I'm not sure that's your problem, enough people post with their multihoming problems to make me believe it is until otherwise proven. Couldn't your NAT work just as well with an internal NIC as an external one? Ed Crowley MCSE+Internet MVP Time Magazine's Person of the Year! -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fred Skrotzki Sent: Thursday, May 10, 2007 6:12 PM To: Exchange Discussions Subject: RE: Migration (2000->2003) issue. What do you recommend? I need to get the 2003 server to send mail back to the 2000 server without getting a NDR. (The other way works) which is great. I just need this to somehow work until I can get all users moved (This process is scheduled to take 5 days due to peoples work schedules and access). After that we are dumping the 2000 server. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Crowley [MVP] Sent: Thursday, May 10, 2007 6:55 PM To: Exchange Discussions Subject: RE: Migration (2000->2003) issue. Yikes! In general, multihoming Exchange servers results in unpredictable routing issues like you're seeing. I recommend that you dump that configuration. Ed Crowley MCSE+Internet MVP Time Magazine's Person of the Year! -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fred Skrotzki Sent: Thursday, May 10, 2007 3:29 PM To: Exchange Discussions Subject: RE: Migration (2000->2003) issue. Yes both servers are in the Same Exchange Organization and administrative group. Neither server has a Smart host defined. Both servers are on the same subnet (2 ip's right next to each other and can see each other). Each has a dedicated external IP assigned in the firewall so they can send directly out with valid reverse records defined. In advanced delivery the only fields defined are: Masquerade domain: Example.com, (Really our base domain and FQDN on 2000 is msmail.example.com and 2003 is defined as mail1.example.com. We do NOT have a SMTP connector created using any smart host. We are in total DNS control of our IP space so don't need to use smart (Also have BIG fat pipe). -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Crowley [MVP] Sent: Thursday, May 10, 2007 4:39 PM To: Exchange Discussions Subject: RE: Migration (2000->2003) issue. Please confirm that both servers are in the same Exchange organization and administrative group or not. Have you configured the "smart host" field in the SMTP virtual servers' properties on either server? If so, create an SMTP Connector, configure smart hosting there, and clear that field on all virtual servers. Ed Crowley MCSE+Internet MVP Time Magazine's Person of the Year! -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fred Skrotzki Sent: Thursday, May 10, 2007 11:55 AM To: Exchange Discussions Subject: Migration (2000->2003) issue. Ok I'm missing something simple here.. Here is the layout. Mail come in to a Linux server that does some filtering for spam, etc. Then takes valid e-mail and forwards to a exchange 2000 server. This server is built on a POC whitebox from old admin (called msmail) that we can't upgrade. I've deployed a new Exchange 2003 server (called mail1) into the domain and moved 3 test mailboxes using the exchange move mailbox exchange option in users and computers. Anybody external and/or internal can send to the three moved mailboxes and they get the mail. The moved mail boxes can send mail to anybody EXCEPT those on the old server. We get NDR's. Each users e-mail addresses are set to [EMAIL PROTECTED] as the default SMTP and [EMAIL PROTECTED] as a secondary smtp so mail from the Linux box get's accepted. It will take me about a week to move each user with there permission from one s _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
