At the end of this video, the student will learn how to configure Send and Receive connectors in Exchange Server 2016. These connectors are critical to being set up properly before mail flow will work on your server.
- [Instructor] Send and receive connectors, in Exchange Server 2016, need to be properly set up before Mail Flow will work in your new exchange server. By default they are not set up to do this, and that will cause all inbound and outbound email to fail until doing so. So, what do we need to begin? Well, we need to start with an accepted domain configured for the organization, and we did this in a previous video, where we set our accepted domains up. Next thing we're going to need is an email address assigned to the recipient.
So after the accepted domain is set up, then each individual mailbox has to have an email address that is assigned to it. You can have it auto populate simply by creating the default domain and telling it to auto populate in the Exchange admin center. Or you can go in to each individual account and create custom email addresses. If you choose the automated way, it will take the login name and the accepted domains and append them to the login name as the default email addresses.
We also need MX records in your public DNS zone. This tells the rest of the world where your mail store is, so it can send emails to it. We also need inbound SMTP, or simple mail transport protocol port 25 connectivity from external senders to your Exchange Server, or a mail route that leads to your Exchange Server. This basically means that from the firewall, we need to port forward TCP port 25 to your inbound Exchange Server, whether it's in the DMZ as a transport server, or as the mailbox server on the inside of the network.
Now we can set up our send and receive connectors. In our Exchange admin center, we're gonna start by clicking on mail flow on the left hand side, and at the top we're going to click on send connectors. This is the connector where outbound email happens. And this needs to be set up properly or it will go nowhere. So let's go ahead and start by clicking on the plus, and choosing our name. I am just going to simply type Outbound, so we know that that's what this connector is for.
I'm gonna go ahead and leave the default Custom, and choose Next because we wanna customize how we want our email to leave the organization. From here we can choose to relay through a smart host, which also has to do with our receive connectors on the receiving end should we choose to take that option, or we can leave the default and choose the MX record associated with the recipient domain. For instance, if we're going to send an email to msn.com, then we need to find out where that email address is and the server associated with it.
We can use the MX record that's out on the public DNS servers, or we can relay through our own internal DNS server to a public DNS server to find out where the MX record is, and then we'll know where to send that email. We're gonna go ahead and choose to leave it at the default, MX record associated with the recipient domain. Now we'll need an address space. For our default send connector, we're going to keep it very simple, and just leave this star and we're going to click Save.
That means any email we want to send outbound is going to go out through this connector. Now we need to send the source server. Since right now we just have the one mailbox exchange server, we're going to choose EXCHANGE1. Now we'll click finish. Now all outbound email that's destined for outside our exchange organization is going to go out through our connector, use public DNS, and then get delivered to the recipient. Let's go ahead and take a look at the receive connectors.
Let's start with our Client Frontend on EXCHANGE1, and double click. From here we're going to go right to the scoping area. This shows that all IP addresses are going to be allowed to be used for our client front end receive connector. Now we'll click on security. We're going to leave this particular connector exactly as it is, by making sure that our transport layer security is turned on, and exchange users is checked as well as the other options that are checked by default.
What this connector is used for is for anybody outside the organization or inside the organization that is using POP3 or IMAP. These are older types of connectivity, used through clients such as Outlook and other products. This allows a secure communication using TCP port 587 and transport layer security so they can receive emails through this special receive connector.
Let's go on to our default front end receive connector. We will again go to our scoping link, and we see that all IP addresses are allowed, and that our TCP port is port 25. This means that it will receive any email on port 25, from any location, whether inside or outside the organization, assuming that a firewall is port forwarding TCP port 25 to that server.
You can remove the IP addresses and replace them with individual IP addresses that you trust, this is a very good way to do this, by clicking on the minus key to remove all IP addresses on IPv6 and IPv4, and then click on the plus key to add in just the trusted servers that you want to receive email from. Now let's click on security. By checking the boxes as you see them here, you can receive email from all users, including anonymous users.
Without the anonymous users box being checked, you will not be able to receive email from anyone on the outside of your organization because they won't be trusted. So make sure that you check the anonymous box, and click Save. Those were the two most important connectors, but we should also mention the other connectors as well, such as the Outbound Proxy Frontend. If you check the proxy through client server option that I discussed earlier in the send connector, then outgoing emails are received by this connector.
In other words, this connector receives emails sent by the transport service if proxy through client access server is checked in the send connector. The client proxy receive connector works in a similar way, it accepts connections on port 465. This receive connector accepts proxied POP and IMAP connections sent from a receive connector. The default exchange receive connector is also a hub transport service, and it accepts incoming mail from the front end transport service and sends to the mailbox transport service.
These three exchange receive connectors can stay exactly as they are by default when you install Exchange Server 2016 without any necessary changes. There are your five Exchange receive connectors, along with the send connector that we set up earlier. By setting up your send and receive connectors properly in Exchange Server 2016, you can resolve any issues with sending and receiving emails though your Exchange server.
Need to set up Exchange Server for the first time? Check out Robert's previous course, Deploying Exchange Server 2016.
Note: This course maps to the certification exam for Exchange Server 2016. Review the course and exam blueprint for the Exchange Server 13 exam here and here.
- Reviewing the Exchange Control Panel
- Managing the Mailbox role
- Configuring permissions and delegates
- Managing and troubleshooting mail transport
- Troubleshooting SMTP mail flow and domain security
- Designing an Exchange SLA
- Backup and recovery
- Planning high availability
- Troubleshooting connectivity