Mail flow from Exchange 2013 to 2010 for specific domain (two sites)

We have two sites joined by a site-to-site VPN tunnel. Site A contains a Exchange 2013 server and site B a Exchange 2010 server. What we want to do is send mail from site A to a domain hosted on the Exchange server in site B through the VPN tunnel.
What we did is create a send connector for this domain on the Exchange 2013 (in site A) server and added the IP address of the Exchange 210 server (in site B) as the Smart Host.
On the Exchange 2010 server we created a receive connector which only listens to the internal IP of the Exchange 2013 server. Furthermore we set it to not use a Authentication Mechanism and set Anonymous users as the only Permission Group.

We are able to telnet port 25 from the Exchange server in Site A to the one in Site B, so that part seems to work.

When mails are send to a mail address in the specific domain (using OWA of Telnet) from site A, the mail gets stuck in the Exchange queue on the Exchange 2013 server.
LVL 1
Ronny StijnsAsked:
Who is Participating?
 
Simon Butler (Sembee)Connect With a Mentor ConsultantCommented:
No, you are referring to the SEND Connector, I was referring to the Receive Connector.
You still need the Send Connectors - there is nothing wrong there. However a Receive Connector is just a listener,

Simon.
0
 
Simon Butler (Sembee)ConsultantCommented:
Unless you have the default connectors locked down to specific addresses, there is no need to configure an additional Receive Connector. Therefore if you don't need the connectors to be locked down, delete the connector and use the default instead.

You will need to have the Authentication methods enabled, even though it isn't using them. However if you use the default connector instead, you should find email flows fine.

Simon.
0
 
Ronny StijnsAuthor Commented:
Doesn't the default connector use the MX record and therefore the mail flows over the internet instead of the tunnel?
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Ronny StijnsAuthor Commented:
Works! Thank you very much for your help!
0
 
Ronny StijnsAuthor Commented:
Worked after implementing the solution.
0
 
ToshkyCommented:
Sorry what was the solution.
0
 
Ronny StijnsAuthor Commented:
Using the default receive connector, instead of creating a second one.
0
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.