On 2/15/2006 17:22, Winship wrote: > Douglas Winship wrote: >>> Then send: lock listname > > Ben Parker replied: >> Unfortunately that is not a valid command. The only way to LOCK a list is >> via a GET of the list. There is an UNLOCK command but not a LOCK command. >> I've tried this. > > Well, I haven't tried in with the current LISTSERV my host site is using, > but, LOCK [listname] > used to be an entirely valid command for listowners to use. Some > listowners used to use it to prevent subscribers from leaving the list. > If you will think back a few years you may recall my complaints to you > at L-Soft (and specifically to you, Ben) about such activity by listowners > whose lists were hosted at L-Soft. > > Douglas Winship [log in to unmask] > There is no 'lock' command in LISTSERV 1.8e. ----- extract from listserv.log ----- 15 Feb 2006 17:40:01 Processing file 24170085 from [log in to unmask] 15 Feb 2006 17:40:01 From [log in to unmask]: lock test-l 15 Feb 2006 17:40:01 To [log in to unmask]: Unknown command - "LOCK". Try HELP. 15 Feb 2006 17:40:01 Sent information mail to [log in to unmask] ----- end extract ----- We use the 'get' command to lock lists. -- Paul Russell Senior Systems Administrator OIT Messaging Services Team University of Notre Dame