Due to a marked increase in mail problems this week (and I mean problems
at mail relay sites, not local connection problems from UTC) I'm obligated
to waste a little bandwidth to get this on record.
 
If you subscribe to the mailing list and everything gets "quiet" - which
for this list is typically no mail in 24 hours - you can confirm that you
are still on the list by sending a "query hp3000-L" to [log in to unmask]
If you get no response, you might consider resubscribing.
 
List delivery errors are forwarded to me by Listserv.  When the volume is low
and I have time, I try to review them and attempt to contact postmasters at
problem sites if possible; otherwise I delete the notices in bulk.  If they
continue, I will set users in digest mode (reduces bounces to 1 per day).  If
that doesn't work, I remove the offending user.  Listserv itself filters the
error bounces that are in "standard" format and will delete you if bounces
persist for several days.  But enough background...
 
Last weekend I had excessive errors from:
   [log in to unmask]  (host unknown at relay crl.com)
   [log in to unmask]  (connection refused to 192.69.46.246 from disc.com)
   [log in to unmask]  (mailbox full, but netcom.com in general bounced a lot
                      of mail two weeks ago)
   [log in to unmask]  (unknown user, this may be legit)
   [log in to unmask]  (host unknown at relay rcwi01.rcw.bp.com)
   [log in to unmask] and [log in to unmask]  (unable to
      connect, still a problem this week)
   [log in to unmask]  (irrecoverable error from relay vm.cnuce.cnr.it)
   Enrique at HP Mexico (bounced last week, but OK now)
 
This week:
   rockwell.com  (bounced Charles Meeker, but I think its fixed now)
   jpmorgan.com  (refused some arbitrary mail items)
   various sites served by uunet.uu.net (MWHSE.COM in particular), uunet has
      an MX loop defined internally and they're still bouncing
   various sites served by mcimail.com (Birket Foster at WRQ and others)
   someone at east.east-slc.edu (bouncing all week, local MX loop)
 
I'm posting this information primarily to let the "victims" know about the
problems, you might want to retrieve the archive files for the last week or
two (mail to [log in to unmask], text 'get hp3000-l log9507D' or log9507E)
 
Sorry for bandwidth waste, but I'm haunted by thoughts of these folks out
there wondering where their list mail went :-)
 
On the bright side, we had an unusually large batch of new users this week,
which may offset the losses due to mail problems.  Greetings to all the new
subscribers.
 
[\] Jeff Kell <[log in to unmask]>  HP3000-L List Janitor