Recreate default receive connectors in Exchange Server
Content
Suppose you only want to recreate one of them, then Proof of stake only remove that specific default receive connector. The Hybrid Configuration Wizard configures one send connector on your on-premises Exchange Server and two connectors (inbound and outbound) in Office 365. Configuring a Send Connector to send outbound internet email via a smart host is the same process as above, with the following differences.
Add send connector for outbound mail via Office 365
Transport services in Exchange have not changed dramatically since Exchange 2013. This means that all transport components are now combined in one server role. In this week’s episode, we dive deep into Microsoft’s latest https://www.xcritical.com/ announcements and changes that will impact your organization in 2025 and beyond. Sometimes the list of IP addresses to add is too long to type out or the IP addresses come from an external source.
- Run the Get-SendConnector cmdlet to find the configured send connectors in Exchange with PowerShell.
- Choose Only when I have a transport rule… and click Next.
- In the protocol logfile, you can see the date and time of the communication, which receive connector was used, and which IP address is connecting to your server.
- When the Send Connector is configured to use smart hosts and a change occurs in the smart hosts, use the Exchange Admin Console to add or remove a smart host.
- This way you have a new Relay Connector which uses all remote IP addresses from the old Relay Connector.
Recreate default receive connectors PowerShell script
When the categorizer determines the mailbox of the recipient, the message is put on the delivery queue before transport routes it to another mailbox server or to the Mailbox exchange connectors transport service. The names look similar, but it’s a different service. The Mailbox transport service is the service that communicates with the mailbox database to deliver the message to a mailbox or to pick up an outgoing message from a mailbox.
Exchange Server default receive connectors
As always, our choice of what’s important and what’s not might not match yours, so feel free to comment and voice your opinion. Exchange Server uses Send Connectors to route messages to other Exchange Server, to other organizations, or to the Internet. This way all servers in the organization know about the Send Connector’s existence and an Exchange server can make routing decisions. Now that we have identified that we have a send connector to the internet and the connectors which the Hybrid Configuration Wizard adds are in place, we can proceed to the next step. The Outbound to Office 365 send connector is already configured when you run the Hybrid Configuration Wizard.
Configuring Outbound Mail Flow Direct to the Internet
You learned how to recreate default receive connectors in Exchange Server. If you have issues with inbound mail flow or made changes to the default Exchange Server receive connectors and want to set it back to its original configuration, recreate them. Recreate the receive connectors in Exchange admin center or with the PowerShell script. Why discuss Exchange 2019 Transport now, since it seems like everybody is moving to the cloud? Well, many of the organizations that move to the cloud run an Exchange hybrid organization and need at least one Exchange 2019 server on-premises for management purposes. This server (or these servers) is often used for SMTP relay purposes.
Specify one or more smart hosts to which Office 365 will deliver email messages. There are different reasons to have a hybrid infrastructure. One of them can be that the HR is, for legal reasons, not allowed to move their mailboxes to the cloud.But in this article I will not write about reasons why a hybrid mail environment could make sence.
What if we like to add a send connector with PowerShell? Sign in to Exchange Admin Center as an administrator or with an account with the privileges to add a send connector in Exchange Server. In the next article, we will migrate mailboxes to Office 365. The send connector is now visible in the Exchange Admin Center. In the figure below, you can see how the Office365 connectors work in both scenarios. It’s quicker to create a send connector with PowerShell.
You learned how to create a send connector in Exchange Server. You learned how to create a send connector in Exchange with EAC and PowerShell. Configuring a new send connector in Exchange with PowerShell is faster. Don’t forget that you can disable the created send connector instead of removing it.
First, the network setting is configured to Route mail through smart hosts instead of MX records. You must then click the + button to add at least one smart host name or IP address. Multiple smart hosts are permitted and are recommended for redundancy. For this scenario to work as expected, we will have to configure the Exchange servers to send all messages directly to Office 365.The connector enables Office 365 to scan all mails for malware and SPAM. When the Send Connector is configured to use smart hosts and a change occurs in the smart hosts, use the Exchange Admin Console to add or remove a smart host. Open the Exchange Admin Center and navigate to Mail flow → Send Connectors.
When you choose to use a smart host you also get the option to configure authentication for the Send Connector. This is only necessary if the smart host requires it. Many email security servers/appliances or even hosted solutions will simply authenticate you based on your IP address rather than require other credentials. Organizations often want to use Exchange Online for outbound mail because of Exchange Online Protection (message hygiene).
Receive Connectors are configured per server, and when something changes in your mail flow, Receive Connectors need special attention. When adding new Exchange servers, new Receive Connectors are added as well. In previous articles, I discuss the transport pipeline and how Exchange 2019 routes inbound and outbound messages using Send and Receive Connectors. In this article, I cover how to manage Exchange 2019 Send and Receive Connectors, including moving to new versions of Exchange. You may also like Find IP addresses using Exchange SMTP relay. It’s important to remove the default receive connector you want to recreate.
I use the script published by Ali Tajran which you can download here. This script checks if any host is still using a Receive Connector on an (old) Exchange server. We showed how to configure outbound mail via Office 365. Change the Exchange on-premises outbound mail flow before, during, or after migration. From that point, the outbound mail flow will go via Exchange Online Protection and land in the recipient’s mailbox. Right now, the on-premises Exchange organization has a send connector for outbound mail to the internet.
After the message arrives, copy the headers and paste them into the Message Header Analyzer. The new send connector will look as follow in the on-premises Exchange admin center. One thing you have to know is, that the very first thing you have to do is to set your publich DNS MX-record’s TTL down. My recommendation is to set the TTL for the MX-records from 3600 to 300, one day before moving . This allows us to have less or no problems at all by changing the mail flow.More information about MX-records you can find HERE.
It went through a few hops in Exchange Online before eventually traveling out to Google mail servers. If you want to speed up your testing, you will need to restart the Microsoft Exchange Transport Service on the server, which forces it to reload the configuration. To look more closely at the messages stuck in a single queue you can use Get-Queue and Get-Message together. For further configuration and tested steps refer to the last section of this article. Outbound mail flow in Exchange Server 2013 is managed with the use of Send Connectors. After completing the wizards for both connectors, you will find these created in Office 365 connectors as shown below.
Click the plus icon to create the first send connector. Ensure the file is unblocked to prevent errors when running the script. Read more in the article Not digitally signed error when running PowerShell script. The mail went from on-premises Exchange Server to Exchange Online.