none
Failed to receive Data. Error: 10054 Error Expected "220". Failed to get a response form the server

    Question

  • By using smtpdiag tool, I get the following message

    Searching for Exchange external DNS settings.

    Computer name is 0000.

     

    Checking SOA for lists.agpn.com.

    Checking external DNS servers.

    Checking internal DNS servers.

    SOA serial number match: Passed.

     

    Checking local domain records.

    Checking MX records using TCP: nps.org.au.

    Checking MX records using UDP: nps.org.au.

    Both TCP and UDP queries succeeded. Local DNS test passed.

     

    Checking remote domain records.

    Checking MX records using TCP: lists.agpn.com.

    Checking MX records using UDP: lists.agpn.com.

    Both TCP and UDP queries succeeded. Remote DNS test passed.

     

    Checking MX servers listed for xxx@lists.agpn.com.

    Connecting to lists.agpn.com [216.8.179.23] on port 25.

    Failed to receive data. Error: 10054

    Error: Expected "220". Failed to get a response from the server.

    Failed to submit mail to lists.agpn.com.

     Interestingly, I have similar result for other addresses, even though I can send/receive from some addresses but Cannot for some.

    Is not it, if I have any internal problem, I will not be able to send/receive email from/to any addresses?

    -------------------------------------------------------------------------------Also--------------------------- 

    The email address which didn't work has the following undeliverable message

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

    Delivery has failed to these recipients or distribution lists:

     

    'xxx@lists.agpn.com.au'
    An error occurred while trying to deliver this message to the recipient's e-mail address. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator.

     

    The following organization rejected your message: [203.37.88.45].

     

      _____  


    Sent by Microsoft Exchange Server 2007







     

    Diagnostic information for administrators:

     

    Generating server: server-mail.nps.qum

     

    xxx@lists.agpn.com.au
    [203.37.88.45] #557 Access denied <xxx@lists.agpn.com.au> for user <xxx@nps.org.au> ##

     

    Original message headers:

     

    Received: from server-mail.nps.qum ([10.1.50.23]) by server-mail.nps.qum
     ([10.1.50.23]) with mapi; Wed, 14 Apr 2010 13:11:53 +1000
    From: xxxxxxx<xxxx@nps.org.au>
    To: "'xxx@lists.agpn.com.au'" <xxx@lists.agpn.com.au>
    Date: Wed, 14 Apr 2010 13:11:53 +1000
    Subject: Please ignore. this is a test from NPS
    Thread-Topic: Please ignore. this is a test from NPS
    Thread-Index: AcrbgEbUuhcHN1XfT/yr4xflUVCTYQ==
    Message-ID: <488882C5775B70449E2F12D1D2751C3B84AAF514B2@server-mail.nps.qum>
    Accept-Language: en-US
    Content-Language: en-US
    X-MS-Has-Attach:
    X-MS-TNEF-Correlator:
    acceptlanguage: en-US
    Content-Type: multipart/alternative;
                boundary="_000_488882C5775B70449E2F12D1D2751C3B84AAF514B2servermailnps_"
    MIME-Version: 1.0

    Wednesday, April 14, 2010 2:03 AM

Answers

  • On Mon, 19 Apr 2010 02:42:39 +0000, mkhan100 wrote:

    >I checked that address and found they are black listed.

    That's not a good thing.

    >Does it mean that email communication is still possible but no gurentee.

    That's correct. It depends on which DNSBL lists your IP address and
    whether or not the organization you're sending to uses that DNSBL.
    There's never any guaranty the you'll be able to send e-mail
    everywhere all the time. Nor is there any way to know if there are
    DNSBLs you don't know about, including the ones that are privately
    maintained, or those that react to too much junk mail, too many unknow
    recipients, etc. by dynamically blocking an IP address for sme
    predetermined amount of time.

    >And that is why I can still send/receive email from someone@macquarie.com

    See above. Maybe they don't use any DNSBL that lists your IP address.

    > blacklist:216.82.254.3 blacklist

    This is an IP address that belongs to MessageLabs. Check YOUR IP
    address, not someone else's!

    > We notice you are on a blacklist. Click here for some suggestions
    >Checking 216.82.254.3 against 105 known blacklists... Listed 1 times with 1 timeouts. Reported by mxtoolbox.com on Sunday, April 18, 2010 at 9:38:31 PM (GMT-5) (History)

    >When I use just macquarie.com it shows that it is NOT a backlisted address.

    That name resolves to a different IP address: 203.210.65.6. Is that
    YOUR IP address?

    Why do you care if the recipient's SMTP server is in a DNSBL? You only
    need to concern yourself with your IP address(es).
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Marked as answer by mkhan100 Monday, April 19, 2010 5:10 AM
    Monday, April 19, 2010 3:34 AM

