Messaging Gateway

 View Only

  • 1.  No route to host in the delivery mta queue.

    Posted May 19, 2010 01:02 AM
    Dear all,

    I have gotten a message in the delivery mta queue.

    The message is like below:
    (connect to <Domain Name>[59.12.203.1]: No route to host)

    This message continue to try in the queue and in the result of it the queued messages may increase.

    So, I have attempted to traceroute in the SBG scanner.
    The result is like below: 


    traceroute to 211.115.219.151 (211.115.219.151), 30 hops max, 38 byte packets
     1  156.147.1.2 (156.147.1.2)  0.922 ms  0.998 ms  0.552 ms
     2  10.0.29.34 (10.0.29.34)  1.034 ms  0.611 ms  1.483 ms
     3  10.0.29.3 (10.0.29.3)  2.464 ms  0.625 ms  0.625 ms
     4  10.0.30.2 (10.0.30.2)  0.612 ms  0.789 ms  0.677 ms
     5  203.247.149.249 (203.247.149.249)  1.981 ms  1.817 ms  1.995 ms
     6  203.247.145.2 (203.247.145.2)  2.598 ms  3.583 ms  3.327 ms
     7  112.223.13.217 (112.223.13.217)  3.388 ms  3.350 ms  4.395 ms
     8  210.120.94.13 (210.120.94.13)  4.702 ms 210.180.225.141 (210.180.225.141)  3.776 ms 210.120.94.13 (210.120.94.13)  3.305 ms
     9  61.40.251.149 (61.40.251.149)  4.520 ms 210.120.105.21 (210.120.105.21)  4.131 ms 203.233.17.117 (203.233.17.117)  5.442 ms
    10  210.107.126.66 (210.107.126.66)  5.361 ms  5.568 ms 61.42.201.82 (61.42.201.82)  5.715 ms
    11  211.115.199.213 (211.115.199.213)  5.964 ms  11.142 ms  4.966 ms
    12  211.115.197.183 (211.115.197.183)  4.966 ms  4.936 ms  12.035 ms
    13  211.239.113.12 (211.239.113.12)  7.896 ms  7.339 ms  6.470 ms
    14  211.239.113.9 (211.239.113.9)  8.601 ms  14.440 ms  6.452 ms
    15  211.239.113.12 (211.239.113.12)  17.676 ms  6.796 ms  12.392 ms
    16  211.239.113.9 (211.239.113.9)  5.608 ms  4.934 ms  13.495 ms
    17  211.239.113.12 (211.239.113.12)  9.278 ms  15.309 ms  6.042 ms
    18  211.239.113.9 (211.239.113.9)  5.495 ms  12.060 ms  5.006 ms
    19  211.239.113.12 (211.239.113.12)  5.955 ms  13.808 ms  6.091 ms
    20  211.239.113.9 (211.239.113.9)  4.707 ms  14.965 ms  6.678 ms
    21  211.239.113.12 (211.239.113.12)  19.360 ms  8.585 ms  16.946 ms
    22  211.239.113.9 (211.239.113.9)  7.106 ms  14.802 ms  7.778 ms
    23  211.239.113.12 (211.239.113.12)  18.839 ms  7.869 ms  15.477 ms
    24  211.239.113.9 (211.239.113.9)  6.903 ms  14.891 ms  6.524 ms
    25  211.239.113.12 (211.239.113.12)  32.351 ms  11.483 ms  8.613 ms
    26  211.239.113.9 (211.239.113.9)  15.308 ms  6.755 ms  16.410 ms
    27  211.239.113.12 (211.239.113.12)  17.378 ms  15.977 ms  16.878 ms
    28  211.239.113.9 (211.239.113.9)  6.153 ms  17.202 ms  6.053 ms
    29  211.239.113.12 (211.239.113.12)  19.787 ms  8.489 ms  16.199 ms
    30  211.239.113.9 (211.239.113.9)  6.680 ms  16.363 ms  6.947 ms

    I guess a firewall exists between our scanner and the external MX.
    Is it right?

    Is there any one to help me or advice to me?

    Thank you.

    Best regards,
    Fossil


  • 2.  RE: No route to host in the delivery mta queue.

    Posted May 19, 2010 10:19 AM
    There is a network routing loop starting at

    13  211.239.113.12 (211.239.113.12)  7.896 ms  7.339 ms  6.470 ms
    14  211.239.113.9 (211.239.113.9)  8.601 ms  14.440 ms  6.452 ms

    This is not a Brightmail issue.

    Your target 59.12.203.1  is in Korea ISP is KOREA TELECOM KORNET.NET
    The loop  211.239.113.12 and .9 are at ISP KRNIC SKLINE.CO.KR

    You, or the recipient domain needs to talk to SkLine

    This information is from     http://www.ip2location.com/demo.aspx

    Why the traceroute to 211.115.219.151 instead of 59.12.203.1?

    Lets look at the issue from outside your network, using internet based tools:

    Traceroute from internet
    http://network-tools.com/default.asp?prog=trace&host=59.12.203.1  ends at a firewall

    ...
    15   195 ms   198 ms   196 ms  220.120.253.34
    16   193 ms   193 ms   193 ms  220.120.253.6
    17   195 ms   201 ms   195 ms  221.163.25.142
    18   193 ms   196 ms   194 ms  221.163.87.10
    19  221.163.87.10  reports: Destination host unreachable.

    Internet tracert shows the loop as well.  It's not just you.
    http://network-tools.com/default.asp?prog=trace&host=211.115.219.151
    ...
    11   228 ms   237 ms   236 ms  211.115.201.84
    12   237 ms   245 ms   247 ms  211.115.197.55
    13   219 ms   220 ms   220 ms  211.239.113.12
    14   232 ms   225 ms   237 ms  211.239.113.9
    15   255 ms   259 ms   272 ms  211.239.113.12
    16   272 ms   266 ms   243 ms  211.239.113.9