Forum Discussion

Urs01's avatar
Urs01
Copper Contributor
Jan 05, 2024
Solved

Exchange Routing Problem - Edge server with scoped connector

We have 2 Exchange Server 2016 in AD-Site A with a send connector to the internet (not scoped) with adress space * We have 2 Exchange Server 2019 in AD-Site B with 2 Edge Servers. We have a created ...
Exchange Server
  • AnnTaeYoun's avatar
    AnnTaeYoun
    Jan 09, 2024

    Urs01 

    By design, this is the intended behavior.
    When selecting a Send connector, Exchange always prefers the most specific (scoped to a specific domain) Send connector.
    This is due to Exchange's routing behavior, where scoped Send connectors are given higher priority.

AnnTaeYoun's avatar
AnnTaeYoun
MVP
Jan 08, 2024

Urs01 

Check the priorities of your connectors!
Connector priority determines the order in which connectors are used to route messages.

Urs01's avatar
Urs01
Copper Contributor
Jan 08, 2024
I can't see any priorities, do you mean the cost value on the addressspace on the connector?
  • AnnTaeYoun's avatar
    AnnTaeYoun
    MVP
    Jan 08, 2024
    Below view command.
    AddressSpaces is value "1","2".

    [PS] C:\Windows\system32>Get-SendConnector

    Identity AddressSpaces Enabled
    -------- ------------- -------
    SMTP {SMTP:*;1} True
    contoso.local {SMTP:contoso.local;2} True
    • Urs01's avatar
      Urs01
      Copper Contributor
      Jan 08, 2024

      AnnTaeYoun 

      It didn't help. Exchange always seems to take the most specific send connector and doesn't take into account cost or "scoped send connector"

      • AnnTaeYoun's avatar
        AnnTaeYoun
        MVP
        Jan 09, 2024

        Urs01 

        By design, this is the intended behavior.
        When selecting a Send connector, Exchange always prefers the most specific (scoped to a specific domain) Send connector.
        This is due to Exchange's routing behavior, where scoped Send connectors are given higher priority.

Resources