All replies

  • On Wed, 14 Apr 2010 02:03:33 +0000, mkhan100 wrote:

    >By using smtpdiag tool, I get the following message
    >
    >Searching for Exchange external DNS settings.


    >Checking MX servers listed for xxx@lists.agpn.com.
    >
    >Connecting to lists.agpn.com [216.8.179.23] on port 25.

    >Failed to receive data. Error: 10054
    >
    >Error: Expected "220". Failed to get a response from the server.

    [ snip ]

    If it's any consolation, I don't get any response from that IP
    address, either. But since there's no MX record for that domain I
    don't find that surprising. The "A" record for that name probably
    isn't a SMTP server. What it IS, is a web server.

    [ snip ]

    >'xxx@lists.agpn.com.au'An error occurred while trying to deliver this message to the recipient's e-mail address. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator.

    That's a different domain, but there IS a SMTP server at the IP
    address 203.37.88.45.

    [ snip ]

    >xxx@lists.agpn.com.au[203.37.88.45] #557 Access denied <xxx@lists.agpn.com.au> for user <xxx@nps.org.au> ##

    And the reason is that you've been denied permission (of some sort) by
    that server.
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP

    --- Rich Matheisen MCSE+I, Exchange MVP
    Wednesday, April 14, 2010 9:14 PM
  • Thanks Rich,

    Question 1: I knew that I was denied permission but how do I resolve it? My domain is not a blacklisted one. What to do now?

     

    Question 2: I have similier output from smtpdiag from many addresses, even though email communications between us, and have NO Problem. Why?

    Checking SOA for macquaire.com.
    Checking external DNS servers.
    Checking internal DNS servers.
    SOA serial number match: Passed.

    Checking local domain records.
    Checking MX records using TCP: nps.org.au.
    Checking MX records using UDP: nps.org.au.
    Both TCP and UDP queries succeeded. Local DNS test passed.

    Checking remote domain records.
    Checking MX records using TCP: macquaire.com.
    Checking MX records using UDP: macquaire.com.
    Both TCP and UDP queries succeeded. Remote DNS test passed.

    Checking MX servers listed for xxx@macquaire.com.
    Connecting to macquaire.com [203.27.227.23] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to macquaire.com

    If possible, give me steps to do to resolve these.

    Thanks in advance.

     

    Wednesday, April 14, 2010 9:53 PM
  • On Wed, 14 Apr 2010 21:53:30 +0000, mkhan100 wrote:

    >Question 1: I knew that I was denied permission but how do I resolve it? My domain is not a blacklisted one. What to do now?

    You conact the admin for the system and ask why you're denied
    permission. If you can't send them e-mail from your system then use
    another e-mail system (gmail, hotmail, etc.).

    >Question 2: I have similier output from smtpdiag from many addresses, even though email communications between us, and have NO Problem. Why?
    >
    >Checking SOA for macquaire.com.Checking external DNS servers.Checking internal DNS servers.SOA serial number match: Passed.
    >
    >Checking local domain records.Checking MX records using TCP: nps.org.au.Checking MX records using UDP: nps.org.au.Both TCP and UDP queries succeeded. Local DNS test passed.
    >
    >Checking remote domain records.Checking MX records using TCP: macquaire.com.Checking MX records using UDP: macquaire.com.Both TCP and UDP queries succeeded. Remote DNS test passed.
    >
    >Checking MX servers listed for xxx@macquaire.com.Connecting to macquaire.com [203.27.227.23] on port 25.Failed to receive data. Error: 10054Error: Expected "220". Failed to get a response from the server.Failed to submit mail to macquaire.com

    I didn't find any MX records for macquaire.com (not even if I query
    their DNS directly), and I can't connect on port 25 to 203.27.227.23.
    There's no web site at that address, either. A quick scan of their web
    site didn't turn up any e-mail addresses, either.
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP

    --- Rich Matheisen MCSE+I, Exchange MVP
    Thursday, April 15, 2010 1:58 AM
  • Thanks for the answer for Q1, which I have already resolved.

    But I am really confused on your Q2 answer. If there is NO MX record for macquarie.com nor you can't query DNS directly and your say No Website at that address,

    a. What does these mean?

    b. How I can successfully send/receive email from that address? http://www.macquarie.com/com/index.htm 

    c. Can you please give me some lights. Is there any problem in my site, you think? If yes, what these might be?

    d. how do I resolve that?

    I highly appriciate your help

     

     

     

     

     

    Thursday, April 15, 2010 3:12 AM
  • On Thu, 15 Apr 2010 03:12:26 +0000, mkhan100 wrote:

    >
    >
    >Thanks for the answer for Q1, which I have already resolved.
    >
    >But I am really confused on your Q2 answer. If there is NO MX record for macquarie.com nor you can't query DNS directly

    I didn't say I can't query their DNS. I said I couldn't find a MX
    record even if I used their DNS name server.

    However, today you spelled the domain name as "macquarie.com" --
    yesterday you spelled it "macquaire.com". For the "macquarie.com" name
    there's MX records.

    Non-authoritative answer:
    macquarie.com MX preference = 10, mail exchanger =
    cluster9.us.messagelabs.com
    macquarie.com MX preference = 20, mail exchanger =
    cluster9a.us.messagelabs.com

    cluster9.us.messagelabs.com internet address = 216.82.254.3
    cluster9.us.messagelabs.com internet address = 216.82.254.35
    cluster9.us.messagelabs.com internet address = 216.82.254.51
    cluster9.us.messagelabs.com internet address = 216.82.254.227
    cluster9.us.messagelabs.com internet address = 216.82.254.243
    cluster9.us.messagelabs.com internet address = 216.82.242.19
    cluster9.us.messagelabs.com internet address = 216.82.249.19
    cluster9.us.messagelabs.com internet address = 216.82.249.35
    cluster9.us.messagelabs.com internet address = 216.82.249.51
    cluster9a.us.messagelabs.com internet address = 216.82.254.35
    cluster9a.us.messagelabs.com internet address = 216.82.254.51
    cluster9a.us.messagelabs.com internet address = 216.82.254.227
    cluster9a.us.messagelabs.com internet address = 216.82.254.243
    cluster9a.us.messagelabs.com internet address = 85.158.136.170
    cluster9a.us.messagelabs.com internet address = 85.158.137.231
    cluster9a.us.messagelabs.com internet address = 216.82.248.44
    cluster9a.us.messagelabs.com internet address = 216.82.248.45
    cluster9a.us.messagelabs.com internet address = 216.82.249.19
    cluster9a.us.messagelabs.com internet address = 216.82.249.35
    cluster9a.us.messagelabs.com internet address = 216.82.249.51
    cluster9a.us.messagelabs.com internet address = 216.82.254.3

    >and your say No Website at that address,

    If you use http://203.27.227.23 you'll find a web site, but all it
    says is "Web Hosting has not been setup for this domain name".

    >a. What does these mean?
    >
    >b. How I can successfully send/receive email from that address? http://www.macquarie.com/com/index.htm

    FROM there? I don't know. That's a URL.

    >c. Can you please give me some lights. Is there any problem in my site, you think? If yes, what these might be?

    Verify the spelling of the domain name. Then rerun the smtpdiag tool
    using the correct domain name.

    >d. how do I resolve that?

    Check your spelling.
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Proposed as answer by Gavin-Zhang Friday, April 16, 2010 6:46 AM
    Friday, April 16, 2010 3:10 AM
  • Extremely Sorry for my spelling mistake.

    Now I use correct address in smtpDiag and found the following errors

    ------

     


    Checking external DNS servers.
    Checking internal DNS servers.
    SOA serial number match: Passed.

    Checking local domain records.
    Checking MX records using TCP: nps.org.au.
    Checking MX records using UDP: nps.org.au.
    Both TCP and UDP queries succeeded. Local DNS test passed.

    Checking remote domain records.
    Checking MX records using TCP: macquarie.com.
    Checking MX records using UDP: macquarie.com.
    Both TCP and UDP queries succeeded. Remote DNS test passed.

    Checking MX servers listed for xxx@macquarie.com.
    Connecting to cluster9.us.messagelabs.com [216.82.254.243] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9.us.messagelabs.com.
    Connecting to cluster9.us.messagelabs.com [216.82.254.227] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9.us.messagelabs.com.
    Connecting to cluster9.us.messagelabs.com [216.82.254.51] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9.us.messagelabs.com.
    Connecting to cluster9.us.messagelabs.com [216.82.254.35] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9.us.messagelabs.com.
    Connecting to cluster9.us.messagelabs.com [216.82.254.3] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9.us.messagelabs.com.
    Connecting to cluster9.us.messagelabs.com [216.82.249.51] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9.us.messagelabs.com.
    Connecting to cluster9.us.messagelabs.com [216.82.249.35] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9.us.messagelabs.com.
    Connecting to cluster9.us.messagelabs.com [216.82.249.19] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9.us.messagelabs.com.
    Connecting to cluster9.us.messagelabs.com [216.82.242.19] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9.us.messagelabs.com.
    Connecting to cluster9a.us.messagelabs.com [216.82.249.51] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9a.us.messagelabs.com.
    Connecting to cluster9a.us.messagelabs.com [216.82.249.35] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9a.us.messagelabs.com.
    Connecting to cluster9a.us.messagelabs.com [216.82.249.19] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9a.us.messagelabs.com.
    Connecting to cluster9a.us.messagelabs.com [216.82.248.45] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9a.us.messagelabs.com.
    Connecting to cluster9a.us.messagelabs.com [216.82.248.44] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9a.us.messagelabs.com.
    Connecting to cluster9a.us.messagelabs.com [85.158.137.231] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9a.us.messagelabs.com.
    Connecting to cluster9a.us.messagelabs.com [85.158.136.170] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9a.us.messagelabs.com.
    Connecting to cluster9a.us.messagelabs.com [216.82.254.243] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9a.us.messagelabs.com.
    Connecting to cluster9a.us.messagelabs.com [216.82.254.227] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9a.us.messagelabs.com.
    Connecting to cluster9a.us.messagelabs.com [216.82.254.51] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9a.us.messagelabs.com.
    Connecting to cluster9a.us.messagelabs.com [216.82.254.35] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9a.us.messagelabs.com.
    Connecting to cluster9a.us.messagelabs.com [216.82.254.3] on port 25.
    Failed to receive data. Error: 10054
    Error: Expected "220". Failed to get a response from the server.
    Failed to submit mail to cluster9a.us.messagelabs.com.

     

     

    please explain

    Friday, April 16, 2010 5:11 AM
  • Hi mkhan,

    Sure, agree with Rich, kindly suggest that you confirm the test domain correct input and has MX record.
    You could use here.

    Regards!
    gavin

    Friday, April 16, 2010 7:01 AM
  • On Fri, 16 Apr 2010 05:11:28 +0000, mkhan100 wrote:

    >
    >
    >Extremely Sorry for my spelling mistake.
    >
    >Now I use correct address in smtpDiag and found the following errors

    For you to fail to connect to that many different SMTP servers there
    has to be some kind of network problem. Exchange just uses the
    services provided by the O/S.

    Can you tracert to any of the IP addresses?
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP

    --- Rich Matheisen MCSE+I, Exchange MVP
    Saturday, April 17, 2010 2:19 AM
  • I have lots of Request timed out when I use the address (tracert 216.82.254.3).  

    Tracing route to mail172.messagelabs.com [216.82.254.3]
    over a maximum of 30 hops:

      1    <1 ms    <1 ms    <1 ms  10.1.57.5
      2     1 ms    <1 ms     1 ms  10.1.50.5
      3    14 ms    22 ms    22 ms  172.30.220.77
      4    24 ms    23 ms    27 ms  10.1.52.254
      5    11 ms    23 ms    29 ms  202.86.117.209
      6    20 ms    26 ms    23 ms  100.3.11.61
      7    30 ms    24 ms    20 ms  202.92.64.2
      8    25 ms    25 ms    22 ms  202.92.64.1
      9    17 ms    23 ms    23 ms  ge1-2.sclardist02.aapt.net.au [202.10.13.30]
     10    23 ms    23 ms    24 ms  te3-1.sclarbrdr01.aapt.net.au [202.10.14.5]
     11    23 ms    25 ms    26 ms  xe7-0-0-320.sybr5.global-gateway.net.nz [202.50.
    238.213]
     12     *        *        *     Request timed out.
     13     *        *        *     Request timed out.
     14     *        *        *     Request timed out.
     15   175 ms   161 ms   162 ms  sl-st20-la-8-1-0.sprintlink.net [160.81.22.129]

     16   186 ms   186 ms   185 ms  144.232.9.18
     17   195 ms   200 ms   183 ms  los-core-01.inet.qwest.net [205.171.32.9]
     18     *        *        *     Request timed out.
     19   228 ms   222 ms   216 ms  204.133.176.66
     20   231 ms   226 ms   214 ms  v100.r.t172.messagelabs.net [216.82.252.83]
     21     *        *        *     Request timed out.
     22     *        *        *     Request timed out.
     23     *        *        *     Request timed out.
     24     *        *        *     Request timed out.
     25     *        *        *     Request timed out.
     26     *        *        *     Request timed out.
     27     *        *        *     Request timed out.
     28     *        *        *     Request timed out.
     29     *        *        *     Request timed out.
     30     *        *        *     Request timed out.

    Trace complete.

     

    Monday, April 19, 2010 1:51 AM
  • On Mon, 19 Apr 2010 01:51:57 +0000, mkhan100 wrote:

    >
    >
    >I have lots of Request timed out when I use the address (tracert 216.82.254.3).

    Those are just likely to be devices that don't respond to an ICMP ECHO
    request.

    If the network is reachable but you cannot connect to port 25 it may
    be that your IP (or network) is blocked. Have you verified that this
    is (or is not) the case? Start here:
    http://www.mxtoolbox.com/blacklists.aspx
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP

    --- Rich Matheisen MCSE+I, Exchange MVP
    Monday, April 19, 2010 2:25 AM
  • I checked that address and found they are black listed. Does it mean that email communication is still possible but no gurentee. And that is why I can still send/receive email from someone@macquarie.com

     

     

    blacklist:216.82.254.3      blacklist  

     We notice you are on a blacklist.  Click here for some suggestions


    Checking 216.82.254.3 against 105 known blacklists...
    Listed 1 times with 1 timeouts.

    Reported by mxtoolbox.com on Sunday, April 18, 2010 at 9:38:31 PM (GMT-5)  (History)


    When I use just macquarie.com it shows that it is NOT a backlisted address.
     

    SuperTool <sup>Beta</sup>

    Command:
    <input id="ctl00_ContentPlaceHolder1_txtToolInput" class="tools_lookup_textbox" name="ctl00$ContentPlaceHolder1$txtToolInput" type="text" value="blacklist:macquarie.com" tabindex="1" /> <input id="ctl00_ContentPlaceHolder1_btnAction" class="tools_lookup_button" onclick="javascript:__doPostBack('ctl00$ContentPlaceHolder1$btnAction','')" name="ctl00$ContentPlaceHolder1$btnAction" type="button" value="Lookup" tabindex="1" />
    blacklist:macquarie.com      blacklist  

    macquarie.com was resolved to 203.210.65.6.
    Checking macquarie.com against 105 known blacklists...
    Listed 0 times with 3 timeouts.
    Blacklist Status Reason TTL ResponseTime
    AHBL  OK     31
    Backscatter.org  OK     31
    BARRACUDA  OK     47
    BURNT-TECH  OK     62
    CASA-CBL  OK     203
    CASA-CBL+  OK     47
    CASA-CDL  OK     203
    CBL  OK     31
    CSMA  OK     47
    CYBERLOGIC  OK     47
    CYMRU-BOGONS  OK     47
    DAN-TOR  OK     125
    DAN-TOREXIT  OK     125
    DEADBEEF  OK     47
    DNSBLINFO  OK     47
    DUINV  OK     156
    DULRU  OK     172
    FABELSOURCES  OK     125
    FIVETEN  OK     125
    GIRL  OK     125
    GRIP  OK     125
    HIL  OK     125
    HIL  OK     140
    HILLI  OK     203
    ICMFORBIDDEN  OK     203
    IMP-SPAM  OK     343
    IMP-WORM  OK     328
    INTERSIL  OK     203
    ivmSIP  OK     203
    ivmSIP/24  OK     203
    KEMPTBL  OK     203
    KUNDENSERVER  OK     203
    LASHBACK  OK     203
    LNSGBLOCK  OK     203
    LNSGBULK  OK     203
    LNSGDUL  OK     203
    LNSGMULTI  OK     203
    LNSGOR  OK     203
    LNSGSRC  OK     203
    MSRBL-Combined  OK     203
    MSRBL-Images  OK     203
    MSRBL-Phising  OK     203
    MSRBL-Spam  OK     203
    MSRBL-Viruses  OK     203
    NERD  OK     218
    NETHERRELAYS  OK     203
    NETHERUNSURE  OK     203
    NIXSPAM  OK     203
    NJABL  OK     203
    NJABLDUL  OK     203
    NJABLFORMMAIL  OK     218
    NJABLMULTI  OK     218
    NJABLPROXIES  OK     218
    NJABLSOURCES  OK     218
    NLKUNBLACKLIST  OK     218
    NLKUNWHITELIST  OK     218
    NOFALSEPOSITIVE  OK     218
    NOMOREFUNN  OK     218
    ORID  OK     343
    ORVEDB  OK     234
    OSPAM  OK     218
    PDL  OK     218
    PSBL  OK     218
    RANGERSBL  OK     234
    RATS-Dyna  OK     218
    RATS-NoPtr  OK     234
    RATS-Spam  OK     234
    RBL-JP  OK     234
    REDHAWK  OK     234
    RRBL  OK     234
    RSBL  OK     234
    SCHULTE  OK     234
    SDERB  OK     234
    SENDERBASE  OK     234
    SERVICESNET  OK     234
    SOLID  OK     234
    SORBS-BLOCK  OK     234
    SORBS-DUHL  OK     234
    SORBS-HTTP  OK     234
    SORBS-MISC  OK     234
    SORBS-SMTP  OK     234
    SORBS-SOCKS  OK     234
    SORBS-SPAM  OK     234
    SORBS-WEB  OK     234
    SORBS-ZOMBIE  OK     234
    SPAMCANNIBAL  OK     234
    SPAMCOP  OK     234
    Spamhaus-ZEN  OK     234
    SPAMSOURCES  OK     234
    SPEWS1  OK     234
    SPEWS2  OK     234
    SWINOG  OK     234
    TECHNOVISION  OK     234
    Tiopan  OK     234
    TRIUMF  OK     234
    UCEPROTECTL1  OK     234
    UCEPROTECTL2  OK     234
    UCEPROTECTL3  OK     234
    VIRBL  OK     234
    WPBL  OK     234
    WSFF  OK     234
    ZONEEDIT  OK     234
    ANT  TIMEOUT     0
    EMAILBASURA  TIMEOUT     0
    SPAMRBL  TIMEOUT     0
    dns lookup ns lookup mx lookup whois lookup

    Reported by mxtoolbox.com on Sunday, April 18, 2010 at 9:49:14 PM (GMT-5)  (History)


    Blacklist Status Reason TTL ResponseTime
    Backscatter.org  LISTED Sorry 216.82.254.3 is blacklisted at Detail
    Return codes were: 127.0.0.2
    1965 109
    AHBL  OK     0
    ANT  OK     0
    BARRACUDA  OK     0
    BURNT-TECH  OK     0
    CASA-CBL  OK     0
    CASA-CBL+  OK     0
    CASA-CDL  OK     0
    CBL  OK     0
    CSMA  OK     0
    CYBERLOGIC  OK     47
    CYMRU-BOGONS  OK     0
    DAN-TOR  OK     0
    DAN-TOREXIT  OK     0
    DEADBEEF  OK     16
    DNSBLINFO  OK     16
    DUINV  OK     16
    DULRU  OK     16
    EMAILBASURA  OK     16
    FABELSOURCES  OK     16
    FIVETEN  OK     62
    GIRL  OK     16
    GRIP  OK     16
    HIL  OK     16
    HIL  OK     31
    HILLI  OK     16
    ICMFORBIDDEN  OK     16
    IMP-SPAM  OK     16
    IMP-WORM  OK     31
    INTERSIL  OK     31
    ivmSIP  OK     31
    ivmSIP/24  OK     31
    KEMPTBL  OK     62
    KUNDENSERVER  OK     140
    LASHBACK  OK     47
    LNSGBLOCK  OK     47
    LNSGBULK  OK     47
    LNSGDUL  OK     47
    LNSGMULTI  OK     47
    LNSGOR  OK     47
    LNSGSRC  OK     47
    MSRBL-Combined  OK     47
    MSRBL-Images  OK     47
    MSRBL-Phising  OK     47
    MSRBL-Spam  OK     47
    MSRBL-Viruses  OK     47
    NERD  OK     47
    NETHERRELAYS  OK     47
    NETHERUNSURE  OK     62
    NIXSPAM  OK     140
    NJABL  OK     62
    NJABLDUL  OK     62
    NJABLFORMMAIL  OK     62
    NJABLMULTI  OK     62
    NJABLPROXIES  OK     62
    NJABLSOURCES  OK     62
    NLKUNBLACKLIST  OK     62
    NLKUNWHITELIST  OK     62
    NOFALSEPOSITIVE  OK     62
    NOMOREFUNN  OK     62
    ORID  OK     62
    ORVEDB  OK     62
    OSPAM  OK     62
    PDL  OK     62
    PSBL  OK     62
    RANGERSBL  OK     62
    RATS-Dyna  OK     62
    RATS-NoPtr  OK     62
    RATS-Spam  OK     94
    RBL-JP  OK     62
    REDHAWK  OK     62
    RRBL  OK     62
    RSBL  OK     62
    SCHULTE  OK     62
    SDERB  OK     62
    SENDERBASE  OK     78
    SERVICESNET  OK     78
    SOLID  OK     78
    SORBS-BLOCK  OK     78
    SORBS-DUHL  OK     78
    SORBS-HTTP  OK     78
    SORBS-MISC  OK     78
    SORBS-SMTP  OK     78
    SORBS-SOCKS  OK     78
    SORBS-SPAM  OK     78
    SORBS-WEB  OK     78
    SORBS-ZOMBIE  OK     78
    SPAMCANNIBAL  OK     78
    SPAMCOP  OK     78
    Spamhaus-ZEN  OK     125
    SPAMSOURCES  OK     109
    SPEWS1  OK     109
    SPEWS2  OK     109
    SWINOG  OK     109
    TECHNOVISION  OK     109
    Tiopan  OK     109
    TRIUMF  OK     109
    UCEPROTECTL1  OK     109
    UCEPROTECTL2  OK     109
    UCEPROTECTL3  OK     109
    VIRBL  OK     109
    WPBL  OK     109
    WSFF  OK     109
    ZONEEDIT  OK     109
    SPAMRBL  TIMEOUT     0
    Monday, April 19, 2010 2:42 AM
  • On Mon, 19 Apr 2010 02:42:39 +0000, mkhan100 wrote:

    >I checked that address and found they are black listed.

    That's not a good thing.

    >Does it mean that email communication is still possible but no gurentee.

    That's correct. It depends on which DNSBL lists your IP address and
    whether or not the organization you're sending to uses that DNSBL.
    There's never any guaranty the you'll be able to send e-mail
    everywhere all the time. Nor is there any way to know if there are
    DNSBLs you don't know about, including the ones that are privately
    maintained, or those that react to too much junk mail, too many unknow
    recipients, etc. by dynamically blocking an IP address for sme
    predetermined amount of time.

    >And that is why I can still send/receive email from someone@macquarie.com

    See above. Maybe they don't use any DNSBL that lists your IP address.

    > blacklist:216.82.254.3 blacklist

    This is an IP address that belongs to MessageLabs. Check YOUR IP
    address, not someone else's!

    > We notice you are on a blacklist. Click here for some suggestions
    >Checking 216.82.254.3 against 105 known blacklists... Listed 1 times with 1 timeouts. Reported by mxtoolbox.com on Sunday, April 18, 2010 at 9:38:31 PM (GMT-5) (History)

    >When I use just macquarie.com it shows that it is NOT a backlisted address.

    That name resolves to a different IP address: 203.210.65.6. Is that
    YOUR IP address?

    Why do you care if the recipient's SMTP server is in a DNSBL? You only
    need to concern yourself with your IP address(es).
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Marked as answer by mkhan100 Monday, April 19, 2010 5:10 AM
    Monday, April 19, 2010 3:34 AM
  • I am expressing my gratitude to Rich Matheisen for his patient and expert answers

    Your contributions make TechNet Forums valuable

    Thank you very much.

     

    Monday, April 19, 2010 5:16 AM