Exchange 2016 - Trying to figure out an email delay (250 2.0.0 Resetting) RRS feed

  • Question

  • Customer using GoldMine 2017 and an on-premises Exchange 2016 server for relay. For those that don't know GoldMine is pretty much a POP/SMTP client. Getting a few delays when sending out emails, wondering if there is anything I can do on the Exchange side to fix up the 250 2.0.0 Resetting. Seems that GoldMine tries once, gets hung up, and then tries again and it goes out. When it tries the second time, the email goes out in <0.2 seconds. Even with the reset all this happens in <2 seconds......so it is not a major delay, but enough that users are starting to notice it. Wondering if there is an Exchange setting I might be able to change to clean that up. Figure it might be something with MaxAcknowledgementDelay. I have that set to 00:00:00 right now.

    This particular log snip is from an internal user sending to 3 other internal users (same domain). Same thing happens when sending to users outside of the domain.

    2018-03-14T22:14:31.484Z,MAIL01\Internal Relay,08D5817B433361ED,0,,,+,,
    2018-03-14T22:14:31.484Z,MAIL01\Internal Relay,08D5817B433361ED,1,,,>,"220 internalrelay.domain.local Microsoft ESMTP MAIL Service ready at Wed, 14 Mar 2018 15:14:30 -0700",
    2018-03-14T22:14:31.485Z,MAIL01\Internal Relay,08D5817B433361ED,2,,,<,EHLO C1932.domain.local,
    2018-03-14T22:14:31.485Z,MAIL01\Internal Relay,08D5817B433361ED,3,,,>,250  internalrelay.domain.local Hello [] SIZE 37748736 PIPELINING DSN ENHANCEDSTATUSCODES 8BITMIME BINARYMIME CHUNKING,
    2018-03-14T22:14:31.490Z,MAIL01\Internal Relay,08D5817B433361ED,4,,,<,RSET,
    2018-03-14T22:14:31.490Z,MAIL01\Internal Relay,08D5817B433361ED,5,,,>,250 2.0.0 Resetting,
    2018-03-14T22:14:31.491Z,MAIL01\Internal Relay,08D5817B433361ED,6,,,<,MAIL FROM:<internalsender@domain.com>,
    2018-03-14T22:14:31.491Z,MAIL01\Internal Relay,08D5817B433361ED,7,,,*,08D5817B433361ED;2018-03-14T22:14:31.484Z;1,receiving message
    2018-03-14T22:14:31.491Z,MAIL01\Internal Relay,08D5817B433361ED,8,,,>,250 2.1.0 Sender OK,
    2018-03-14T22:14:31.491Z,MAIL01\Internal Relay,08D5817B433361ED,9,,,<,RCPT TO:<user1@domain.com>,
    2018-03-14T22:14:31.491Z,MAIL01\Internal Relay,08D5817B433361ED,10,,,>,250 2.1.5 Recipient OK,
    2018-03-14T22:14:31.492Z,MAIL01\Internal Relay,08D5817B433361ED,11,,,<,RCPT TO:<user2@domain.com>,
    2018-03-14T22:14:31.492Z,MAIL01\Internal Relay,08D5817B433361ED,12,,,>,250 2.1.5 Recipient OK,
    2018-03-14T22:14:31.492Z,MAIL01\Internal Relay,08D5817B433361ED,13,,,<,RCPT TO:<user3@domain.com>,
    2018-03-14T22:14:31.492Z,MAIL01\Internal Relay,08D5817B433361ED,14,,,>,250 2.1.5 Recipient OK,
    2018-03-14T22:14:31.494Z,MAIL01\Internal Relay,08D5817B433361ED,15,,,<,RSET,
    2018-03-14T22:14:31.494Z,MAIL01\Internal Relay,08D5817B433361ED,16,,,>,250 2.0.0 Resetting,
    2018-03-14T22:14:32.548Z,MAIL01\Internal Relay,08D5817B433361ED,17,,,<,RSET,
    2018-03-14T22:14:32.548Z,MAIL01\Internal Relay,08D5817B433361ED,18,,,>,250 2.0.0 Resetting,
    2018-03-14T22:14:32.562Z,MAIL01\Internal Relay,08D5817B433361ED,19,,,<,MAIL FROM:<internalsender@domain.com>,
    2018-03-14T22:14:32.562Z,MAIL01\Internal Relay,08D5817B433361ED,20,,,*,08D5817B433361ED;2018-03-14T22:14:31.484Z;2,receiving message
    2018-03-14T22:14:32.562Z,MAIL01\Internal Relay,08D5817B433361ED,21,,,>,250 2.1.0 Sender OK,
    2018-03-14T22:14:32.563Z,MAIL01\Internal Relay,08D5817B433361ED,22,,,<,RCPT TO:<user1@domain.com>,
    2018-03-14T22:14:32.563Z,MAIL01\Internal Relay,08D5817B433361ED,23,,,>,250 2.1.5 Recipient OK,
    2018-03-14T22:14:32.563Z,MAIL01\Internal Relay,08D5817B433361ED,24,,,<,RCPT TO:<user2@domain.com>,
    2018-03-14T22:14:32.563Z,MAIL01\Internal Relay,08D5817B433361ED,25,,,>,250 2.1.5 Recipient OK,
    2018-03-14T22:14:32.563Z,MAIL01\Internal Relay,08D5817B433361ED,26,,,<,RCPT TO:<user3@domain.com>,
    2018-03-14T22:14:32.563Z,MAIL01\Internal Relay,08D5817B433361ED,27,,,>,250 2.1.5 Recipient OK,
    2018-03-14T22:14:32.564Z,MAIL01\Internal Relay,08D5817B433361ED,28,,,<,DATA,
    2018-03-14T22:14:32.564Z,MAIL01\Internal Relay,08D5817B433361ED,29,,,>,354 Start mail input; end with <CRLF>.<CRLF>,
    2018-03-14T22:14:32.576Z,MAIL01\Internal Relay,08D5817B433361ED,30,,,*,,Proxy destination(s) obtained from OnProxyInboundMessage event. Correlation Id:4d16df2a-bb35-4115-a04f-1b619a6d3d77
    2018-03-14T22:14:32.685Z,MAIL01\Internal Relay,08D5817B433361ED,31,,,>,"250 2.6.0 <S0ZWS1g2OChaI18zMT1ENDk0NDYxNjcx@C1932> [InternalId=1120986464264, Hostname=MAIL01.domain.local] 6853 bytes in 0.103, 64.542 KB/sec Queued mail for delivery",
    2018-03-14T22:14:32.686Z,MAIL01\Internal Relay,08D5817B433361ED,32,,,<,QUIT,
    2018-03-14T22:14:32.688Z,MAIL01\Internal Relay,08D5817B433361ED,33,,,>,221 2.0.0 Service closing transmission channel,
    2018-03-14T22:14:32.688Z,MAIL01\Internal Relay,08D5817B433361ED,34,,,-,,Local

    Wednesday, March 14, 2018 11:19 PM

All replies

  • Hello,

    Thanks for contacting our forum.

    It seems that sometimes your application sends QUIT command before receiving reply for the "the final dot" of the message (250 for OK). Application is resetting the SMTP session maybe we need contact application vendor.

    Please refer to:  Smtp sending via Exchange some mails do not complete but still send - why?

    Please note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. And the changes made in the above blog is not supported officially by Microsoft.

    What’s the version of your Exchange server? Does restart the transport service works? It’s recommended to update to the latest version and check the results if it’s not.

    And if this issue only affect specific sender or specific sender IP.

    Hope it helps.

    Best Regards,
    Jason Chao

    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.

    • Proposed as answer by Jason.Chao Friday, March 16, 2018 2:24 AM
    Thursday, March 15, 2018 6:37 AM