I have recently installed a Server 2008 R2 + Exchange 2010 devbox with the following objective: There are a small number of external email addresses clients use to send and receive emails within our organization. What I'd like to do is aggregate those external emails into one system - Outlook 2010 + Outlook 2010 OWA. The current idea is that we can set those external emails to forward all emails to an exchange mailbox and have clients reply to these emails by using the From: field to keep the recipients unaware that any forwarding has occurred. The forwarding of these external emails to exchange is easy. The From field in Outlook and OWA exists, but the last piece of the puzzle is the ability for the exchange server to inspect the From field of the outgoing mail and route it to the appropriate IMAP connector to be sent to the third party email system to be sent out. Any ideas would be appreciated. But keep in mind that I'd rather stay away from any commercial products if possible and I'd like to avoid having to modify Outlook 2010/ OWA to get it to work.

Hi, Just clarify you want if a particular email address is in from field the mail should route to a particular connector, if yes then try creating a transport rule which say if from field is X do this, have a look into this article : http://technet.microsoft.com/en-us/library/dd638183.aspx, do let us know if doesn't help.Ripu Daman Mina | MCSE 2003 & MCSA Messaging

Just had a good look at the Transport Rules - How does one do a "If mail is positive for xx Transport Rule, send to xx Connector"? The action list for the Transport Rules does not appear to have a "send to x Connector" action. The actions appear to revolve entirely around modifying the message.

Hi, Try creating a connector for XX domain & any mail for XX will eventually will go through that connector, have a look into this article : http://technet.microsoft.com/en-us/library/aa997285.aspx Ripu Daman Mina | MCSE 2003 & MCSA Messaging

Hrm, I've yet to look completely into this solution, but am I correct in saying that I can only connect through SMTP and not IMAP/POP3? Also, hang on, send connectors look at the RECIPIENT address, not the SENDER address. So how will that help me route a mail for example from s.t.richmond@gmail.com to the gmail.com domain to be sent?

Hrm, I've yet to look completely into this solution, but am I correct in saying that I can only connect through SMTP and not IMAP/POP3?

On Fri, 24 Sep 2010 21:21:12 +0000, STRichmond wrote: > > >Hrm, I've yet to look completely into this solution, but am I correct in saying that I can only connect through SMTP and not IMAP/POP3? > >Also, hang on, send connectors look at the RECIPIENT address, not the SENDER address. So how will that help me route a mail for example from s.t.richmond@gmail.com to the gmail.com domain to be sent? I haven't used this, but it's the only commercial product I've found to do sender-based routing: http://www.messageconcept.net/ExSBR%20Flyer%20V3.pdf --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich, Thanks for that. Although I don't want a commercial product it at least shows me that Exchange 2010 can't actually do what I require without modification. So the next question is - How can I go about developing my own extension. I've had a brief look at the Exchange SDK and Transport Rules API, and it doesn't look OVERLY difficult.

On Sat, 25 Sep 2010 03:03:21 +0000, STRichmond wrote: >Thanks for that. Although I don't want a commercial product it at least shows me that Exchange 2010 can't actually do what I require without modification. So the next question is - How can I go about developing my own extension. I've had a brief look at the Exchange SDK and Transport Rules API, and it doesn't look OVERLY difficult. Moving your question to an Exchange developer forum would be your best bet. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Thanks Rich, I've done so here: http://social.technet.microsoft.com/Forums/en-US/exchangesvrdevelopment/thread/b81b4945-b2f9-4c7d-b3c8-ff35ecfb8eeb