Lists are on hold due to problems with mail not going out:

     o  A message is received, from list3, by the sender saying "message
     delivered"; review of various logs (seems to) show same.
     o  "Review" of list3 gets a message showing as subscribers
     [log in to unmask] (a system 20 miles away) and [log in to unmask] (a system
     2000 miles away).
     o  Telnetting to either [log in to unmask] or [log in to unmask] would show no
     receipt of any messages from list3, even several days after they were
     sent (from within the workplace to list3).
     o  Daily Monitoring report shows self@ and oddname@ with (unspecified)
     errors.
     o  List2, with the same two external accounts plus a dozen or more
     other subscribers, showed receipt of sent messages; in fact, some
     users across the country responded to test messages with "Received
     it."
     o  Sometime the last few days, list2 (and list3) were no longer
     getting mail out, including to the above addresses external to the
     building. "Review" still shows self@ and oddname@ as subscribers.
     o  There is _some_ evidence that list3 and list2 quit getting mail out
     about the time changes were made to /etc/aliases (actually
     /etc/mail/aliases) to include for list3 the five required lines. Yes,
     that could appear to point to that file's being changed, but it is not
     definite. (List1, a third list, was also added to aliases yesterday).

     The easy answer is "You changed a file, look there." However, that has
     yielded no answers. We have delegates of an international system
     awaiting this list, "due yesterday."Other potential lists are on hold.

     I am contacting various tech support (such as this list) and reviewing
     documentation. Our Unix Administrator is baffled at the moment as
     well. Who has experience in problem(s) like this?

     Apologies for the long post.   Thanks, Doug USDOE/OSTI Listserv Admin.