Google Apps and Exchange 2007 external email routing

I have a setup using Exchange 2003 where some of the users are on the Exchange server and some are not and they share a single domain name. I am trying to do this on 2007 and it is not working out the way we want.

MS changed the whole thing in 2007 compared to 2003 and I can't figure out the combination of Edge server sending policies to make it right. I would like to have all emails looked up outside the server and then delivered. Since the SBS server grabs the mail on the external email server, the external routing is fine, but the internal routing would need to be external in all cases.Here is a simple example:

For example Bob is an in-house employee and is in the office using Outlook. Joe is a contractor or a remote user who does not need exchange access so he is going to an external email server, not exchange. When Bob sends to Joe it fails as AD does not find the user. I have looked for the answer and have no success in implementing it. There is a process for Exchange to check AD, then if the user is not found send out to the world to see fit ere is a match

This is a SBS 2008 box with Exchange 2007
LVL 1
BITS_LAAsked:
Who is Participating?
 
Cliff GaliherCommented:
It is rarely recommended to split your users across multiple platforms and it is *never* easy to do. Troubleshooting, mail routing and tracking, user management, all of these become more complex, more than the sum of their parts because the added step of the interconnectedness and process determination add overhead.  In short, my *first* recommendation is to make a plan to consolidate. Exchange has OWA for web access, Outlook Anywhere for remote client access, supports POP3 and IMAP for non-Outlook clients...I'll repeat, the cases where splitting up your userbase across multiple mail platforms is a good idea is *exceedingly* rare.

With that said, what you need to do is set up a shared namespace. It involves setting up a lookup policy and an additional SMTP connector, which SBS wizards won't like, so be aware that any use of the SBS wizards will re-break this configuration.  With that said, here goes:

http://technet.microsoft.com/en-us/library/bb676395(EXCHG.80).aspx

-Cliff
0
 
BITS_LAAuthor Commented:
I agree. Due to the sensitive nature of the data in this office they have to keep PCI complicane and such, so normal access via OWA is complicated. I do agree and understand the area I am entering is rare and complicated. With my 2003 setup I had them eventually merge to 100% EXC. This is not currently an option for the other setup and will explore the best case with them for the long term. For the short term this is what they want to have happen.

I think I read this article, but I will give it a shot after hours and post my findings. Thank you for the response and I look forward to resolving this issue.
0
 
BITS_LAAuthor Commented:
I just got confirmation that the policy adjustments I did on Sunday actually worked. The tests for me seemed to fail. Maybe they just needed propagate.

The article was what I based my work on. Thank you for confirming that this was the solution.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.