none
Mail Getting Stuck in Edge Transport

    Frage

  • I have a single Exchange 2013 Server with CAS and Mailbox roles on it.  Active Directory is 2008 R2 Forest and Domain functional level.  I also have a 2010 Edge Transport server that accepts mail from the internet and does its spam detection on it.  I have patched the 2010 Exchange Edge Server to SP3 CU 2.  I have also patched Exchange 2013 to this week to latest versions.  Mail flow will work for about 4 or 5 hours and then email will get stuck in the queue on the Edge server.  Mail still works internally on the 2013 server and I can also send mail out via the Edge.  I restart the Exchange Transport service on the 2013 Mailbox server and then I hit retry on the Edge Server queue and I get all the mail that was sitting in the queue.  This happens several times in a 24 hour period and I can not figure out what the reason is.  Nothing is glaring in the Event Logs.  The Edge transport queue has the error "451 5.7.3 Cannot achieve Exchange Server authentication." Attempted failover to alternate host , but that did not succeed. Either there are no alternative hosts, or delivery failed to all alternative hosts.

    Any help would be greatly appreciated.

    Thanks


    GSR

    Donnerstag, 3. Oktober 2013 20:03

Alle Antworten

  • Hello,

    From your description, I understand that when edge transport server receives messages from internet, these messages get stuck in the queue on the edge server, but you can send messages to internet via edge. If I have any misunderstanding, please free let me know.

    From the error, I recommend you use get-receiveconnector | fl to check the authentication and permission group for all receive connectors. (Note: The authentication should have Transport Layer Security, Exchange Server authentication, Integrated Windows authentication and Exchange Servers group selected. Permission group should have Exchange Users.)

    If these settings are ok, please make sure whether edge transport server can ping exchange 2013 mailbox successfully.

    If you have any feedback on our support, please click here


    Cara Chen
    TechNet Community Support

    Freitag, 4. Oktober 2013 03:37
    Moderator
  • Yes that is correct.  When they get stuck inbound on the edge server I can still send mail from my internal mailbox server outbound.  And yes all of the connectors and network access is available.  This works for 3 to 4 hours and then I get this condition.  So if I was missing any of those things I would think it would not work at all for a while.

    It just happened and I was able to send mail out.  But on my Edge Server I have an error in the queue.  451 4.4.0 Primary target responded with 451 5.7.3 can not achieve Exchange Server authentication.  Now if I restart the hub transport service on the 2013 HUB/Mailbox I can click retry on the edge queue and the things that are stuck in the queue will flow into our mailboxes.

    Thanks


    Greg


    GSR

    Freitag, 4. Oktober 2013 15:37
  • Hello,

    Sorry for delayed response.

    Please post the result for your all receive connector settings.

    I recommend you check the smtp receive protocol logging when the issue occurs. Before you use it, please enable it.

    Besides, I recommend you use network monitor to monitor your network again.

    If you have any feedback on our support, please click here


    Cara Chen
    TechNet Community Support

    Montag, 7. Oktober 2013 09:00
    Moderator
  • I'm using Exchange Server 2016 with one Mailbox in the LAN and one edge in the perimeter network.
    Everything is ok, exept that i can't receive mail from internet; it stick in queue showing No Matching Connector.
    I can send mail without any issue.
    Please i need your help
    Donnerstag, 17. Mai 2018 14:31