Why did this mail fail?

Discussion in 'Computer Support' started by John Jones, Feb 27, 2007.

  1. John Jones

    John Jones Guest

    From the following, anyone suggest why all e's I send from my googlemail to
    a mate at verison.net bounces whereas others from my Orange account do get
    through?
    This is what is generated:-

    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 recipient has been delayed:



    Message will be retried for 1 more day(s)

    Technical details of temporary failure:
    TEMP_FAILURE: DNS Error: Could not contact DNS servers

    ----- Message header follows -----

    Received: by 10.65.251.17 with SMTP id d17mr6272191qbs.1172408047089;
    Sun, 25 Feb 2007 04:54:07 -0800 (PST)
    Received: by 10.64.251.10 with HTTP; Sun, 25 Feb 2007 04:54:06 -0800 (PST)
    Message-ID: <>
    Date: Sun, 25 Feb 2007 12:54:06 +0000
    From: "John Smith" <>
    To:
    Subject: Fwd: Fw: 3 pictures for you
    In-Reply-To: <[email protected]>
    MIME-Version: 1.0
    Content-Type: multipart/mixed;
    boundary="----=_Part_15278_4731093.1172408046926"
    References: <[email protected]>

    ----- Message body suppressed -----
     
    John Jones, Feb 27, 2007
    #1
    1. Advertisements

  2. John Jones

    Mike Easter Guest

    My guess is that you have spelled 'verizon' incorrectly as 'verison' --
    and altho' verizon tries to help out people who spell its name
    incorrectly by registering the name verison.net and 'trying' to provide
    nameservice for it, the verison nameservice is no good.

    Time to look up verison.net A record

    Searching for verison.net A record at e.root-servers.net Got referral
    to A.GTLD-SERVERS.net. [took 85 ms]
    Searching for verison.net A record at A.GTLD-SERVERS.net. Got
    referral to dns2.verizon.com. [took 44 ms]
    Searching for verison.net A record at dns2.verizon.com. Reports a
    server failure! [took 1027 ms].

    Response:
    Unknown (server failure at dns2.verizon.com).

    whois -h whois.markmonitor.com verison.net ...
    Registrant:
    Verizon Trademark Services
    Time to look up verison.net MX record

    Searching for verison.net MX record at i.root-servers.net Got
    referral to E.GTLD-SERVERS.net. [took 104 ms]
    Searching for verison.net MX record at E.GTLD-SERVERS.net. Got
    referral to vzdns01.verizon.com. [took 84 ms]
    Searching for verison.net MX record at vzdns01.verizon.com. Got
    referral to H.ROOT-SERVERS.net. [took 638 ms]
    Searching for verison.net MX record at H.ROOT-SERVERS.net. Got
    referral to j.gtld-servers.net. [took 16 ms]
    Searching for verison.net MX record at j.gtld-servers.net. Got
    referral to dns2.verizon.com. [took 208 ms]
    Searching for verison.net MX record at dns2.verizon.com. Reports a
    server failure! [took 116 ms].

    Response:
    Unknown (server failure at dns2.verizon.com).
     
    Mike Easter, Feb 27, 2007
    #2
    1. Advertisements

  3. John Jones

    John Jones Guest

    Bugger me Mike, that's the answer - spelled wrong - Excellent - TVM .
    Stupid me...John
    ---------------------


     
    John Jones, Feb 27, 2007
    #3
  4. John Jones

    Mike Easter Guest

    It is actually *bad* that verizon /attempts/ to provide service to the
    verison name but /then/ fails because of poor nameservice, because it
    slows down the process of the mail being 'properly' rejected. A proper
    *permanent* [as opposed to temporary] rejection would be both more
    prompt and 'decisive' and would lead to a quicker correction of the
    problem.
    YW.
     
    Mike Easter, Feb 27, 2007
    #4
  5. John Jones

    Mike Easter Guest

    Actually, my long post in this thread had 51 lines, not posts

    Lines: 51

    The point of all of that dnsstuff pasting I did was to demonstrate what
    was interesting to /me/ about how verizon had handled and *not* handled
    the nameservice including MX for verison.

    The business of how to misspell verizon isn't really very interesting to
    me; what /was/ interesting was how a major provider had decided to deal
    with the verison issue, and how poorly they had actually pulled it off
    in the MX nameservice department.

    That's what my post was about. I wasn't trying to spend 51 lines of
    dnsstuff pasting to spell verizon correctly.

    The business about addressing some question as asked isn't nearly as
    intersting as addressing the 'question' which interests me.
     
    Mike Easter, Feb 28, 2007
    #5
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.