We currently have an 11 user SBS 2003 server which handles our e-mail, however I'm trying to setup a test migration to Zimbra. For this test migration I'd like to have some e-mail addresses moved over to Zimbra but the rest remaining on SBS 2003, all under the same domain.
In Microsoft terminology I've discovered that this is called a shared namespace/address space. I've looked through various articles and the best guide I've found so far is this http://support.microsoft.com/kb/321721
I was planning to set the new Zimbra server as the new primary, so port 25 of the Zimbra server is open to the internet through our firewall. This way round because it's easy to configure the routing in Zimbra so that specific e-mail addresses get passed on to the old SBS server. I've already got the routing set up within Zimbra and it works perfectly, so sending to oldSBSuser@ourdomain.com from a Zimbra account goes straight to the old SBS Exchange Server. I've not yet switched the port forwarding on our firewall though, so the SBS 2003 machine is still technically the primary.
The problem is I can't get the address space sharing to work in SBS 2003... so that if a user on the SBS server tries to send to an account that no longer exists in SBS, it gets passed to the new mail server.
I've pretty much followed that MS KB article by the word but I'm still getting bounce messages from Exchange when I try and send to a user who now lives on Zimbra.
So here's what I did, I edited our Default Recipient Policy and added @example.local as a new SMTP address, and removed @ourdomain.com
I added a new Recipient Policy called Split Namespace with a new SMTP address of @ourdomain.com and unticked the "This Exchange Organization is responsible for all mail delivery to this address" tick box, which I believe should mean that Exchange is now not-authoritative for that domain.
So I have 3 Recipient Policies listed in System Manager:
1) a mailbox manager policy with priority 1 which deletes messages older than 600 days from user mailboxes
2) Default Policy with priority lowest
3) Split Namespace policy with priority 2
Then I went into the properties of our Default SMTP Virtual Server and checked to make sure the "Forward all mail with unresolved recipients to host" text box was clear under the Messages tab. It was already clear.
Next step was to create an additional SMTP Connector, called it split namespace SMTP connector and set "Forward all mail through this connector to the following smart host" as the LAN IP address of our new Zimbra machine in square brackets... [192.168.1.5]. Added a Local Bridgehead of SERVER _ Default SMTP Virtual Server
Went to the "Address Space" tab and added a new SMTP address of ourdomain.com with Cost set to 1. I also ticked the "Allow messages to be relayed to these domains" box. Checked the delivery options and it's set to "Always Run"
Edited the our existing SmallBusiness SMTP connector to change the cost of the * asterisk Address Space down to 20 so in theory the new SMTP Connector should processed before this one.
Then restarted the MS Exchange Routing Service and the SMTP services
However when I try to send an email through our SBS server to our Zimbra server, I get the following bounce message: "The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address."
So it's not working or I've messed something up somewhere. Anyone know anything else I can check/try?
Is this even supported in SBS 2003? Wouldn't be suprised if there was some sort of crazy restriction stopping me from doing this.