• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1113
  • Last Modified:

Exchange 2010 sp1 /hosted multi-tenant split domain setup

I've successfully deployed exchange 2010 sp1 in /hosted mode with multi-tenancy and the install is working great. We are running into a problem configuring the send connectors for inter domain email and split domains. We have several customers wanting to only put a couple of email accounts on the exchange server and have the rest of their email accounts resolve to a pop server at an external location. Currently I have a internal send connector set to relay email between the domains on the server so they can send emails to one another. Directions for this were found at: http://www.zerohoursleep.com/2010/10/step-by-step-starting-with-exchange-2010-sp1-multi-tenant-sending-and-receiving-emails/

I created the connector: new-SendConnector -Name 'TestOrg' -Usage 'Internal' -AddressSpaces 'SMTP:testorg.com;1','SMTP:lab.com;1' -IsScopedConnector $false -DNSRoutingEnabled $false -SmartHosts '[]' -SmartHostAuthMechanism 'None' -UseExternalDNSServersEnabled $false -SourceTransportServers 'Exchange'

I added all my internal domains to the connector listed above and email is able to flow from one domain to another.

My problem is we have a number of customers who need split-domains set up where users who arent on the exchange server are relayed to an external server. Example to route unknown users on a domain to google my send connector looks as is:

New-SendConnector -Name "Internal Relay - test.org" -Custom -AddressSpaces "SMTP:test.org;5" -SmartHosts aspmx.l.google.com -SourceTransportServers "server"

This results in an internal loop error when sending from one internal domain to another. Sending from an external domain everything is fine. If I remove the "internal" connector listed above the split-domain send connector works perfectly fine delivering locally and to the external server.

How can I make it so both send connectors work?
1 Solution
one of these two exchange organizations must have the accepted domain listed as authoritative
whichever side does not have the MX record pointing to their systems should have this set
Glen KnightCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
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.

Join & Write a Comment

Featured Post

Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now