none
Three server relay RRS feed

  • Question

  • Let me explain the issue because there are two of them (we think).

    We have three exchange servers.

    A. Exchange 2007 (in a WS2008 AD)

    B. Exchange 2013 (in a WS2012 AD)

    C. Exchange 2019 (in a WS2019 AD)

    There are several domain names on server B, but only one domain that is shared between all three servers.

    For over a year, A and B shared a domain, then C was installed this year (two weeks ago).

    None of the servers are in the same AD.

    External mail for the sharedomain.com comes to B.

    If it gets mail for users that aren't on B it relays to A.

    When someone on A sends e-mail to a user not on A it gets relayed to B.

    Once C was introduced, C was told to forward to B, B still to A, and A changed to forward to C.

    It was working for a couple of days then stopped.

    Also, server C will not send any e-mail at all, even though the logs say e-mail is being handed off.

    Even Hotmail is not receiving e-mail from server C.

    Also we're assuming that B stopped receiving from C but can't show it.

    Any help is appreciated.


    Alert from Microsoft Forum

    Tuesday, July 2, 2019 4:09 PM

All replies

  • What change was implemented to make it stop? ;)

    Can you run a get-sendconnector | fl on the C environment and post the results?

    How many NICs are in each of the the 2019 Mailbox servers? 


    Tuesday, July 2, 2019 4:31 PM
  • [PS] C:\Windows\system32>get-sendconnector | fl

    AddressSpaces                : {SMTP:uac.org;1}
    AuthenticationCredential     :
    CloudServicesMailEnabled     : False
    Comment                      :
    ConnectedDomains             : {}
    ConnectionInactivityTimeOut  : 00:10:00
    ConnectorType                : Default
    DNSRoutingEnabled            : False
    DomainSecureEnabled          : False
    Enabled                      : True
    ErrorPolicies                : Default
    ForceHELO                    : False
    Fqdn                         : srv5.thehierarchy.net
    FrontendProxyEnabled         : False
    HomeMTA                      : Microsoft MTA
    HomeMtaServerId              : THS025
    Identity                     : External THCI to THII relay
    IgnoreSTARTTLS               : False
    IsScopedConnector            : False
    IsSmtpConnector              : True
    MaxMessageSize               : 100 MB (104,857,600 bytes)
    Name                         : External THCI to THII relay
    Port                         : 25
    ProtocolLoggingLevel         : None
    Region                       : NotSpecified
    RequireOorg                  : False
    RequireTLS                   : False
    SmartHostAuthMechanism       : None
    SmartHosts                   : {mail.thehierarchy.net}
    SmartHostsString             : mail.thehierarchy.net
    SmtpMaxMessagesPerConnection : 20
    SourceIPAddress              : 0.0.0.0
    SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
    SourceTransportServers       : {THS025}
    TlsAuthLevel                 :
    TlsCertificateName           :
    TlsDomain                    :
    UseExternalDNSServersEnabled : False
    AddressSpaces                : {SMTP:*;1}
    AuthenticationCredential     :
    CloudServicesMailEnabled     : False
    Comment                      :
    ConnectedDomains             : {}
    ConnectionInactivityTimeOut  : 00:10:00
    ConnectorType                : Default
    DNSRoutingEnabled            : True
    DomainSecureEnabled          : False
    Enabled                      : True
    ErrorPolicies                : Default
    ForceHELO                    : False
    Fqdn                         :
    FrontendProxyEnabled         : False
    HomeMTA                      : Microsoft MTA
    HomeMtaServerId              : THS025
    Identity                     : THCI Primary Send Connector
    IgnoreSTARTTLS               : False
    IsScopedConnector            : False
    IsSmtpConnector              : True
    MaxMessageSize               : 35 MB (36,700,160 bytes)
    Name                         : THCI Primary Send Connector
    Port                         : 25
    ProtocolLoggingLevel         : None
    Region                       : NotSpecified
    RequireOorg                  : False
    RequireTLS                   : False
    SmartHostAuthMechanism       : None
    SmartHosts                   : {}
    SmartHostsString             :
    SmtpMaxMessagesPerConnection : 20
    SourceIPAddress              : 0.0.0.0
    SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
    SourceTransportServers       : {THS025}
    TlsAuthLevel                 :
    TlsCertificateName           :
    TlsDomain                    :
    UseExternalDNSServersEnabled : False
    [PS] C:\Windows\system32>

    Alert from Microsoft Forum

    Tuesday, July 2, 2019 4:50 PM
  • You should know that I removed the connectors, and put them back.

    Mail then flowed from C to B, and then to A, but Hotmail still received nothing.

    It was back mail (meaning all of the tests arrived together).

    C receives mail though, which means that B gets its first, relays to A, and A relays to C.

    Since I see that e-mails were sent, I retried some tests for the relay but none worked.

    I e-mailed server C from Hotmail and that was received so I replied to that, and that works, but not sending a new e-mail (without replying) to Hotmail.


    Alert from Microsoft Forum

    Tuesday, July 2, 2019 5:13 PM
  • Nothing was done prior to it stopping other than a DNS change, which was rectified but the what I state in the previous response is still the case.

    Also, users on C can receive e-mail, but not on B that has to pass through C


    Alert from Microsoft Forum

    Tuesday, July 2, 2019 5:15 PM
  • Hi DarkAngel11,

     

    I understand there are three Exchange servers coexistence. Since Exchange 2007 had stopped supports on 7/12/2011, and the requirement of supported coexistence scenarios for Exchange 2019 is Exchange 2013 or later versions. It's suggested updating the Exchange 2007 server to Exchange 2016 or later, and then retire the legacy server. The links below for your reference:

     

    https://support.microsoft.com/en-us/lifecycle/search/?p1=10926&wa=wsignin1.0

    https://docs.microsoft.com/en-us/Exchange/plan-and-deploy/system-requirements?view=exchserver-2019#supported-coexistence-scenarios-for-exchange-2019

     

    Regards,

    Kelvin Deng


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, July 3, 2019 7:37 AM
  • Hi DarkAngel11,

     

    I am writing here to confirm with you how the thing going now?

     

    If you need further help, please provide more detailed information, so that we can give more appropriate suggestions

     

    Regards,

    Kelvin Deng


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, July 8, 2019 1:36 AM
  • Kelvin your reply stopped others from providing any assistance.


    Alert from Microsoft Forum

    Monday, July 8, 2019 3:00 AM
  • Hi DarkAngel11,

     

    I understand the three Exchange servers are in the sharedomain.com. Before serve C add in, the mail flow is clear. After adding server C, you mentioned 'C was told to forward to B' and ' A changed to forward to C.' The following questions comes to my mind.

     

    1.How did you realize 'forward'? Set up connectors or rule? Could you describe the detailed steps?

    2.What messages of C forward to B? Inbound messages or Outbound messages of B?

    3.What messages of A forward to C? Inbound messages or Outbound messages of A?

    4.What's the purpose of  'A changed to forward to C'?

     

    For better understand, could you kindly provide your current topology mail flow chart?

     

    Regards,

    Kelvin Deng


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, July 10, 2019 2:34 AM
  • Hi ,

     

    I am writing here to confirm with you how the thing going now?

     

    If you need further help, please provide more detailed information, so that we can give more appropriate suggestions

     

    Regards,

    Kelvin Deng


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, July 15, 2019 8:48 AM