none
Exchange 2013 Anonymous Relay: RSET, "4.7.0 Timeout waiting for client input"

    Question

  • I have an internal Exchange 2013 server with an anonymous relay set up. Works flawlessly except for one situation.

    I have one client that has 2 apps on it, which need to use the relay to send email notifications. One of the apps works just fine, notifications are sent through the relay and delivered to the mailbox. The other app SAYS it sent successfully, but fails to route to the mailbox. It gets dropped as it hits the Exchange server, with an error in the protocol logs of: "4.7.0 Timeout waiting for client input"

    If I use authenticated email through port 587, the same application emails successfully. Yet, when I switch it back to using anonymous port 25, it fails.

    Here are the logs for 2 emails, the first one shows the successful application, the second is the application that is failing.

    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,0,192.168.1.25:25,192.168.1.50:23899,+,,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,1,192.168.1.25:25,192.168.1.50:23899,*,SMTPSubmit SMTPAcceptAnyRecipient SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,2,192.168.1.25:25,192.168.1.50:23899,>,"220 myserver.mydomain.local Microsoft ESMTP MAIL Service ready at Thu, 13 Apr 2017 15:28:45 -0400",
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,3,192.168.1.25:25,192.168.1.50:23899,<,EHLO mypc,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,4,192.168.1.25:25,192.168.1.50:23899,*,SMTPSubmit SMTPAcceptAnyRecipient SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,5,192.168.1.25:25,192.168.1.50:23899,>,250-myserver.mydomain.local Hello [192.168.1.50],
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,6,192.168.1.25:25,192.168.1.50:23899,>,250-SIZE 36700160,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,7,192.168.1.25:25,192.168.1.50:23899,>,250-PIPELINING,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,8,192.168.1.25:25,192.168.1.50:23899,>,250-DSN,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,9,192.168.1.25:25,192.168.1.50:23899,>,250-ENHANCEDSTATUSCODES,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,10,192.168.1.25:25,192.168.1.50:23899,>,250-STARTTLS,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,11,192.168.1.25:25,192.168.1.50:23899,>,250-8BITMIME,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,12,192.168.1.25:25,192.168.1.50:23899,>,250-BINARYMIME,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,13,192.168.1.25:25,192.168.1.50:23899,>,250 CHUNKING,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,14,192.168.1.25:25,192.168.1.50:23899,<,MAIL FROM:<app1@mydomain.local>,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,15,192.168.1.25:25,192.168.1.50:23899,*,SMTPSubmit SMTPAcceptAnyRecipient SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,16,192.168.1.25:25,192.168.1.50:23899,*,08D4690C273A4AAA;2017-04-13T19:28:46.356Z;1,receiving message
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,17,192.168.1.25:25,192.168.1.50:23899,>,250 2.1.0 Sender OK,
    2017-04-13T19:28:46.371Z,myserver\relay connector,08D4690C273A4AAA,18,192.168.1.25:25,192.168.1.50:23899,<,RCPT TO:<notifyemailaddy@mydomain.local>,
    2017-04-13T19:28:46.371Z,myserver\relay connector,08D4690C273A4AAA,19,192.168.1.25:25,192.168.1.50:23899,>,250 2.1.5 Recipient OK,
    2017-04-13T19:28:46.371Z,myserver\relay connector,08D4690C273A4AAA,20,192.168.1.25:25,192.168.1.50:23899,<,RSET,
    2017-04-13T19:28:46.371Z,myserver\relay connector,08D4690C273A4AAA,21,192.168.1.25:25,192.168.1.50:23899,*,Tarpit for '0.00:00:05',
    2017-04-13T19:28:51.387Z,myserver\relay connector,08D4690C273A4AAA,22,192.168.1.25:25,192.168.1.50:23899,>,250 2.0.0 Resetting,
    2017-04-13T19:28:57.496Z,myserver\relay connector,08D4690C273A4A9D,23,192.168.1.25:25,192.168.1.50:23812,<,NOOP,
    2017-04-13T19:28:57.496Z,myserver\relay connector,08D4690C273A4A9D,24,192.168.1.25:25,192.168.1.50:23812,*,Tarpit for '0.00:00:05',
    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,25,192.168.1.25:25,192.168.1.50:23812,>,250 2.0.0 OK,
    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,26,192.168.1.25:25,192.168.1.50:23812,<,MAIL FROM:<app2@mydomain.local>,
    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,27,192.168.1.25:25,192.168.1.50:23812,*,SMTPSubmit SMTPAcceptAnyRecipient SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,28,192.168.1.25:25,192.168.1.50:23812,*,08D4690C273A4A9D;2017-04-13T19:24:30.874Z;2,receiving message
    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,29,192.168.1.25:25,192.168.1.50:23812,>,250 2.1.0 Sender OK,
    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,30,192.168.1.25:25,192.168.1.50:23812,<,RCPT TO:<notifyemailaddy@mydomain.local>,
    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,31,192.168.1.25:25,192.168.1.50:23812,>,250 2.1.5 Recipient OK,
    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,32,192.168.1.25:25,192.168.1.50:23812,<,RSET,
    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,33,192.168.1.25:25,192.168.1.50:23812,>,250 2.0.0 Resetting,
    2017-04-13T19:34:03.227Z,myserver\relay connector,08D4690C273A4A9D,34,192.168.1.25:25,192.168.1.50:23812,>,451 4.7.0 Timeout waiting for client input,
    2017-04-13T19:34:03.227Z,myserver\relay connector,08D4690C273A4A9D,35,192.168.1.25:25,192.168.1.50:23812,-,,Local
    Monday, April 17, 2017 1:40 PM

