>> you're getting the dns timeout because you're off-line.  when you're
>> off-line, sendmail can't look up (or verify) the existence of the
>> address to which (or from which) you are sending the mail, so it stays
>> in the client queue.  when you go back on-line, then the dns lookups
>> can work again, so the queue can be flushed.
>> 
>> this is perfectly normal behavior.
>
>So, you need DNS working even for the local mail delivery from cron to
>root? Doesn't seem to be good.

not at all.  i get my daily output regardless of connectivity issues.
it's important to note the headers of the "after" message that were
posted:

>From tmiller@flex.com Sun Mar 30 03:17:04 2003
>Return-Path: <tmiller@flex.com>
>Received: from aluminum.miller.net (localhost [127.0.0.1])
>       by aluminum.miller.net (8.12.8/8.12.8) with ESMTP id h2U8H41R002829
>       for <root@aluminum.miller.net>; Sun, 30 Mar 2003 03:17:04 -0500 (EST)
>Received: (from root@localhost)
>       by aluminum.miller.net (8.12.8/8.12.8/Submit) id h2U8F0HU000663;
>       Sun, 30 Mar 2003 03:15:00 -0500 (EST)
>Date: Sun, 30 Mar 2003 03:15:00 -0500 (EST)
>From: Charlie Root <tmiller@flex.com>
>Message-Id: <200303300815.h2U8F0HU000663@aluminum.miller.net>
>To: root@aluminum.miller.net

apparently the host knows itself as aluminum.miller.net, yet the daily
report was coming from tmiller@flex.com.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
werdna@squooshy.com       * "information is power -- share the wealth."