>>  >We have a subscriber who is being subscribed over and over to one of
>>  >our lists by someone.. and getting the subscription confirmation
>>  >requests.. over and over..
>
>>  A possible solution to this problem now (which may or may not meet
>>  your needs) would be to SERVE this address OUT.  Any future
>>  correspondence that appears to come from the address would not be
>>  responded to or acted on and would be forwarded to you with full
>>  headers intact.
>
>Serve out a subscriber's address???  How would that affect him on our
>list and the others he is probably subscribed to on the same system?

Until the subscriber is SERVEd back on any messages he sent to
LISTSERV (or any of the mailing lists it hosts) would not be
processed but would instead be forwarded to the listowners or site
managers for examination.  Depending on how annoying the forged
subscription requests are and how frequently they're being sent this
may be your best option; you can serve the user back on once you
receive one of the forged subscription requests.

This wasn't a way of saying that your feature request was
unreasonable; it was a suggestion of something you could try to solve
the problem given that the feature you want does not presently exist.
(I don't know whether such a feature is planned for a future release
or not.)
--
Jacob Haller, Technical Support
L-Soft international, Inc
http://www.lsoft.com/