Forum Discussion

walter-wodzien's avatar
walter-wodzien
Brass Contributor
Oct 15, 2024
Solved

new Exchange 2019 node tries to connect to Exchange 2016 on port 2525 when using SMTP relay

We had a pair of Exchange 2016 servers that are only used for SMTP relay and user management, one server in each geographic datacenter. We just added Exchange 2019 to the environment, one node in eac...
2016
Exchange Server
hybrid
  • walter-wodzien's avatar
    walter-wodzien
    Oct 17, 2024

    figured this out, turns out E2016 does not care much about the shadow copy while E2019 aggressively pursues it 🙂  after disabling shadow copy E2019 sends the message right away, one can actually see this in action by looking at the message tracking log (HAREDIRECT).  more info on the feature here: https://learn.microsoft.com/en-us/exchange/mail-flow/transport-high-availability/shadow-redundancy?view=exchserver-2019

walter-wodzien's avatar
walter-wodzien
Brass Contributor
Oct 17, 2024

figured this out, turns out E2016 does not care much about the shadow copy while E2019 aggressively pursues it 🙂  after disabling shadow copy E2019 sends the message right away, one can actually see this in action by looking at the message tracking log (HAREDIRECT).  more info on the feature here: https://learn.microsoft.com/en-us/exchange/mail-flow/transport-high-availability/shadow-redundancy?view=exchserver-2019