Announcement

Collapse
No announcement yet.

"421 4.4.1 Connection timed out" Exchange 2007 Error

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • "421 4.4.1 Connection timed out" Exchange 2007 Error

    Hello,

    We are currently seeing these errors on e-mails that have 5MB+ attachments. Mail with smaller or no attachments get though OK. This is multi-domain - checks from hotmail.com, gmail.com, yahoo.com, <myisp>.com as well as real life e-mails from a couple of big companies are all experiencing this problem. Senders usually get warnings about the delay and then finally a failure messge; e.g. from Hotmail:

    Warning:
    Code:
    This is an automatically generated Delivery Status Notification.
    THIS IS A WARNING MESSAGE ONLY.
    YOU DO NOT NEED TO RESEND YOUR MESSAGE.
    Delivery to the following recipients has been delayed.
    [email protected]
    
    Reporting-MTA: dns;blu0-omc1-s12.blu0.hotmail.com
    Received-From-MTA: dns;BLU106-W5
    Arrival-Date: Fri, 4 Dec 2009 13:48:32 -0800
    Final-Recipient: rfc822;[email protected]
    Action: delayed
    Status: 4.4.7
    Will-Retry-Until: Sun, 6 Dec 2009 13:48:33 -0800
    Failure:
    Code:
    This is an automatically generated Delivery Status Notification.
    Unable to deliver message to the following recipients, due to being unable to connect successfully to the destination mail server.
    [email protected]
    
    Reporting-MTA: dns;blu0-omc1-s12.blu0.hotmail.com
    Received-From-MTA: dns;BLU106-W5
    Arrival-Date: Fri, 4 Dec 2009 13:48:32 -0800
    Final-Recipient: rfc822;[email protected]
    Action: failed
    Status: 4.4.7
    After enabling SMTP receive logs, checking them, and searching the internet I concluded - from http://social.technet.microsoft.com/...7-f99c2b961563 and an experts-exchange.com link - that I could solve the issue by issuing the following Exchange Management Shell command:
    Set-ReceiveConnector -identity "<my receive connector>" -BinaryMimeEnabled $false -ChunkingEnabled $false

    Before the change:
    Code:
    SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders	Set Session Permissions
    220 remote.xxxxxxxx.com Microsoft ESMTP MAIL Service ready at Mon, 7 Dec 2009 16:12:04 +0000	
    EHLO ey-out-1920.google.com	
    250-remote.xxxxxxxx.com Hello [74.125.78.144]	
    250-SIZE 10485760	
    250-PIPELINING	
    250-DSN	
    250-ENHANCEDSTATUSCODES	
    250-STARTTLS	
    250-AUTH	
    250-8BITMIME	
    250-BINARYMIME	
    250 CHUNKING	
    MAIL FROM:<[email protected]>	
    08CC4094CAFD3F4E;2009-12-07T16:12:04.659Z;1	receiving message
    250 2.1.0 Sender OK	
    RCPT TO:<[email protected]>	
    250 2.1.5 Recipient OK	
    DATA	
    354 Start mail input; end with <CRLF>.<CRLF>	
    421 4.4.1 Connection timed out
    After the change:
    Code:
    SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders	Set Session Permissions
    220 remote.xxxxxxxx.com Microsoft ESMTP MAIL Service ready at Mon, 7 Dec 2009 20:52:57 +0000	
    EHLO ey-out-1920.google.com	
    250-remote.xxxxxxxx.com Hello [74.125.78.145]	
    250-SIZE 10485760	
    250-PIPELINING	
    250-DSN	
    250-ENHANCEDSTATUSCODES	
    250-STARTTLS	
    250-AUTH	
    250 8BITMIME	
    MAIL FROM:<[email protected]>	
    08CC4094CAFD3F52;2009-12-07T20:52:57.988Z;1	receiving message
    250 2.1.0 Sender OK	
    RCPT TO:<[email protected]>	
    250 2.1.5 Recipient OK	
    DATA	
    354 Start mail input; end with <CRLF>.<CRLF>	
    421 4.4.1 Connection timed out
    From the same log, just to show that messages without attachments do get through:
    Code:
    SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders	Set Session Permissions
    220 remote.xxxxxxxx.com Microsoft ESMTP MAIL Service ready at Mon, 7 Dec 2009 20:08:22 +0000	
    EHLO ey-out-1920.google.com	
    250-remote.xxxxxxxx.com Hello [74.125.78.147]	
    250-SIZE 10485760	
    250-PIPELINING	
    250-DSN	
    250-ENHANCEDSTATUSCODES	
    250-STARTTLS	
    250-AUTH	
    250-8BITMIME	
    250-BINARYMIME	
    250 CHUNKING	
    MAIL FROM:<[email protected]>	
    08CC4094CAFD3F50;2009-12-07T20:08:23.740Z;1	receiving message
    250 2.1.0 Sender OK	
    RCPT TO:<[email protected]>	
    250 2.1.5 Recipient OK	
    DATA	
    354 Start mail input; end with <CRLF>.<CRLF>	
    250 2.6.0 <[email protected]> Queued mail for delivery	
    QUIT	
    221 2.0.0 Service closing transmission channel
    Can anyone suggest what next to try / where I should look?
    Thanks.

    chrisinparis
    Last edited by chrisinparis; 7th December 2009, 22:54. Reason: Minor formatting correction

  • #2
    Re: &quot;421 4.4.1 Connection timed out&quot; Exchange 2007 Error

    What is the connectiontimeout interval on the receive connector? By default on a Hub Transport it is 10mins, on an Edge server it is 5mins. It could be that the mail items are taking longer than these thresholds to complete the transaction.

    Check the connection timeout using

    Get-ReceiveConnector | fl Id*,*connectiontime*

    Change the ConnectionTimeOut value

    Set-Receiveconnector <NameofConnector> -ConnectionTimeOut 00:20:00

    This will change it to 20mins for instance.

    See http://technet.microsoft.com/en-us/l.../bb125140.aspx for more info.

    Shaun

    Comment


    • #3
      Re: &quot;421 4.4.1 Connection timed out&quot; Exchange 2007 Error

      Thanks for the suggestion shauncroucher, I changed the timeout for the internet-recieve connection and this time an e-mail with a 7.85 MB attachment (from hotmail) got through.

      However, an e-mail with an attachment of 9.2 MB, sent first from gmail and then tried again from hotmail does not get through. From the exchange smtp receive log:
      Code:
      552 5.3.4 Message size exceeds fixed maximum message size,
      But I'd have thought that would still get through, as the max mesage size is 10 MB:
      Code:
      [PS] C:\Windows\System32>get-transportconfig
      
      
      ClearCategories                : True
      DSNConversionMode              : UseExchangeDSNs
      GenerateCopyOfDSNFor           : {5.4.8, 5.4.6, 5.4.4, 5.2.4, 5.2.0, 5.1.4}
      InternalSMTPServers            : {127.0.0.1}
      JournalingReportNdrTo          : <>
      MaxDumpsterSizePerStorageGroup : 18MB
      MaxDumpsterTime                : 7.00:00:00
      MaxReceiveSize                 : 10MB
      MaxRecipientEnvelopeLimit      : 5000
      MaxSendSize                    : 10MB
      TLSReceiveDomainSecureList     : {}
      TLSSendDomainSecureList        : {}
      VerifySecureSubmitEnabled      : False
      VoicemailJournalingEnabled     : True
      WritingBrandingInDSNEnabled    : True
      Xexch50Enabled                 : True
      So a few followup questions:
      1. Should my message with an attachment of 9.2 MB be getting through? What can I check?
      2. Should I try setting -BinaryMimeEnabled and -ChunkingEnabled back to $true? Or was this a 'good' change as my 5 MB attachment e-mail got through immediately following this change?
      3. Is 30 minutes a reasonable timeout? Any reason not increase or decrease this?

      Thanks.
      chrisinparis

      Comment


      • #4
        Re: &quot;421 4.4.1 Connection timed out&quot; Exchange 2007 Error

        1) Check my blog here for message size checking:

        http://exchangeshell.wordpress.com/2...ing-powershell

        Note that depending on conversion algorithms for MIME/TNEF etc and the headers of the message, the size of a message may change during transit, 0.8MB does seem on the high side but it is still possible I guess. This may be the problem here. Try changing the size limit to 15 and try again.

        2) I would always try to leave settings like that at default if possible and only change if necessary, so if you change them back to what they were and test. If you find it causes further problems then you can always change back again.

        3) Note that the higher the timeout, the longer an SMTP connection can remain open for an email message. The idle time is still set at a lower level so that will offer some protection again a DOS attach for example. If you need more time for larger mail items to get through then I guess you will need to maintain a longer timeout value here. See how things go, if you need to readjust there is nothing stopping you

        Shaun

        Comment


        • #5
          Re: &quot;421 4.4.1 Connection timed out&quot; Exchange 2007 Error

          Thanks for answering my questions. I have not played around with any more parameters since, and now 'smaller' attachments are no longer getting through

          E.g. An e-mail with a 3.5 MB attachment sent from Gmail tries several times to get through but ultimately fails e.g.
          Google
          Code:
          Technical details of temporary failure:=20
          ... 
          The error that the other server return=
          ed was: 451 451 4.7.0 Timeout waiting for client input (state 18).
          
          Technical details of permanent failure:=20
          ... 
          The error that the other server return=
          ed was: 451 451 4.7.0 Timeout waiting for client input (state 18).
          Exchange
          From the Exchange smtp receive log:
          Code:
          SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders
          ...
          250 2.1.0 Sender OK
          RCPT TO:<[email protected]>
          250 2.1.5 Recipient OK
          DATA
          354 Start mail input; end with <CRLF>.<CRLF>
          451 4.7.0 Timeout waiting for client input
          Things come to mind:
          1. There's still an issue with my config (I only changed the parameter for internet connector i.e. identity = 'Windows SBS Internet Receive <server>'; should I have changed the ConnectionTimeout parameter for the one with the identity of 'External-recv' or 'Default <server>').

          2. The internet connection is poor (ADSL, I looked at the line characteristics and they looked 'poor' but the line should be good enough for an e-mail with a 5MB attachment, and downloading medium to large files (windows updates, VMWare applications etc) goes without any problems).

          Any advice as to what to check next, config or possibly the line?
          Thanks, and Happy New Year.

          Comment


          • #6
            Re: &quot;421 4.4.1 Connection timed out&quot; Exchange 2007 Error

            In case someone finds this by searching through the archives... Finally fixed this. There were two problems it seems:

            1. Ethernet ports on the router were going bad.
            Found this out by using ping as described at http://support.microsoft.com/kb/314825/en-us . Replaced router, fixed half of the problem.

            2. Global transport rule
            Although the receive connector and the global transportconfig maxreceivesize parameters were both set to accept e-mails of up to 15MB, the global transportconfig maxsendsize was set to 10MB. Should not matter I thought, it's for sending (a 9.2MB e-mail send internally from one user to another got through OK). But I was wrong (now I think it applies to 'sending' from the recieve smtp connector to the message store) - doing a set-transportconfig -maxsendsize 15MB fixed the problem. My test 9.2MB from an internet e-mail address got through.
            Last edited by chrisinparis; 9th April 2010, 22:27. Reason: fixed typo

            Comment

            Working...
            X