I have a customer with hosted e-mail by a hosting company. The plan is to move to dedicated exchange server. But during transition period for a couple of months both should work as there are mobile users whose e-mails will not be migrated to exchange server for some time. Now I can set up MX records so as Exchange is primary target and hosted e-mail is secodnary target but doing that will mean all e-mail will come to exchange. The goal is to receive all e-mails for all users in both places. So i want to have exchange (primary mx) to receive e-mails and then forwarding a copy to the e-mail server of the hosting company. The e-mail should then appear in both servers. How can I set this up? Example: E-mail is sent to user1@domain.com , exchange should deliver to local inbox and send a copy to hosting company e-mail server, which also has a user1@domain.com mailbox. Message in the other e-mail system should appear from original sender, not from exchange server.

Hi You can set a forwarding address on the mailboxes that will also deliver to the local mailbox. The command to do this in 2010 is (not sure what version you are going to use): Set-Mailbox usename -ForwardingSmtpAddress sameuser@otherdomain.com -DeliverToMailboxAndForward $true The only problem you have is that you are trying to do this with a single SMTP namespace which will not work. You will need to have a different SMTP domain which you can configure as an additional proxy address on the hosted mailboxes. The MX record for this domain will point directly to the hosted servers. Cheers, Steve

You'll generate a lot of superfluous e-mail that way. The two mailboxes for each user will never be in synch. Mail will be deleted, answered, categorized in one mailbox, but not in the other one. How many mail users are there at this customer? Another option could be to leave the MX record as is, pointing to the hosting company. Then for your established Exchange mailbox users download the mail with a POP3/IMAP4 Connector. This requires that you configure your SMTP domain as non-authoritative on your Exchange server. When a mail is sent inside your SMTP domain, Exchange sees if it finds the recipient on your server. If so, fine, will be delivered. If not, send the mail out to the Internet and deliver it to the hosting company. This method is tried and true in the SBS world. It works the same way in Exchange 2010 as in Exchange 2007. (SBS 2008 comes with Exchange 2007.) There are lots of POP3 downloaders. The one below is just an example, never the less of high quality. How to Configure Non-Authoritative Accepted Domains in SBS 2008 (Exchange 2007) http://blogs.technet.com/b/sbs/archive/2008/09/25/how-to-configure-non-authoritative-accepted-domains-in-sbs-2008-exchange-2007.aspx MAPILab POP3 Connector for Exchange 2007/2010 http://www.mapilab.com/exchange/exchange_pop3/ MCTS: Messaging | MCSE: S+M

Hi You can set a forwarding address on the mailboxes that will also deliver to the local mailbox. The command to do this in 2010 is (not sure what version you are going to use): Set-Mailbox usename -ForwardingSmtpAddress sameuser@otherdomain.com -DeliverToMailboxAndForward $true The only problem you have is that you are trying to do this with a single SMTP namespace which will not work. You will need to have a different SMTP domain which you can configure as an additional proxy address on the hosted mailboxes. The MX record for this domain will point directly to the hosted servers. Cheers, Steve

You'll generate a lot of superfluous e-mail that way. The two mailboxes for each user will never be in synch. Mail will be deleted, answered, categorized in one mailbox, but not in the other one. How many mail users are there at this customer? Another option could be to leave the MX record as is, pointing to the hosting company. Then for your established Exchange mailbox users download the mail with a POP3/IMAP4 Connector. This requires that you configure your SMTP domain as non-authoritative on your Exchange server. When a mail is sent inside your SMTP domain, Exchange sees if it finds the recipient on your server. If so, fine, will be delivered. If not, send the mail out to the Internet and deliver it to the hosting company. This method is tried and true in the SBS world. It works the same way in Exchange 2010 as in Exchange 2007. (SBS 2008 comes with Exchange 2007.) There are lots of POP3 downloaders. The one below is just an example, never the less of high quality. How to Configure Non-Authoritative Accepted Domains in SBS 2008 (Exchange 2007) http://blogs.technet.com/b/sbs/archive/2008/09/25/how-to-configure-non-authoritative-accepted-domains-in-sbs-2008-exchange-2007.aspx MAPILab POP3 Connector for Exchange 2007/2010 http://www.mapilab.com/exchange/exchange_pop3/ MCTS: Messaging | MCSE: S+M