none
Error: 421 4.4.0 failed to parse smtp response from Mailbox Transport Delivery: string did not match smtp response suffix regex <250 2.0.0 OK[resubmit=False]

    Question

  • mail from two exchange 2013 CU13 sending message from internal to internal Exchange 2016 CU3 sometimes mail gets stuck with message in title. It is the same situation as mentioned on blog http://exchangeserverpro.com/september-2016-updates-exchange-server-20162013/ where 

    We found out when “user A” is sending e-mail to ‘distribution group A’ !and! to himself, (Where “User A” is also member of “Distribution group A) e-mail will be delivered but gets stuck in queue with error

    how to fix?

    an event log error 4999 MSExchange Common occurs around the same time:

    Watson report about to be sent for process id: 7172, with parameters: E12, c-RTL-AMD64, 15.00.1210.003, edgetransport, M.Exchange.Transport, CheckIfSentFromHubAndReceivedByHub, FormatException, 63718994, 15.00.1210.002.
    ErrorReportingEnabled: True 


    rebooting the server did not help.

    doing windows updates did not help.

    updating to CU14 did not help.

    updating to .net 4.6.1 did not help.

    Thursday, November 10, 2016 4:14 PM

All replies

  • Hi,

    For further troubleshooting, I would like to collect some information.

    1. How many Exchange Server 2016 in your organization? Are they in DAG and all patched to CU3?
    2. 4999 is a common error event, please review application log for some other related error events.
    3. If you send messages between Exchange 2016 user mailbox, will this issue occur?

    Best Regards,

    Lynn-Li
    TechNet Community Support


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

    Friday, November 11, 2016 9:30 AM
    Moderator
  • Hi,

    Any updates?

    Another wondering, if userA send a message to himself or just send message to that distribution group, will this message stuck in queue?


    Best Regards,

    Lynn-Li
    TechNet Community Support


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

    Tuesday, November 15, 2016 12:48 PM
    Moderator
  • Hi

    We are currently running 1 exchange 2013 CU14 and 1 exchange 2016 server, we installed CU14 on the 2013 server and CU3 on the 2016 server last weekend and stated getting the same problem. Some, but not all emails sent to internal distribution groups where the sender is a member of the group sit in the queue with the following error.

    421 4.4.0 failed to parse smtp response from Mailbox Transport Delivery: string did not match smtp response suffix regex <250 2.0.0 OK[resubmit=False

    The weird thing is that it looks like the failed recipients are getting the email but it still just sits in the queue.

    Adrian

    Friday, November 18, 2016 5:17 AM
  • Hi Adrian,

    I had the same issue and now finished the Exchange migration to Exchange 2016 CU3.

    After all was migrated to Exchange 2016 I have uninstalled all Exchange 2013 servers and after that i can't reproduce the problem! All is normal now!

    I think there is a problem with Exchange 2016 CU3 in mixed environments (Exchange 2013 and Exchange 2016 older CU versions) when e-mail sent to distribution groups and to SELF is processed by the older version of Exchange.

    Regards, Maurice


    • Edited by Mause1981 Wednesday, November 30, 2016 9:43 AM
    Wednesday, November 30, 2016 9:42 AM
  • Hi , We are facing the same issue. did you find any workaround.
    Friday, December 30, 2016 4:00 AM
  • Hey did anyone find a workarround on this ? i'm facing excactly the same Issue, in my Exchange organization we use 2013CU14 and 2016CU4. the Distributiongroup has members from both MailboxServer, and the Error occurs only on those members on the Exchange2016CU4.

    Identität: svrExch01\15197\99522982183256
    Betreff: ###########
    Internetnachrichten-ID:mailserver
    Von Adresse:EmailSender
    Status: Wiederholen
    Größe (KB): 15
    Name der Nachrichtenquelle: SMTP:Default SVREXCH01
    Quell-IP: 192.168.0.24
    SCL (Spam Confidence Level): -1
    Empfangsdatum: 11.01.2017 12:44:07
    Ablaufzeit: 13.01.2017 12:44:07
    Letzter Fehler: 421 4.4.0 failed to parse smtp response from Mailbox Transport Delivery: string did not match smtp response suffix regex <250 2.0.0 OK[resubmit=False][Microsoft.Exchange.Transport.MailboxTransport.SmtpInClientHostname=svrex01]>

    Thanks for your Support

    Best Regards




    • Edited by vilickgaby Thursday, January 12, 2017 8:06 AM
    Thursday, January 12, 2017 7:45 AM
  • We were having the same issue since we started the migration from Exchange 2013 CU12 to Exchange 2016 CU3. We didn't test updating to latest CUs but I saw others having no success with that. So the workaround is to export the messages in the Exchange 2013 queue and drop them on the Exchange 2016 server.

    Here are the steps:

    1) Run this on Exchange 2013; this is for one QUEUE ID at a time; you might change it to run for all stuck messages at once:

    $array = @(Get-Message -Queue "WHAT\9" -ResultSize unlimited)
    $array | ForEach-Object {Suspend-Message -Identity $_.Identity -Confirm:$false}
    $array | ForEach-Object {$i++;Export-Message $_.Identity | AssembleMessage -Path ("C:\TEMP\MailQueue-Manual\"+ $i +".eml")}
    $array | ForEach-Object {Remove-Message -Identity $_.Identity -Confirm:$false}

    2) Copy/Drop the *.eml files to C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Pickup on the Exchange 2016 server.

    • Proposed as answer by P. Cesar Gamez Saturday, February 4, 2017 12:26 AM
    Saturday, February 4, 2017 12:26 AM
  • Same issue here - we are on all latest Exchange 2013 and Exchange 2016 updates and are seeing exactly the same error
    Friday, February 10, 2017 6:24 PM
  • Suddenly start getting this error yesterday. Emails are queuing from inside and outside the company.

    I'm on EX2013 CU15, and EX2016 CU4.

    So far this, and another thread is the only place I see activity. I did notice that CU16 and CU5 just got released. Anyone else with these issues???

    Tuesday, March 21, 2017 7:23 PM
  • I've been reviewing the messages in the queue, and it appears as though all the messages were indeed received by the recipients, but still gets stuck in queue.

    I'm waiting on a call from Microsoft regarding this, but looks like (another) bug.

    My goal will be to export the messages from queue as P. Cesar Gamez mentioned (for safe keeping), and decommission 2013 as soon as possible.

    It's funny how the migration from 2007 was so laborious, but worked so well, while the migration from 2013 to 2016 was so easy and works like crap.

    Wednesday, March 22, 2017 12:50 PM
  • Any news on this? We just upgraded to EX2K16 CU4 and EX2K13 CU15 and still have these problems. Most notably messages to large distribution lists get regulary stuck in the queue. It seems most of them are delivered correctly (emphasis on 'most'), but the sender still gets an NDR when the message expires.

    Yes, I could check the queue every morning and export stuck messages, but that's not optimal, to put it mildly.

    I consider contacting Microsoft Support, but fear the costs if they somehow pin this on us.

    Tuesday, March 28, 2017 7:35 AM