>If I understand correctly LISTSERV command processor runs on the VM
>mainframe but the "distribute" module(?) would be on machine connected
>to the mainframe ? In the header there was another machine (I would
>assume an outgoing gateway) My problem is how can I kow what caused the
>7 hours delay for sat least one (and maybe some more) message(s) out 150
>?

Command processing output is NOT shipped through the distribute
backbone.  List "distrbitutions" are.   That means that
if a user unsubscribes, they may get notification that that
had occurred, yet still receive lots of distributions that
were already in-transit.

>Is it a normal occurence for LISTSERV delay shiiping a mailfile to the
>next host ? If not then I will try to get in contect with Brown LISTSERV
>Maintainer ...

(mail) SlIP happens, esp. on weekends.