Sending too many incorrect commands (either explicitly by the user, or
implicitly by some errant mail process) to LISTSERV itself can cause this.

You as another LISTSERV user can try to issue the following

SERVE userid@node

If that returns service, then it was probably the above problem. If not,
the a LISTSERV admin explicitly had turned OFF service and you'll need to
contact that admin.

/Pete