locked
Delay in sending email to a certain domain - Exchange 2007 RRS feed

  • Question

  • Hello all,
    We seem to be having a slowdown from our email being delivered to a certain domain. This only appears to be happening when we send to just this one domain. The person on the other end sent header information, which is shown below. Besides this, we are getting an email from our Exchange server saying the delivery has been delayed. It does eventually get delivered some time later. Thanks for the assistance!

    ---------------------------------------------------------

    Microsoft Mail Internet Headers Version 2.0

    Received: from outbound.mailstreet2003.net ([10.0.25.92]) by outbound.mailstreet2003.net with Microsoft SMTPSVC(6.0.3790.3959);

                     Thu, 17 Sep 2009 02:40:06 -0400

    Received: from p01c12m032.mxlogic.net ([208.65.145.247]) by outbound.mailstreet2003.net with Microsoft SMTPSVC(6.0.3790.3959);

                     Thu, 17 Sep 2009 02:40:06 -0400

    Received: from unknown [208.125.104.154]

                    by p01c12m032.mxlogic.net (mxl_mta-6.3.0-4)

                    with SMTP id 5c9d1ba4.0.189767.00-011.245289.p01c12m032.mxlogic.net (envelope-from <user1@domain1.com>);

                    Thu, 17 Sep 2009 00:40:06 -0600 (MDT)

    Received: from server.domain.local ([192.168.1.31]) by server.domain.local

     ([192.168.1.31]) with mapi; Wed, 16 Sep 2009 07:52:38 -0400

    From: User 1 <user1@domain1.com>

    To: "User 2" <user2@domain2.ORG>

    Date: Wed, 16 Sep 2009 07:52:37 -0400

    Subject: RE: email

    Thread-Topic: email

    Thread-Index: Aco1V8b03RESEnJwQHa1D5M6eMf/HQBbFb+w

    Message-ID: <08DF3523698E854C8CFC712E4B1EC38EAAA300EC05@server.domain.local>

    References: <8FD8FDD3DC42E145B5B26B06FA5358690542032B@mse0be1.mailstreet2003.net>

    In-Reply-To: <8FD8FDD3DC42E145B5B26B06FA5358690542032B@mse0be1.mailstreet2003.net>

    Accept-Language: en-US

    Content-Language: en-US

    X-MS-Has-Attach: yes

    X-MS-TNEF-Correlator:

    acceptlanguage: en-US

    Content-Type: multipart/related;

                    boundary="=_reb-r512DF473-t4AB1D9C6";

                    type="multipart/alternative"

    MIME-Version: 1.0

    X-Processed-By: Rebuild v2.0-0

    X-Spam: [F=0.2727272924; B=0.500(0); CM=0.500; MH=0.500(2009091701); R=0.600(10981620539); S=0.200(2009090401); SC=none]

    X-MAIL-FROM: <user1@domain1.com>

    X-SOURCE-IP: [(unknown)]

    X-AnalysisOut: [v=1.0 c=1 a=MZCyh37EnKEBsuG3Aq+LJA==:17 a=Eg5hcHOYAAAA:8 a]

    X-AnalysisOut: [=wHIULTkva4a8YQ2JflAA:9 a=0UVtKI-VQCUdv3szCewA:7 a=GV59J3F]

    X-AnalysisOut: [GiLiPMuLCg-stRgqny20A:4 a=CS9kbu5uwm8A:10 a=pFKgF9ukDCUA:1]

    X-AnalysisOut: [0 a=VsjRE4IVNw0A:10 a=-KmVHm8FC7kA:10 a=Lhvt-li1OV4A:10 a=]

    X-AnalysisOut: [yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=tpQhr_hAHxF-NWyXemAA:9 a]

    X-AnalysisOut: [=bIuN9XMeNfGhN9jk6-oA:7 a=RYhYRZz_me5VGVbDvWhBQFC9t4MA:4 a]

    X-AnalysisOut: [=TS0TvMHwFkXPtt9f1KAA:9 a=XaZgxXhwC31Z4GuoJLilngHIyPUA:4 a]

    X-AnalysisOut: [=KQqxNPgzF0kA:10 a=BhRmhaFIb5rMjBJ6:18]

    Return-Path: user1@domain1.com

    X-OriginalArrivalTime: 17 Sep 2009 06:40:06.0686 (UTC) FILETIME=[B1BE13E0:01CA3761]

     

    --=_reb-r512DF473-t4AB1D9C6

    Content-Type: multipart/alternative;

                    boundary="=_reb-r3A51A0DD-t4AB1D9C6"

     

    --=_reb-r3A51A0DD-t4AB1D9C6

    Content-Type: text/plain; charset="us-ascii"

    Content-Transfer-Encoding: quoted-printable

     

    --=_reb-r3A51A0DD-t4AB1D9C6

    Content-Type: text/html; charset="us-ascii"

    Content-Transfer-Encoding: quoted-printable

     

     

    --=_reb-r3A51A0DD-t4AB1D9C6--

    --=_reb-r512DF473-t4AB1D9C6

    Content-Type: image/jpeg; name="image001.jpg"

    Content-Description: image001.jpg

    Content-Disposition: inline; filename="image001.jpg"; size=2286;

                    creation-date="Wed, 16 Sep 2009 07:52:38 GMT";

                    modification-date="Wed, 16 Sep 2009 07:52:38 GMT"

    Content-ID: <image001.jpg@01CA36A2.A8315E50>

    Content-Transfer-Encoding: base64

     

     

    --=_reb-r512DF473-t4AB1D9C6--

    Thursday, September 17, 2009 6:16 PM

