View Single Post
  #7 (permalink)  
Old 09-03-2007, 09:38 AM
batfastad batfastad is offline
Elite Member
 
Posts: 275
Cool

At the moment all I was looking to do was test Zimbra, by hopefully making no changes to our current Exchange set up at all.

I thought the easiest way to do that would be by using a completely separate domain name which we currently have spare.
And somehow configuring Exchange to bounce all mail to a certain domain over to Zimbra's internal IP address.

At the moment port 25 is forwarded to our Exchange server on our local network.


Having re-read that Split Domain article, I'm unsure which option I'm looking for... Zimbra as the Primary or Secondary.

I guess the easiest route for me to configure the split domain would be like this:
- Forward 25 to Zimbra, rather than our Exchange server
- That means that any mail that can be delivered to a Zimbra account, is processed by Zimbra.
- Then I configure Zimbra's postfix to bounce other mail onto the Exchange server (using the local DNS address of the Exchange server) using the instructions on that Wiki article

Then if I decide to shut-down the Zimbra test server or do a fresh install onto a different machine, I just forward port 25 back to our main Exchange server like at the moment and Exchange handles all the inbound mail requests?

That would certainly be a good option - no configuration changes needed in Exchange!


But is that Zimbra as a primary or secondary?
My thinking that the above scenario represents Zimbra as a secondary, even though it is technically acting as the primary SMTP receiving server at our IP address

Is that correct?
It's been a long day!
Reply With Quote