[BusyBox] RE: Mail System Error - Returned Mail

[Erik Andersen]

On Fri Feb 08, 2002 at 10:14:44PM -0500, Gregg C Levine wrote:
> Hello again from Gregg C Levine normally with Jedi Knight Computers
> Erik, it did it again! Here is what it said to me:
>
> Reporting-MTA: dns; mtiwmhc25.worldnet.att.net
> Arrival-Date: Sat, 9 Feb 2002 00:45:49 +0000
> Received-From-MTA: dns; who (12.88.80.28)
> 
> Final-Recipient: RFC822; <andersen at codepoet.org>
> Action: failed
> Status: 5.1.1
> Remote-MTA: dns; andersen.dsl.xmission.com (166.70.15.250)
> Diagnostic-Code: smtp; 550 <andersen at codepoet.org>... Relaying denied

166.70.15.250 is not my computer.  It belongs to Tim Riker.
This is not my problem and there is nothing I can do for you
to fix it.  Lets take a look at the cause of your problem for
a minute.  First lets check what your nameserver says for 
andersen.dsl.xmission.com (which is what I use for my MX):

    $ host -X ns1.worldnet.att.net andersen.dsl.xmission.com
    andersen.dsl.xmission.com       A       166.70.14.212

Looks just fine.  New lets look at codepoet.org and busybox.net
from _my_ nameserver:

    $ host codepoet.org
    codepoet.org            A       166.70.14.212
    $ host busybox.net
    busybox.net             A       166.70.14.212

Still fine.  New lets look at codepoet.org and busybox.net from 
_your_ nameserver:

    $ host -X ns1.worldnet.att.net codepoet.org
    codepoet.org            A       166.70.15.250
     !!! codepoet.org A record has zero ttl
    $ host -X ns1.worldnet.att.net busybox.net
    busybox.net             A       166.70.15.250
     !!! busybox.net A record has zero ttl

Oops!  Your nameserver is broken.  Your nameserver has decided to
cache RR values with a zero TTL.  Clearly the idiots running
worldnet.att.net (or more accurately the idiots that wrote their
broken software) never bothered to read RFC-1035 Section 3.2.1:

    TTL ... Zero values are interpreted to mean that the RR can only
    be used for the transaction in progress, and should not be
    cached.  For example, SOA records are always distributed with a
    zero TTL to prohibit caching.  Zero values can also be used for
    extremely volatile data.

http://www.ietf.org/rfc/rfc1035.txt
http://www.freesoft.org/CIE/RFC/1123/121.htm

I'm sorry, but this is not my problem.  Please tell these jerks
that they are using broken DNS software and they should get it
fixed or at least have the decency to flush their (broken) cache.

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--