LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Parts/Attachments: text/plain (41 lines)
Print Reply
Sender:
"Forum on LISTSERV release 1.6" <[log in to unmask]>
Subject:
From:
Gary Sponseller <[log in to unmask]>
Date:
Fri, 3 May 1991 13:02:10 EDT
In-Reply-To:
Message of Fri, 3 May 91 08:25:16 EDT from <USDGK@VTVM1>
Reply-To:
"Forum on LISTSERV release 1.6" <[log in to unmask]>
On Fri, 3 May 91 08:25:16 EDT Greg Kroll said:
>On Fri, 3 May 91 10:23:26 BST <KINSELLA@IRTCCARL> said:
>>...deleted...
>>Is there an easy solution? (I know the obvious one of log on as the student
>>but that is messy.)
>>
 
>Austin,
>
>  You will need POSTMASTER privilege to do this, but a good way to
>"unsubscribe" a user from any and all lists would be:
>
>for <userid>@<node> signoff * (netwide
>
>  where: <userid> = the userid of the person you are acting in behalf of.
>         <node>   = the node name of the above stated userid.
>
>POSTMASTER privilege is defined in LISTSERV's LOCAL SYSVARS file via the
>POSTMASTER= variable.  Hope this helps!
>
>--Greg Kroll
 
I *strongly* advise using the "Listserv JOB" method over the one-by-one
"FOR userid" method!  The Job is much easier on network/local resources...
 
Cut out the job below and fill in your users' addresses.  Send to your
local backbone Listserv address for processing.  I do student userids
at the end of each semester this way and it works quite well.
 
Regards,
Gary
 
-- cut here --
//Cleanup   JOB  Echo=No
QUIET Delete * DD=NAMES ( NETWIDE
//Names DD  *
user1@node
user2@node
user3@node
/*

ATOM RSS1 RSS2