On Tue, 03 Nov 1998 16:04:56 +1000, you said:
> I have followed these instructions, and yet we still keep getting these
> messages. Is there some way to check that I have the latest tables in
> place or could there be a problem somewhere else.

OK.. here's the scoop.  The message quoted is one that I've been
automatically generating under the following conditions:

1) A Listserv distribute job arrives at vtbit.cc.vt.edu (which already
indicates your tables are out of date, as that went off the backbone
many months ago), and the outbound files bounce because the
destination nodes aren't in Bitnet anymore either.  The message
generator keys off this bounce message.

2) A distribute job arrives for ECUVM.Bitnet.  This one is so old I
can probably drop it.. ;)

3) A distribute job arrives at vtbit.cc.vt.edu, and generates an error
message with '<DIST2> Server number NNNN not found'.  Again, (a) the
job shouldn't have been routed to vtbit, and (b) the originating
server *also* thinks *another* since-gone server is still there.

The two most common causes of problems I've seen are:

A) failure to put the files in the right place
B) failure to actually restart Listserv.

To see the current table versions, send a 'show release' to your
Listserv - the current tables are VERS9810, with VERS9811 due in a
few days.

--
                                Valdis Kletnieks
                                Computer Systems Senior Engineer
                                Virginia Tech

For what it's worth, at least *some* sites are actually reading these
messages and acting on them.  I'm seeing a number of sites that are
chronically unreachable at all, or that bounce mail addressed to
'postmaster'.