Create a Send connector in Exchange Server to send mail to the internet

Artikkeli
02/22/2023

When install your first Exchange Server 2016 or Exchange 2019 server, the server isn't able to send mail outside of your Exchange organization. To send mail outside your Exchange organization, you need to create a Send connector.

What do you need to know before you begin?

Estimated time to complete: 5 minutes
You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "Send connectors" entry in the Mail flow permissions topic.
See Deploy a new installation of Exchange Server if you're beginning your installation. After the installation, you can use the steps in this topic to create an internet Send connector.
For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard shortcuts in the Exchange admin center.

Tip

Having problems? Ask for help in the Exchange forums. Visit the forums at: Exchange Server, Exchange Online, or Exchange Online Protection.

Create a Send connector to send mail to the internet

Until you create a Send connector, mail can't flow from your Exchange to the internet. The exception is if you install an Edge Transport in your perimeter network and subscribe the Edge Transport to your Exchange organization. For more information, see Edge Transport servers.

See also Send connectors for more information about connectors and why you would may or may not want to use them instead of Edge Transport Servers.

Use the EAC to create an internet Send connector

In the EAC, navigate to Mail flow > Send connectors, and then click Add . This starts the New Send connector wizard.
On the first page, enter the following information:
- Name: Enter a descriptive name for the Send connector (for example, To internet).
- Type: Select Internet.
When you're finished, click Next.
On the next page, verify that MX record associated with recipient domain is selected. This means the connector uses DNS on the internet to route mail, as opposed to routing all outbound mail to a smart host. For information about creating a Send connector that uses smart host routing, see Create a Send connector to route outbound mail through a smart host.

When you're finished, click Next.
On the next page, enter the following information:
- In the Address space section, click Add . In the Add domain dialog box that appears, in Fully Qualified Domain Name (FQDN), enter an asterisk (*), and then click Save. This value indicates that the Send connector applies to messages addressed to all external domains.
- The Scoped send connector setting is important if your organization has Exchange servers installed in multiple Active Directory sites:
  - If you don't select Scoped send connector, the connector is usable by all transport servers (Exchange 2013 or later Mailbox servers and Exchange 2010 Hub Transport servers) in the entire Active Directory forest. This is the default value.
  - If you select Scoped send connector, the connector is only usable by other transport servers in the same Active Directory site.
When you're finished, click Next.
On the next page, in the Source server section, click Add . In the Select a Server dialog box that appears, select one or more Mailbox servers that you want to use to send mail to the internet. If you have multiple Mailbox servers in your environment, select the ones that can route mail to the internet. If you have only one Mailbox server, select that one. After you've selected at least one Mailbox server, click Add, click OK, and then click Finish.

After you create the Send connector, it appears in the Send connector list. To configure the Send connector to proxy outbound mail through the Front End Transport service, see Configure Send connectors to proxy outbound mail.

Use the Exchange Management Shell to create an internet Send connector

Open the Exchange Management Shell. For more information, see Open the Exchange Management Shell.
Use the following syntax:
```
New-SendConnector -Name <Name> -AddressSpaces * -Internet [-SourceTransportServer <fqdn1>,<fqdn2>...]
```
This example creates the internet Send connector named "To internet" with the following properties:
- The usage type is Internet.
- The Send connector uses DNS routing. We aren't using the DNSRoutingEnabled parameter, and the default value is $true.
- The Send connector is for all external domains (*).
- The local Exchange server is the source server. We aren't using the SourceTransportServer parameter, and the default value is the local Exchange server.
- The Send connector isn't scoped to the local Active Directory site. We aren't using the IsScopedConnector parameter, and the default value is $false.
```
New-SendConnector -Name "To internet" -AddressSpaces * -Internet
```
For information about other options, see New-SendConnector.

Note

To configure the Send connector to proxy outbound mail through the Front End Transport service, add -FrontEndProxyEnabled $true to the command. For more information, see Configure Send connectors to proxy outbound mail.

How do you know this worked?

To verify that you have successfully created a Send Connector that sends mail to the internet, create and send a message from an internal mailbox to an outside recipient, and verify the recipient receives the message.

You can also turn on protocol logging for the Send connector, and view the information in the log. For more information, see Protocol logging.

Jaa