Owners

Maintaining your mailing list

Modifying the mailing list options

Replace "listname" in the command GET listname (HEADER with the name of your list and send it to LISTSERV@LIST.ETSI.ORG (The ")" is deliberately omitted).

You will receive an e-mail containing a copy of your list header :

* listname : sample description for listname
* Owner=name@email.address (some one)
* Subscription= by owner, confirm.
* Renewal=6-monthly,delay(25)
* SET listname NORENEW for name@email.address
* Validate= YES,CONFIRM
* Review= Private
* Confidential= No
* Send= Private
* Notify= Owners
* Errors-To= Owner
* Auto-Delete= Yes, Semi-Auto,Delay(4),Max(100)
* Notebook= yes,d:\archive,monthly,private
* Digest= yes,d:\archive,daily,01,1000

The GET command automatically locks the header. This has the advantage that another owner cannot make changes at the same time but it also prevents users from subscribing or unsubscribing. Edit the list header to change the options as required, remembering to replace the xs in the PW= xxx with your list password. Add the following line to the top of the list header, remembering to replace listname with the name of your list.

PUT listname LIST

Send the modified header to LISTSERV@LIST.ETSI.ORG

If you decide not to modify the header you can release the lock on the list by sending the command

UNLOCK listname

Note: you can request the header and a list of the subscribers by omitting the "(header" part of the GET command, but you must not try to modify the subscriber part of the header.

Adding and deleting subscribers

Occasionally a user may not be able to subscribe or unsubscribe using the normal commands. In this case you can use the add and delete commands.

ADD listname him@e-mail.address (firstname lastname)

DELETE listname him@e-mail.address

e.g. ADD TESTLIST FRED@ETSI.ORG (FRED DUPONT)

Troublesome subscribers

Hopefully, within the ETSI community, this won’t be a problem, however LISTSERV has some built-in features and it is worth describing them.

The list owner can set a subscriber to NOPOST which will allow them to receive mail but which will prevent them from posting mail to the list. This could provide observer status for some subscribers.

If a user sends more than 21 consecutive invalid commands to LISTSERV, LISTSERV automatically rejects any further commands from that user. This could happen if a user accidentally sends a file to the address reserved for commands. It is possible for the list owner, or any other list subscriber, to issue a SERVE him@e-mail.address command to restore that user's access. As with all other LISTSERV commands, the SERVE command is sent to LISTSERV.