In article <[log in to unmask]>, "Blaine E.
Thompson" <[log in to unmask]> says:
 
 
 
 
 
>Date: Wed, 19 Jun 1996 09:10:30 -0500 (CDT)
>From: Mail Delivery Subsystem <[log in to unmask]>
>Subject: Warning: could not send message for past 12 hours
>To: <[log in to unmask]>
 
 
I get messages like this from various sites all the time.
I only worry when the problem exceeds 24-hrs weekdays.
Feel free to use DiG or NSLOOKUP against the 4 authoritative
DNS's for that domain, which all happen to be in the
same domain (haven't checked to see if they are all on
the same IP network, in which case, <frown>).
 
netcom.com.     8811    IN      NS      AS3.netcom.com.
netcom.com.     8811    IN      NS      AS4.netcom.com.
netcom.com.     8811    IN      NS      NETCOMSV.netcom.com.
netcom.com.     8811    IN      NS      NS.netcom.com.
 
>    **********************************************
>    **      THIS IS A WARNING MESSAGE ONLY      **
>    **  YOU DO NOT NEED TO RESEND YOUR MESSAGE  **
>    **********************************************
>
>The original message was received at Tue, 18 Jun 1996 17:45:01 -0500 (CDT)
>from postal.tamu.edu [128.194.103.24]
>
>   ----- The following addresses have delivery notifications -----
><[log in to unmask]>  (transient failure)
>(...)
>
>   ----- Transcript of session follows -----
>451 <[log in to unmask]>... IX.NETCOM.COM: Name server timeout
>(...)
>Warning: message still undelivered after 12 hours
>Will keep trying until message is 3 days old
>
>--BDV03291.835193430/postal.tamu.edu
>Content-Type: message/delivery-status
>
>Reporting-MTA: dns; postal.tamu.edu
>Arrival-Date: Tue, 18 Jun 1996 17:45:01 -0500 (CDT)
>
>Final-Recipient: RFC822; [log in to unmask]
>Action: delayed
>Status: 4.4.3
>Last-Attempt-Date: Wed, 19 Jun 1996 09:10:30 -0500 (CDT)
>Will-Retry-Until: Fri, 21 Jun 1996 17:45:01 -0500 (CDT)