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

Send connector in Exchange 2007

We have a domain trust between two companies (connected via MPLS) and the other company receives email on our behalf (common SMTP address) and sends externally received email onto us via external contacts setup in their Exchange environment to mimic our users Exchange accounts held locally.  

These emails are simply sent onto us our via direct MX record (DNS) by the other company.

If we wanted this email routed direct to our Exchange server technically all the other company would have to do is create a send connector that points at our Exchange systems IP address?
1 Solution
Here is you're set up as per what i understand

MX record of yourcompany.com is pointing to othercompany.com

othercompany.com receives emails - since it is authorised too, and forwards to yourcompany.com using an internal relay connector.

Until here it sounds good - cause you're achieving name-space-sharing concept.

From here onwards, you asked what if other companies want to send emails directly to your company Bypassing the normal MX route.

Yes, they'll need to create send connectors - add yourcompany.com address space and add IP Address of your internet facing firewall / Edge server.

If yourcompany.com Exchange server is authorised to receive emails - you're good to go.

However, if you want all the companies to send you emails effortlessly - change your MX record to point to yourcompany.com environment from othercompany.com servers.



Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

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