Hello, Company A + B share a domain name (@company.ca) and hosted (pop3) mail solution. A web portal (https://mail.company.ca) is used to add/configure users. Company C (the company I work for) is taking over the IT infrastructure of Company A only. We want to move Company A to our in house Exchange 2010, but need to leave Company B's mail on the hosted site. We will be changing the mx records for the domain to point to our environment. Is there a way to split the authorative domain on Exchange 2010 so that some users are hosted locally, and some are hosted externally. Could the Internal Relay domain be used in this instance, and if so how is the send connector configured? And if I change the mx records, will that also change the address for the portal URL? Thank you.

Hi there are two way one is through federation gateway & 2nd one is Hybrid configuration wizard. For 2nd one exchange 2010 with sp2 must. here is two helpful link which will resolve this problem. http://technet.microsoft.com/en-us/library/dd335047.aspx http://technet.microsoft.com/en-us/library/hh529921.aspx Don't forget to mark helpful or answer connect me :- http://in.linkedin.com/in/satya11 http://facebook.com/satya.1000

Sorry. I was not clear. Company A + B do not use Active Directory and are not using Exchange. The mail is hosted by Company A's ISP.

On Wed, 3 Oct 2012 13:56:30 +0000, CCCOttawa wrote: >Sorry. I was not clear. > >Company A + B do not use Active Directory and are not using Exchange. The mail is hosted by Company A's ISP. Then why ask the qestion in a forum for Exchange administration? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Because I am trying to Administrate my Exchange (Company C) to work with / accept only a piece of the other mail service.

This is one of the simple exchange issue. I will help you but let me know if this post is being moved to different location. We are in Exchange Admin but this is Exchange connector issue. Here is the action Plan: Mail flow: 1. Create accepted domain as internal relay in Company C 2. Create send connector to have the smart host forwarded to ISP mailserver which is the current mx record. and use same domain name space @company.ca 3. Ask the ISP to add your IP on the safe sender 4. change the mx record to your server. Client connectivity: 1. Create a new url for the Company A users for autodiscover, activesync, owa and RPC over http 2. Instruct or configure the same to the users of Company A. 3. Company B can continue with the same wayRegards, Prabhat Nigam XHG and AD Architect and DR Expert Website: msexchangeguru.com VBC: https://www.mcpvirtualbusinesscard.com/VBCServer/wizkid/card

This is one of the simple exchange issue. I will help you but let me know if this post is being moved to different location. We are in Exchange Admin but this is Exchange connector issue. Here is the action Plan: Mail flow: 1. Create accepted domain as internal relay in Company C 2. Create send connector to have the smart host forwarded to ISP mailserver which is the current mx record. and use same domain name space @company.ca 3. Ask the ISP to add your IP on the safe sender 4. change the mx record to your server. Client connectivity: 1. Create a new url for the Company A users for autodiscover, activesync, owa and RPC over http 2. Instruct or configure the same to the users of Company A. 3. Company B can continue with the same wayRegards, Prabhat Nigam XHG and AD Architect and DR Expert Website: msexchangeguru.com VBC: https://www.mcpvirtualbusinesscard.com/VBCServer/wizkid/card

On Wed, 3 Oct 2012 18:16:24 +0000, CCCOttawa wrote: >Because I am trying to Administrate my Exchange (Company C) to work with / accept only a piece of the other mail service. If your server's going to be the MX to receive the e-mail the you'll have to decide who's going the be authoritative for the domain -- expecially if you and the other company are going to send e-mail to each other. A simple "internal relay" will work fine if the two of you never exchange e-mail. Just send everything that isnn't in your directory to them and they'll have to send the NDR for mail that doesn't exist in their organization. This can get pretty ugly if your server is receiving a ton of spoofed e-mail and you're just sending it all to them (you can't use recipient filtering). If they use recipient filtering then you'll be sending all the NDRs and possibly getting on DNSBLs because of it. A safer way to deal with it is for them to add a secondary SMTP proxy address to their mail-enabled objects (let's call it "relay.domain.com"). You create mail-enabled contacts in your AD with a target address of user@relay.domain.com and a secondary SMTP proxy address of user@domain.com. Use a Send connector with an address space of relay.domain.com to direct the mail to their organization. Now you can turn on recipient filtering. You won't accept e-mail for addresses that don't exist. No more problems with sending masses of NDRs. The problem here is an administrative one -- they have to tell you whenever they add (or remove) a mail-enabled object so you can add the corresponding object to your AD. Directory synchronization can remove some of the administrative work, but ultimately you'll want to stop that address space sharing because it's a real PITA. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP