Once you have used the DISTRIBUTE MAIL DEBUG=YES to determine
which LISTSERV (Bitnet nodes) are involved in the delivery,
you also have to interrogate each Bitnet node along the
path (realizing that there may be more Bitnet nodes involved,
than LISTSERV sites) -- and these links can be different from
LISTSERV's view since local routing can affect same i.e.,
you must issue various RSCS (or JES2 or JNET) cmds to interrogate
each node along the way to find the next hop, and any link backlog.
 
Then, you might encounter a Bitnet/Internet gateway, so you have
to figure out how to interrogate it (SMTP QUEU cmd?).  Even when
you have done that, MX hosts might be involved, followed then
by e-mail forwarding at the target FQDN, all along hoping that
all DNSes involved are in synch, or someone did not change an IP
address and had a too-long TTL for the old address.
 
Makes for several interesting career paths ;-)
 
--  co-owner INFOSYS, TQM-L, CPARK-L, ERAPPA-L, JANITORS, LDBASE-L, et -L
[log in to unmask] "No joyriders on the Info Super Hiway!"+1 814 863 1843
31 Shields Bldg. -- Penn State Univ -- University Park, PA 16802-1202 USA