Hello,
 
Two questions.
 
First the easy one.  From time to time (three times in the last 48 hrs),
listserv dies (the lsv process "goes away").  Our systems folks can
see no local reason why.  Obviously, we can implement procedures to
respawn the process, but we were curious if others had observed this
behaviour.
 
Secondly, our list NET-HAPPENINGS distributes to 20k+ folks who for the most
part all receive a daily digest.  Many though do not, and receive the
20 to 30 daily posts individually.  Due to transient and sometimes,
not so transient conditions, this volume generates approximately
3000 - 5000 error messages each day usually of this form:
 
####################### Message Follows ###########################
 
178 Dec 21 L-Soft list server (182)  NET-HAPPENINGS: error report from BB
 
Date:         Thu, 21 Dec 1995 04:57:52 -0500
Subject:      NET-HAPPENINGS: error report from BBCGATE.BBC.CO.UK
To: [log in to unmask]
X-LSV-ListID: None
 
The enclosed mail  file has been identified as a  delivery error for list
NET-HAPPENINGS because it was sent to the reserved 'owner-net-happenings'
mailbox.
 
<snip snip>
 
From: Mail Delivery Subsystem <[log in to unmask]>
Subject: Warning: could not send message for past 4 hours
Message-Id: <[log in to unmask]>
To: <[log in to unmask]>
Auto-Submitted: auto-generated (warning-timeout)
 
 
        **********************************************
        **      THIS IS A WARNING MESSAGE ONLY      **
        **  YOU DO NOT NEED TO RESEND YOUR MESSAGE  **
        **********************************************
 
        The original message was received at Thu, 21 Dec 1995 05:17:22 GMT
        from lists.internic.net [198.41.0.15]
 
        ----- The following addresses have delivery notifications -----
        [log in to unmask]  (transient failure)
        (expanded from: <[log in to unmask]>)
 
####################### End Enclosed message ######################
 
 
Here is my question....
 
Is this normal behaviour?  Does the listserv owner and the "Errors TO"
entry in the list config normally receive such notices?  We recognize
that we can filter these notices with procmail, but it seems then
that we would be addressing the symptom and not the underlying cause.
How do other maintainers manage error messages?
 
Many thanks,
 
Tom
 
 
--
 
Tom Newell              [log in to unmask]    +1 703 742 4796
NIC Liaison             InterNIC Support Services