Answers

  • Hi,

    Is the issue only occured on one domain or some domains?

    From the tesing result by using smtpdiag.exe, it seems that the problematic domain could not be connected via 25 port. This indicates the destination server has the issue rather than your Exchange server's problem. I suggest we contact the problematic domain to confirm and obtain more information on this issue.

    Thanks

    Allen



    • Marked as answer by Allen Song Friday, September 25, 2009 9:55 AM
    Wednesday, September 23, 2009 3:28 AM
  • Hi

    As Allen suggested check with MXLOGIC.Net, as per the test you have a single Send connector to external  with relaying enabled to Mxlogic.net.

    As Allen suggested is this the same with other domains, if not send the smtpdiag.exe report of any external domain such as Gmail or any..

    Thanks
    Hari

    • Marked as answer by Allen Song Friday, September 25, 2009 9:55 AM
    Wednesday, September 23, 2009 6:40 AM

All replies

  • Is this happening to only one domain?  Try submitting message to this domain from telnet and see does it takes huge time even to display the banner?

    http://support.microsoft.com/kb/153119
    Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|
    Friday, September 18, 2009 5:08 AM
  • Unfortunately when I try to ping mail.domain2.org I don't get a response. It does take a little bit of time, about 25 seconds or so. I'm unable to telnet to port 25 of the mail server either.
    Friday, September 18, 2009 3:50 PM
  • On Thu, 17-Sep-09 18:16:59 GMT, NuttySquirrel wrote:

    >Hello all,We seem to be having a slowdown from our email being delivered to a certain domain. This only appears to be happening when we send to just this one domain. The person on the other end sent header information, which is shown below. Besides this, we are getting an email from our Exchange server saying the delivery has been delayed. It does eventually get delivered some time later. Thanks for the assistance!---------------------------------------------------------

    rt host to deliver your mail? Or is the
    "domain2.org" using servers in the mxlogic.net domain for their mail
    exchanger?

    You might want to check you transport's send logs to see what the
    conversation between your server (208.125.104.154) and the other MTA
    (208.65.145.247?) looks like. Are you getting 4xx status codes from
    their MTA (graylisting, maybe?)?

    What's your message retry frequency? Look at the "Limits" tab on your
    HT (or Edge) server's property page. If it's set too short (or too
    long) you can have problems with graylists where they either refus the
    connection if it's retried too soon, or "forget" the last connection
    from the IP because the retry comes too late. The problem can be
    exacerbated if there are multiple MTAs in the reveiving domain and
    each retry hits a different one.

    >Microsoft Mail Internet Headers Version 2.0
    >Received: from outbound.mailstreet2003.net ([10.0.25.92]) by outbound.mailstreet2003.net with Microsoft SMTPSVC(6.0.3790.3959);
    p 2009 02:40:06 -0400
    >Received: from p01c12m032.mxlogic.net ([208.65.145.247]) by outbound.mailstreet2003.net with Microsoft SMTPSVC(6.0.3790.3959);
    > Thu, 17 Sep 2009 02:40:06 -0400
    >Received: from unknown [208.125.104.154]
    > by p01c12m032.mxlogic.net (mxl_mta-6.3.0-4)
    > with SMTP id 5c9d1ba4.0.189767.00-011.245289.p01c12m032.mxlogic.net (envelope-from );
    > Thu, 17 Sep 2009 00:40:06 -0600 (MDT)
    >Received: from server.domain.local ([192.168.1.31]) by server.domain.local
    > ([192.168.1.31]) with mapi; Wed, 16 Sep 2009 07:52:38 -0400
    >From: User 1
    >To: "User 2"
    >Date: Wed, 16 Sep 2009 07:52:37 -0400

    From the headers it looks like you have a single Exchange server.
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP

    --- Rich Matheisen MCSE+I, Exchange MVP
    Saturday, September 19, 2009 3:11 AM
  • Does all your outgoing mails relay through mxlogic.net, if so check with Logic.net

    There could be some DNS issues or SMTP port issue of the destination, use the below tool for diagnosing the issue

    Syntax:

    smtpdiag.exe  h@yourdomain.com  y@problamatic-domain.com  /v

    Download the tool from the below site
    http://www.microsoft.com/downloads/details.aspx?familyid=bc1881c7-925d-4a29-bd42-71e8563c80a9&displaylang=en
    Saturday, September 19, 2009 9:35 AM
  • Hi,

    Please try to telnet the problematic domain by using IP address directly to send the testing email.

    What's the result? Is the same issue occurring as previous operation?

    Thanks

    Allen
    Monday, September 21, 2009 8:59 AM
  • Rich Matheisen, your troubleshooting steps look involved - I am a beginner at Exchange. But if the other users' tips don't work out I will have to try it.

    -Hari-, here is the log from smtpdiag.exe:

    -------------------------------------------------------------------------------------------------

    Searching for Exchange external DNS settings.
    Computer name is ADMIN1DT.

    Checking SOA for domain2.org.
    Checking external DNS servers.
    Checking internal DNS servers.

    Checking TCP/UDP SOA serial number using DNS server [192.168.1.21].
    TCP test succeeded.
    UDP test succeeded.
    Serial number: 2003030740

    Checking TCP/UDP SOA serial number using DNS server [192.168.1.22].
    TCP test succeeded.
    UDP test succeeded.
    Serial number: 2003030740
    SOA serial number match: Passed.

    Checking local domain records.
    Starting TCP and UDP DNS queries for the local domain. This test will try to
    validate that DNS is set up correctly for inbound mail. This test can fail for
    3 reasons.
        1) Local domain is not set up in DNS. Inbound mail cannot be routed to
    local mailboxes.
        2) Firewall blocks TCP/UDP DNS queries. This will not affect inbound mail,
    but will affect outbound mail.
        3) Internal DNS is unaware of external DNS settings. This is a valid
    configuration for certain topologies.
    Checking MX records using TCP: domain1.com.
      MX:    mail.domain1.com (10)
      A:     mail.domain1.com [208.125.xxx.xxx]
    Checking MX records using UDP: domain1.com.
      MX:    mail.domain1.com (10)
      A:     mail.domain1.com [208.125.xxx.xxx]
    Both TCP and UDP queries succeeded. Local DNS test passed.

    Checking remote domain records.
    Starting TCP and UDP DNS queries for the remote domain. This test will try to
    validate that DNS is set up correctly for outbound mail. This test can fail for
    3 reasons.
        1) Firewall blocks TCP/UDP queries which will block outbound mail. Windows
    2000/NT Server requires TCP DNS queries. Windows Server 2003 will use UDP
    queries first, then fall back to TCP queries.
        2) Internal DNS does not know how to query external domains. You must
    either use an external DNS server or configure DNS server to query external
    domains.
        3) Remote domain does not exist. Failure is expected.
    Checking MX records using TCP: nittec.org.
      MX:    domain2.org.inbound10.mxlogic.net (10)
      MX:    domain2.org.inbound10.mxlogicmx.net (10)
      A:     domain2.org.inbound10.mxlogic.net [208.65.144.3]
      A:     domain2.org.inbound10.mxlogic.net [208.65.144.2]
      A:     domain2.org.inbound10.mxlogic.net [208.65.145.3]
    Checking MX records using UDP: nittec.org.
      MX:    domain2.org.inbound10.mxlogicmx.net (10)
      MX:    domain2.org.inbound10.mxlogic.net (10)
      A:     domain2.org.inbound10.mxlogicmx.net [208.65.144.3]
      A:     domain2.org.inbound10.mxlogicmx.net [208.65.144.2]
      A:     domain2.org.inbound10.mxlogicmx.net [208.65.145.2]
    Both TCP and UDP queries succeeded. Remote DNS test passed.

    Checking MX servers listed for y@domain2.org.
    Connecting to domain2.org.inbound10.mxlogicmx.net [208.65.145.2] on port 25.
    Connecting to the server failed. Error: 10061
    Failed to submit mail to domain2.org.inbound10.mxlogicmx.net.
    Connecting to domain2.org.inbound10.mxlogicmx.net [208.65.144.2] on port 25.
    Connecting to the server failed. Error: 10061
    Failed to submit mail to domain2.org.inbound10.mxlogicmx.net.
    Connecting to domain2.org.inbound10.mxlogic.net [208.65.145.3] on port 25.
    Connecting to the server failed. Error: 10061
    Failed to submit mail to domain2.org.inbound10.mxlogic.net.
    Connecting to domain2.org.inbound10.mxlogic.net [208.65.144.2] on port 25.
    Connecting to the server failed. Error: 10061
    Failed to submit mail to domain2.org.inbound10.mxlogic.net.
    Connecting to domain2.org.inbound10.mxlogicmx.net [208.65.144.3] on port 25.
    Connecting to the server failed. Error: 10061
    Failed to submit mail to domain2.org.inbound10.mxlogicmx.net.
    Connecting to domain2.org.inbound10.mxlogic.net [208.65.144.3] on port 25.
    Connecting to the server failed. Error: 10061
    Failed to submit mail to domain2.org.inbound10.mxlogic.net.

    -------------------------------------------------------------------------------------------------

    All of our outgoing mail does not relay through mxlogic, it appears that domain2.org's mail relays through mxlogic.net though.

    Allen Song, after inputting in the command:
    telnet 208.65.144.3 it says connection failed.

    Tuesday, September 22, 2009 2:58 PM
  • Hi,

    Is the issue only occured on one domain or some domains?

    From the tesing result by using smtpdiag.exe, it seems that the problematic domain could not be connected via 25 port. This indicates the destination server has the issue rather than your Exchange server's problem. I suggest we contact the problematic domain to confirm and obtain more information on this issue.

    Thanks

    Allen



    • Marked as answer by Allen Song Friday, September 25, 2009 9:55 AM
    Wednesday, September 23, 2009 3:28 AM
  • Hi

    As Allen suggested check with MXLOGIC.Net, as per the test you have a single Send connector to external  with relaying enabled to Mxlogic.net.

    As Allen suggested is this the same with other domains, if not send the smtpdiag.exe report of any external domain such as Gmail or any..

    Thanks
    Hari

    • Marked as answer by Allen Song Friday, September 25, 2009 9:55 AM
    Wednesday, September 23, 2009 6:40 AM
  • Here is the result of smtpdiag.exe when attempting to connect to google.com...it looks like we are getting a reply from this server.

    ---------------------------------------------------------------------------------------------------

    Searching for Exchange external DNS settings.
    Computer name is ADMIN1DT.

    Checking SOA for google.com.
    Checking external DNS servers.
    Checking internal DNS servers.

    Checking TCP/UDP SOA serial number using DNS server [192.168.1.21].
    TCP test succeeded.
    UDP test succeeded.
    Serial number: 1393016

    Checking TCP/UDP SOA serial number using DNS server [192.168.1.22].
    TCP test succeeded.
    UDP test succeeded.
    Serial number: 1393016
    SOA serial number match: Passed.

    Checking local domain records.
    Starting TCP and UDP DNS queries for the local domain. This test will try to
    validate that DNS is set up correctly for inbound mail. This test can fail for
    3 reasons.
        1) Local domain is not set up in DNS. Inbound mail cannot be routed to
    local mailboxes.
        2) Firewall blocks TCP/UDP DNS queries. This will not affect inbound mail,
    but will affect outbound mail.
        3) Internal DNS is unaware of external DNS settings. This is a valid
    configuration for certain topologies.
    Checking MX records using TCP: domain1.com.
      MX:    mail.domain1.com (10)
      A:     mail.domain1.com [208.125.xxx.xxx]
    Checking MX records using UDP: domain1.com.
      MX:    mail.domain1.com (10)
      A:     mail.domain1.com [208.125.xxx.xxx]
    Both TCP and UDP queries succeeded. Local DNS test passed.

    Checking remote domain records.
    Starting TCP and UDP DNS queries for the remote domain. This test will try to
    validate that DNS is set up correctly for outbound mail. This test can fail for
    3 reasons.
        1) Firewall blocks TCP/UDP queries which will block outbound mail. Windows
    2000/NT Server requires TCP DNS queries. Windows Server 2003 will use UDP
    queries first, then fall back to TCP queries.
        2) Internal DNS does not know how to query external domains. You must
    either use an external DNS server or configure DNS server to query external
    domains.
        3) Remote domain does not exist. Failure is expected.
    Checking MX records using TCP: google.com.
      MX:    google.com.s9b2.psmtp.com (100)
      MX:    google.com.s9a1.psmtp.com (10)
      MX:    smtp2.google.com (10)
      MX:    smtp1.google.com (10)
      MX:    google.com.s9a2.psmtp.com (10)
      MX:    google.com.s9b1.psmtp.com (100)
      A:     smtp2.google.com [74.125.65.25]
      A:     smtp1.google.com [74.125.45.25]
    Checking MX records using UDP: google.com.
      MX:    google.com.s9b2.psmtp.com (100)
      MX:    google.com.s9a1.psmtp.com (10)
      MX:    smtp2.google.com (10)
      MX:    smtp1.google.com (10)
      MX:    google.com.s9a2.psmtp.com (10)
      MX:    google.com.s9b1.psmtp.com (100)
    Both TCP and UDP queries succeeded. Remote DNS test passed.
      A:     google.com.s9b2.psmtp.com [74.125.148.14]
      A:     google.com.s9a1.psmtp.com [74.125.148.10]
      A:     google.com.s9a2.psmtp.com [74.125.148.11]
      A:     google.com.s9b1.psmtp.com [74.125.148.13]

    Checking MX servers listed for y@google.com.
    Connecting to google.com.s9a2.psmtp.com [74.125.148.11] on port 25.
    Received:
    220 Postini ESMTP 242 y6_21_1c4 ready.  CA Business and Professions Code Section
     17538.45 forbids use of this system for unsolicited electronic mail advertiseme
    nts.


    Sent:
    ehlo domain1.com

    Received:
    250-Postini says hello back
    250-STARTTLS
    250-8BITMIME
    250 HELP

    Sent:
    mail from: <h@domain1.com>

    Received:
    250 Ok

    Sent:
    rcpt to: <y@google.com>

    Received:
    550 5.2.1 <y@google.com>... Mailbox disabled for this recipient

    Error: Expected "250". Server rejected the recipient address.
    Failed to submit mail to google.com.s9a2.psmtp.com.
    Connecting to smtp1.google.com [74.125.45.25] on port 25.
    Received:
    220 smtp.google.com ESMTP

    Sent:
    ehlo domain1.com

    Received:
    250-smtp.google.com Hello rrcs-208-125-xxx-xxx.nys.biz.rr.com [208.125.xxx.xxx],
     pleased to meet you
    250-ENHANCEDSTATUSCODES
    250-PIPELINING
    250-8BITMIME
    250-SIZE 20000000
    250-STARTTLS
    250-DELIVERBY
    250 HELP


    Sent:
    mail from: <h@domain1.com>

    Received:
    250 2.1.0 <h@domain1.com>... Sender ok

    Sent:
    rcpt to: <y@google.com>

    Received:
    550 5.2.1 <y@google.com>... Mailbox disabled for this recipient

    Error: Expected "250". Server rejected the recipient address.
    Failed to submit mail to smtp1.google.com.
    Connecting to smtp2.google.com [74.125.65.25] on port 25.
    Received:
    220 smtp.google.com ESMTP

    Sent:
    ehlo domain1.com

    Received:
    250-smtp.google.com Hello rrcs-208-125-xxx-xxx.nys.biz.rr.com [208.125.xxx.xxx],
     pleased to meet you
    250-ENHANCEDSTATUSCODES
    250-PIPELINING
    250-8BITMIME
    250-SIZE 20000000
    250-STARTTLS
    250-DELIVERBY
    250 HELP


    Sent:
    mail from: <h@domain1.com>

    Received:
    250 2.1.0 <h@domain1.com>... Sender ok

    Sent:
    rcpt to: <y@google.com>

    Received:
    550 5.2.1 <y@google.com>... Mailbox disabled for this recipient

    Error: Expected "250". Server rejected the recipient address.
    Failed to submit mail to smtp2.google.com.
    Connecting to google.com.s9a1.psmtp.com [74.125.148.10] on port 25.
    Received:
    220 Postini ESMTP 226 y6_21_1c4 ready.  CA Business and Professions Code Section
     17538.45 forbids use of this system for unsolicited electronic mail advertiseme
    nts.


    Sent:
    ehlo domain1.com

    Received:
    250-Postini says hello back
    250-STARTTLS
    250-8BITMIME
    250 HELP

    Sent:
    mail from: <h@domain1.com>

    Received:
    250 Ok

    Sent:
    rcpt to: <y@google.com>

    Received:
    550 5.2.1 <y@google.com>... Mailbox disabled for this recipient

    Error: Expected "250". Server rejected the recipient address.
    Failed to submit mail to google.com.s9a1.psmtp.com.
    Connecting to google.com.s9b1.psmtp.com [74.125.148.13] on port 25.
    Received:
    220 Postini ESMTP 244 y6_21_1c4 ready.  CA Business and Professions Code Section
     17538.45 forbids use of this system for unsolicited electronic mail advertiseme
    nts.


    Sent:
    ehlo domain1.com

    Received:
    250-Postini says hello back
    250-STARTTLS
    250-8BITMIME
    250 HELP

    Sent:
    mail from: <h@domain1.com>

    Received:
    250 Ok

    Sent:
    rcpt to: <y@google.com>

    Received:
    550 5.2.1 <y@google.com>... Mailbox disabled for this recipient

    Error: Expected "250". Server rejected the recipient address.
    Failed to submit mail to google.com.s9b1.psmtp.com.
    Connecting to google.com.s9b2.psmtp.com [74.125.148.14] on port 25.
    Received:
    220 Postini ESMTP 171 y6_21_1c4 ready.  CA Business and Professions Code Section
     17538.45 forbids use of this system for unsolicited electronic mail advertiseme
    nts.


    Sent:
    ehlo domain1.com

    Received:
    250-Postini says hello back
    250-STARTTLS
    250-8BITMIME
    250 HELP

    Sent:
    mail from: <h@domain1.com>

    Received:
    250 Ok

    Sent:
    rcpt to: <y@google.com>

    Received:
    550 5.2.1 <y@google.com>... Mailbox disabled for this recipient

    Error: Expected "250". Server rejected the recipient address.
    Failed to submit mail to google.com.s9b2.psmtp.com.

    ---------------------------------------------------------------------------------------------------

    So basically it looks like it's only communciation between domain1.com and domain2.org that is being delayed...and the problem is not our's (domain1), it's their's (domain2)...

    Wednesday, September 23, 2009 2:13 PM
  • Hi,

    That's the expect result as we concluded. You need to contact the domain2 to work out this issue.

    Thanks

    Allen
    Friday, September 25, 2009 7:02 AM
  • Thanks for the assistance. What should I tell domain2 about this issue?
    Monday, September 28, 2009 12:55 PM
  • Just curious, what can I tell domain2 so that they are aware of the situation? Thanks!
    Tuesday, September 29, 2009 8:05 PM
  • Hi,

    You should tell them that you could not connect domain2 in 25 port by using telnet. And to get the more information from the domain2.

    Thanks

    Allen
    Wednesday, September 30, 2009 2:15 AM