Another alternative solution to this is to use LISTSERV Maestro, and
have the lists in "HRLs" (Maestro hosted recipient lists) or in a
separate database that Maestro can access read-only. In both these
cases, LISTSERV has no control over the recipient list. In the case
of the Maestro-hosted list, you can decide on a list-by-list basis
whether to allow subscribers access to the subscription data. In the
case of a pull from a separate database, then it is up to the person
who maintains the database.
This assumes that you are talking about one-way lists (announcements,
newsletters, etc.) to which a limited number of people can post and
not about discussion lists. I assume that no one would be so
heartless as to trap someone on a discussion list :-).
--
Francoise Becker <[log in to unmask]>
Knowledge is just a click away: http://www.lsoft.com/optin.html