> The problem is essentially the same regardless of what you modify. If you
> have multiple owners with the kind of connectivity problem you described,
> you want to avoid this kind of scenario:
 
Thanks for the answer, Eric.  This reminds me of what I just said about
the listproc list.  The few times I asked questions on that list, I got
answers like "go into x/blop|dev%&groof and run zinoffern|xx0 on your
hglefer#zud scramster."  Every time I've asked a question on this list,
I've gotten a clear and useful answer.
 
Btw, if any of you VM people would like to help solve a mystery, let me
know and I'll send you a copy of the headers of mail that takes four or
five hours to get here from UGA.  The problem is not in the route between
there and here.  The mail does something on the UGA system for all that
time.  That much is clear from the headers.  What it does is not clear.
OTOH, I guess there's no point in my knowing what it does since there's
nothing I can do about it.  I'm thankful that I can run lists from that
system, even with the delays.  I got spoiled during the years when mail
got here almost instantly.  Something changed there several months ago.
   --Natalie ([log in to unmask])