Exchange 2010 send/receive connectors

I am truly thankful for sites like this one and here is my question which I am under the gun for. We just bought a company and taking over their operations. For now they have two mail services the services they have plus the our exchange servers. We are both exchange 2010 sp2 separate organizations. We managed to create a connection to their network via the WAN and we can see the internals of their network.

The issue is they have one exchange server and all the message hygiene and routing is done by an ISP. They have had multiple problems sending email to our organization. So what we have decided to do is build a send connector and connect their email server directly to our server by passing the internet and spam filter. I am also not an expert of this area. My first question is do they have to have a one to one ratio with send and receive connectors. For example they and our organization has an existing receive connector to receive any email from anyone. Do we need to create a receive connector in addition to this. All we are doing is wanting them to be able to send directly to our organization. Can I just build a send connector on their exchange server and call it a day.

Also, they have 9,000 plus messages in queue. Here is the bigger issue. Our company advertises through auto discovery contoso.local so everyone can connect. In fact when I build the new connector I am going to build this as contoso.local. Issue is within our organization we have other email address policies like traderwinds.local. Their primary smtp address is traderwinds.local. What is the best way to get those 9,000 or so messages addressed to traderwinds.local to deliver through contoso.local or should I build a separate connector. I know I asked a lot of questions and assistance will be greatly appreciated, thanks
Who is Participating?

Improve company productivity with a Business Account.Sign Up

guswebbConnect With a Mentor Commented:
Good that you have mail flowing. Those 9,000 queued items should also flow as long as your Exchange server is designated as authoritative for the traderwinds domain, and the addresses to which the queued emails are pending also exists against a mailbox on your Exchange server.
Create the new send connector on their Exchange server and have it send all emails for your domain space (instead of *) directly to your Exchange server across the WAN interface i.e. using the internal IP of your Exchange server. This is something we also do and it works just fine.
techdriveAuthor Commented:
So a command like this will deliver all the mail plus the email address policy that is internal to our network like the example I used above. New-SendConnector -Name ‘contoso’ -Usage ‘Custom’ -AddressSpaces ‘SMTP:Contoso.local;1' -IsScopedConnector $false -DNSRoutingEnabled $false -SmartHosts ‘[], [], []‘ -SmartHostAuthMechanism ‘None’ -UseExternalDNSServersEnabled $false -SourceTransportServers ‘[]’
techdriveAuthor Commented:
Email now works fine. It is routed from there server to our server. Problem is they have the other 9,000 messages sitting in queue that my only option is remove or remove with NDR. How do I get those messages delivered.
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.