locked
MB Server not sending e-mail through Edge Transport RRS feed

  • Question

  • Hi all,
    It's been awhile since I've done some administering Exchange and whoa....it's changed a bit.  Here's my problem:

    I have installed the MB "Role" in my "trust" network and the edge transport role in my "DMZ".  When I send an e-mail out, it does send; however, it's sending the email from the MB server rather than the Edge Transport.  This will cause me all kinds of problems with the SPF record, etc.  No idea why it's not routing out through my Edge Transport!

    The send connectors I see:
    EdgeSync - MYSITE- To Internet
    EdgeSync - Inbound - To MYSITE
    Outbound to Office 365 - Another can of worms for another post.

    The receive connectors are:
    Client Frontend MBSERVERNAME - Role: FrontendTransport
    Client Proxy MBSERVERNAME - Role: HubTransport
    Default MBSERVERNAME - Role: HubTransport
    Default Frontend MBSERVERNAME - Role: FrontendTransport
    Outbound Proxy Frontend MBSERVERNAME - Role: FrontendTransport

    Lastly,
    What the heck are all these receive connectors and why don't I see an edgesync connect in the receive connectors area?!

    Tuesday, March 7, 2017 3:46 AM

All replies

  • Hi rmmill3,

    Did you subscribe the Edge Transport server to your Active Directory site?

    Please refer to the following articles to configure your internet mail flow:

    Configure Internet mail flow through a subscribed Edge Transport server

    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.

    Also see : Configuring Exchange 2016 Edge Transport Server

    Best Regards,


    Niko Cheng
    TechNet Community Support


    Please remember to mark the replies as answers.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by Niko.Cheng Tuesday, April 11, 2017 6:04 AM
    Wednesday, March 8, 2017 9:22 AM
  • Hi there and thank you for your help!
    I did subscribe to the edge transport and here are my tests showing it's working...at least I think.

    [PS] C:\Windows\system32>test-edgesynchronization |fl


    RunspaceId                  : bunchoflettersandnumbers
    SyncStatus                  : Normal
    UtcNow                      : 3/8/2017 11:59:14 PM
    Name                        : EXCHET
    LeaseHolder                 : CN=EXCHMB,CN=Servers,CN=Exchange Administrative Group
                                  (bunchoflettersandnumbers),CN=Administrative Groups,CN=mycompany,CN=Microsoft
                                  Exchange,CN=Services,CN=Configuration,DC=mycompany,DC=com
    LeaseType                   : Option
    FailureDetail               :
    LeaseExpiryUtc              : 3/9/2017 12:27:38 AM
    LastSynchronizedUtc         : 3/8/2017 11:57:38 PM
    TransportServerStatus       : Skipped
    TransportConfigStatus       : Skipped
    AcceptedDomainStatus        : Skipped
    RemoteDomainStatus          : Skipped
    SendConnectorStatus         : Skipped
    MessageClassificationStatus : Skipped
    RecipientStatus             : Skipped
    CredentialRecords           : Number of credentials 3
    CookieRecords               : Number of cookies 2

    [PS] C:\Windows\system32>Start-EdgeSynchronization


    RunspaceId     : bunchoflettersandnumbers
    Result         : Success
    Type           : Configuration
    Name           : EXCHET
    FailureDetails :
    StartUTC       : 3/9/2017 12:01:18 AM
    EndUTC         : 3/9/2017 12:01:18 AM
    Added          : 0
    Deleted        : 0
    Updated        : 0
    Scanned        : 0
    TargetScanned  : 0

    RunspaceId     : bunchoflettersandnumbers
    Result         : Success
    Type           : Recipients
    Name           : EXCHET
    FailureDetails :
    StartUTC       : 3/9/2017 12:01:18 AM
    EndUTC         : 3/9/2017 12:01:18 AM
    Added          : 0
    Deleted        : 0
    Updated        : 0
    Scanned        : 0
    TargetScanned  : 0

    Thursday, March 9, 2017 12:02 AM
  • Hi rmmill3,

    Did you use a smart host to route all outbound email ?

    If yes, the automatically created Send connector won't have the correct configuration. Then, after the Edge Subscription process is complete, you need to manually create a Send connector to the Internet. Create the Send connector inside the Exchange organization, and select the Edge Subscription as the source server for the connector. Select the Custom usage type and configure one or more smart hosts. This new Send connector will be replicated to the AD LDS instance on the Edge Transport server the next time EdgeSync synchronizes configuration data. You can force immediate EdgeSync synchronization by running the Start-EdgeSynchronization cmdlet on a Mailbox server. More details see: Route outbound email to a smart host .

    Best Regards,


    Niko Cheng
    TechNet Community Support


    Please remember to mark the replies as answers.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by Niko.Cheng Friday, March 10, 2017 9:04 AM
    Friday, March 10, 2017 2:57 AM