All replies

  • I have an internal Exchange 2013 server with an anonymous relay set up. Works flawlessly except for one situation.

    I have one client that has 2 apps on it, which need to use the relay to send email notifications. One of the apps works just fine, notifications are sent through the relay and delivered to the mailbox. The other app SAYS it sent successfully, but fails to route to the mailbox. It gets dropped as it hits the Exchange server, with an error in the protocol logs of: "4.7.0 Timeout waiting for client input"

    If I use authenticated email through port 587, the same application emails successfully. Yet, when I switch it back to using anonymous port 25, it fails.

    Here are the logs for 2 emails, the first one shows the successful application, the second is the application that is failing.

    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,0,192.168.1.25:25,192.168.1.50:23899,+,,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,1,192.168.1.25:25,192.168.1.50:23899,*,SMTPSubmit SMTPAcceptAnyRecipient SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,2,192.168.1.25:25,192.168.1.50:23899,>,"220 myserver.mydomain.local Microsoft ESMTP MAIL Service ready at Thu, 13 Apr 2017 15:28:45 -0400",
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,3,192.168.1.25:25,192.168.1.50:23899,<,EHLO mypc,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,4,192.168.1.25:25,192.168.1.50:23899,*,SMTPSubmit SMTPAcceptAnyRecipient SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,5,192.168.1.25:25,192.168.1.50:23899,>,250-myserver.mydomain.local Hello [192.168.1.50],
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,6,192.168.1.25:25,192.168.1.50:23899,>,250-SIZE 36700160,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,7,192.168.1.25:25,192.168.1.50:23899,>,250-PIPELINING,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,8,192.168.1.25:25,192.168.1.50:23899,>,250-DSN,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,9,192.168.1.25:25,192.168.1.50:23899,>,250-ENHANCEDSTATUSCODES,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,10,192.168.1.25:25,192.168.1.50:23899,>,250-STARTTLS,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,11,192.168.1.25:25,192.168.1.50:23899,>,250-8BITMIME,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,12,192.168.1.25:25,192.168.1.50:23899,>,250-BINARYMIME,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,13,192.168.1.25:25,192.168.1.50:23899,>,250 CHUNKING,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,14,192.168.1.25:25,192.168.1.50:23899,<,MAIL FROM:<app1@mydomain.local>,
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,15,192.168.1.25:25,192.168.1.50:23899,*,SMTPSubmit SMTPAcceptAnyRecipient SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,16,192.168.1.25:25,192.168.1.50:23899,*,08D4690C273A4AAA;2017-04-13T19:28:46.356Z;1,receiving message
    2017-04-13T19:28:46.356Z,myserver\relay connector,08D4690C273A4AAA,17,192.168.1.25:25,192.168.1.50:23899,>,250 2.1.0 Sender OK,
    2017-04-13T19:28:46.371Z,myserver\relay connector,08D4690C273A4AAA,18,192.168.1.25:25,192.168.1.50:23899,<,RCPT TO:<notifyemailaddy@mydomain.local>,
    2017-04-13T19:28:46.371Z,myserver\relay connector,08D4690C273A4AAA,19,192.168.1.25:25,192.168.1.50:23899,>,250 2.1.5 Recipient OK,
    2017-04-13T19:28:46.371Z,myserver\relay connector,08D4690C273A4AAA,20,192.168.1.25:25,192.168.1.50:23899,<,RSET,
    2017-04-13T19:28:46.371Z,myserver\relay connector,08D4690C273A4AAA,21,192.168.1.25:25,192.168.1.50:23899,*,Tarpit for '0.00:00:05',
    2017-04-13T19:28:51.387Z,myserver\relay connector,08D4690C273A4AAA,22,192.168.1.25:25,192.168.1.50:23899,>,250 2.0.0 Resetting,
    2017-04-13T19:28:57.496Z,myserver\relay connector,08D4690C273A4A9D,23,192.168.1.25:25,192.168.1.50:23812,<,NOOP,
    2017-04-13T19:28:57.496Z,myserver\relay connector,08D4690C273A4A9D,24,192.168.1.25:25,192.168.1.50:23812,*,Tarpit for '0.00:00:05',
    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,25,192.168.1.25:25,192.168.1.50:23812,>,250 2.0.0 OK,
    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,26,192.168.1.25:25,192.168.1.50:23812,<,MAIL FROM:<app2@mydomain.local>,
    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,27,192.168.1.25:25,192.168.1.50:23812,*,SMTPSubmit SMTPAcceptAnyRecipient SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,28,192.168.1.25:25,192.168.1.50:23812,*,08D4690C273A4A9D;2017-04-13T19:24:30.874Z;2,receiving message
    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,29,192.168.1.25:25,192.168.1.50:23812,>,250 2.1.0 Sender OK,
    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,30,192.168.1.25:25,192.168.1.50:23812,<,RCPT TO:<notifyemailaddy@mydomain.local>,
    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,31,192.168.1.25:25,192.168.1.50:23812,>,250 2.1.5 Recipient OK,
    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,32,192.168.1.25:25,192.168.1.50:23812,<,RSET,
    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,33,192.168.1.25:25,192.168.1.50:23812,>,250 2.0.0 Resetting,
    2017-04-13T19:34:03.227Z,myserver\relay connector,08D4690C273A4A9D,34,192.168.1.25:25,192.168.1.50:23812,>,451 4.7.0 Timeout waiting for client input,
    2017-04-13T19:34:03.227Z,myserver\relay connector,08D4690C273A4A9D,35,192.168.1.25:25,192.168.1.50:23812,-,,Local

    Looks to me that issue is on the app or sending server side, not Exchange.
    Monday, April 17, 2017 2:53 PM
  • Yeah, looks that way to me too. Of course the vendor says "well, we get a send success message in our logs and its your exchange server dropping it, so not our problem."

    Strange thing is, if I configure the app authenticated over port 587, it works. Just seems to be an issue with the anonymous relay over port 25.

    Monday, April 17, 2017 3:00 PM
  • Hello

    tip:

    create new receive connector with same settings /relay, etc.. / and increase MaxAcknowledgementDelay  and tarpitinterval time


    sorry my english

    Monday, April 17, 2017 3:17 PM
  • Yeah, looks that way to me too. Of course the vendor says "well, we get a send success message in our logs and its your exchange server dropping it, so not our problem."

    Strange thing is, if I configure the app authenticated over port 587, it works. Just seems to be an issue with the anonymous relay over port 25.

    Their app is lying! lol.

    Is there any anti-virus or anti-malware installed on the servers? Wonder why the client is issuing a RSET command.

    Monday, April 17, 2017 3:20 PM
  • Well, their app isn't necessarily lying. I mean, the message is getting to the Exchange server. It's just that, for some reason, the Exchange server ends up dropping it. 

    I have disabled all anti-virus/firewalls from client and servers in troubleshooting, no difference.

    Sneff_Gabor, I will try your suggestion later today and report back.

    Monday, April 17, 2017 3:49 PM
  • Well, their app isn't necessarily lying. I mean, the message is getting to the Exchange server. It's just that, for some reason, the Exchange server ends up dropping it. 

    I have disabled all anti-virus/firewalls from client and servers in troubleshooting, no difference.

    Sneff_Gabor, I will try your suggestion later today and report back.


    Note that if you create a new receive connector based on sending ip, both apps will use it since its the same server sending. Might as well make those changes on the existing connector if that is the case.
    Monday, April 17, 2017 4:45 PM
  • Well, their app isn't necessarily lying. I mean, the message is getting to the Exchange server. It's just that, for some reason, the Exchange server ends up dropping it. 

    I have disabled all anti-virus/firewalls from client and servers in troubleshooting, no difference.

    Sneff_Gabor, I will try your suggestion later today and report back.


    Right, but its never accepted by Exchange.
     Exchange isn't dropping it, its being told by the app to RSET and its doing exactly what its told and following the RFCs
    Monday, April 17, 2017 4:46 PM
  • Tried creating new receive connector and changed tarp interval and MaxAcknowledgementDelay, same results. 

    If the RSET is initiated by the app, why is Exchange throwing: "4.7.0 Timeout waiting for client input"? Think the two are related to this source of the issue?


    Monday, April 17, 2017 6:15 PM
  • Tried creating new receive connector and changed tarp interval and MaxAcknowledgementDelay, same results. 

    If the RSET is initiated by the app, why is Exchange throwing: "4.7.0 Timeout waiting for client input"? Think the two are related to this source of the issue?


    Yea, I think so. Based on your logs:

    1. The client is saying reset and start all over:

    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,32,192.168.1.25:25,192.168.1.50:23812,<,RSET

    2. Exchange comes back and says sure and per RFC accepts the reset:

    2017-04-13T19:29:02.512Z,myserver\relay connector,08D4690C273A4A9D,33,192.168.1.25:25,192.168.1.50:23812,>,250 2.0.0 Resetting,

    https://www.ietf.org/rfc/rfc5321.txt

    4.1.1.5.  RESET (RSET)

       This command specifies that the current mail transaction will be
       aborted.  Any stored sender, recipients, and mail data MUST be
       discarded, and all buffers and state tables cleared.  The receiver
       MUST send a "250 OK" reply to a RSET command with no arguments.  A
       reset command may be issued by the client at any time.  It is
       effectively equivalent to a NOOP (i.e., it has no effect) if issued
       immediately after EHLO, before EHLO is issued in the session, after
       an end of data indicator has been sent and acknowledged, or
       immediately before a QUIT.  An SMTP server MUST NOT close the
       connection as the result of receiving a RSET; that action is reserved
       for QUIT (see Section 4.1.1.10).

    3. Then Exchange times out ( after waiting for 5 minutes! )waiting for the client to do something:

    2017-04-13T19:34:03.227Z,myserver\relay connector,08D4690C273A4A9D,34,192.168.1.25:25,192.168.1.50:23812,>,451 4.7.0 Timeout waiting for client input

    Monday, April 17, 2017 6:59 PM
  • Interesting.....

    I have sent this thread to the vendor. I'll update when I have more info.

    Monday, April 17, 2017 7:02 PM
  • Hello,

    Any update from your vendor?

    If the suggestion from Andy is correct, please be free to mark it as answer.
    Also, share the solution with us if possible.

    Best Regards,

    Allen Wang


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

    Wednesday, April 26, 2017 9:21 AM
    Moderator