Configure Internet mail flow through a subscribed Edge Transport server


Applies to: Exchange Server 2013

Topic Last Modified: 2015-04-08

To establish Internet mail through an Edge Transport server, subscribe the Edge Transport server to an Active Directory site. This automatically creates the two Send connectors required for Internet mail flow:

  • A Send connector configured to send outbound email to all Internet domains.

  • A Send connector configured to send inbound email from the Edge Transport server to an Exchange 2013 Mailbox server.

If you don't want to subscribe the Edge Transport server to an Active Directory site, it's possible to manually create the Send connectors required to establish mail flow between the Mailbox server and the Edge Transport server. For more information, see Configure Internet mail flow through an Edge Transport server without using EdgeSync. However, we recommend you subscribe the Edge Transport server to the Active Directory site whenever possible.

  • Estimated time to complete: 20 minutes.

  • You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "EdgeSync" entry and the "Edge Transport servers" in the Mail flow permissions topic.

  • Before you subscribe an Edge Transport server to your organization, you will first need to configure authoritative domains and email address policies for your Exchange organization.

  • Enable the secure LDAP port 50636/TCP through the firewall separating your perimeter network from the Exchange organization. The Edge Transport server needs to be able to communicate with all Exchange 2013 Mailbox servers in the subscribed Active Directory site.

  • For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard shortcuts in the Exchange admin center.

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

  1. On the Edge Transport server, create the Edge Subscription file using the following syntax.

    New-EdgeSubscription -FileName <FileName>.xml [-Force]

    The following example creates an Edge Subscription file named EdgeSubscriptionInfo.xml in the folder C:\My Documents. The Force parameter suppresses prompts confirming commands that will be disabled and warnings that configuration data will be overwritten on the Edge Transport server.

    New-EdgeSubscription -FileName "C:\My Documents\EdgeSubscriptionInfo.xml" -Force
  2. Copy the resulting Edge Subscription file to a Mailbox server in the Active Directory site you're subscribing the Edge Transport server to.

  3. On the Mailbox server, to import the Edge Subscription file, use the following syntax.

    New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path "<FileName>.xml" -Encoding Byte -ReadCount 0)) -Site <SiteName>

    This example imports the Edge Subscription file named EdgeSubscriptionInfo.xml from the folder D:\Data, and subscribes the Edge Transport server to the Active Directory site named "Default-First-Site-Name".

    New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path "D:\Data\EdgeSubscriptionInfo.xml" -Encoding Byte -ReadCount 0)) -Site "Default-First-Site-Name"
    You can use the CreateInternetSendConnector or CreateInboundSendConnector parameters to prevent one or both of the required Send connectors from being automatically created. For more information, see Edge Subscriptions.
  4. On the Mailbox server, run the following command to start the first EdgeSync synchronization.

  5. When you're finished, we strongly recommend you delete the Edge Subscription file from both the Edge Transport server and from the Mailbox server. The Edge Subscription file contains information about credentials used during the LDAP communication process.