>> I think of something like: >> ALTER <listname> <newid>@<node> > >Wow! That would allow you to SUBSCRIBE to a list, and then ALTER your >user@node to someone else's user@node -- thus inundating HIM with the >list traffic. > Well - it could be a two steps process : 1. Send an ALTER * NETWIDE ( newid=....... newnode=........ 2. Send from the new id a validating message, ALTER * NETWIDE ( FROM oldid=..... oldnode=...... You could change step2 and have the LISTSERV to which #1 was sent send mail to newid@newnode asking for confirmation (in a form such as suggested in #2), and informing that if unconfirmed during ??? (a month?) will cause the ALTER to be changed to SIFNOFF. I know, originally the suggestion was about A list, but I think it's a lot of trouble for just one list.....and if someone is only subscribed to 1 list, then in that case *=1 ...... /Zvika