>>Do all of you carefully read through every error report that arrives?
If not, then how do you decide before reading an error report wheather
it is one to discard or a new error you need to read?
 
Roger
[log in to unmask] - Roger Myers<<
 
Are you kidding?  My list, Healthre, is moderately busy with 500 subscribers,
about 40% set to mail and the rest to digest.  There are 20 messages
on a good day and more than 50 messages on a bad day.
 
I read the error message carefully enough to identify the problem
subscriber and then set the account to digest on the very first
bounce.  For some accounts (aol.com) this save much grief
in terms of dozens or maybe even hundreds of bounced error messages.
For some accountes (usually an .edu) it may help a bit but sometimes
the error messages are outdated (like 3 to 7 days old) and might
actually go away on their own if you let them -- it's like seeing
the light from a supernova that exploded hundreds of years ago --
by the time you get the error message the problem has already
been fixed.  But you never know, so I set them to digest anyway.
 
This leads to an occasional over-reaction, some system that's down
and just bounces a few messages but that's rare.
 
Once the acount is set to digest I don't bother reading the
error messages unless it's a bounce of the digest.
 
After four bounced digests the subscriber gets deleted.
 
Well that's what my co-owner and I do.  Don't know if its the
most efficient but it works and we only rarely found gnashing our
teeth and screaming.
 
Eleftheria Maratos-Flier