ADD list password address user-name
ALIas list password new-address address-as-subscribed
[quiet] DELETE list password address [address]
IGNore list password address
LOCk list password
UNLock list password
[quiet] SET list [option arg[s] for address
[address]
or, for adding multiple user-names:
[quiet] ADD list password {address user-name} &
{ address user-name }{ address user-name }
Add specified user(s) to the list. If more than one user is added, enclose
each one in brackets {}. Multiple names may be placed on one line or place
one name per line in brackets. Commands spanning more than one line require
an ampersand (&) at the end of each line to indicate that the command
is continued on the next line. If the optional "quiet" switch
is added before the command line, the user(s) will not be notified. When
adding a user to a list only the following characters are permitted in
a user's address or user-name:
All the alphabetic letters from a - Z including both upper and lower case, all the numbers from 0 - 9, and the following characters [ \ t + = : ; ' . , @ # % ! _ - ] while user names may NOT contain the following characters: ` " < > [ ] { } | $ ~ * ? ! \
(Please note that in this discussion the symbol \t is a combined
symbol which stands for the tab character and not the separate characters
slash-t.)
Although a user-name can be as many words as the user wants, the portion that shows up in a review command is limited to five words including the e-mail address.
Examples:
For a list named "mylist" whose owner password is "foo"
add mylist foo ht56@springfield.org Albert Parker
will subscribe Albert Parker to MyList with the address ht56@springfield.org and Albert will receive a welcome message from ListProc.
quiet add mylist foo trans@springfield.org MaryLou Parker
will subscribe MaryLou Parker to MyList with the address trans@springfield.org but MaryLou will NOT receive a welcome message or any indication of having been added to the list from ListProc because in this case the quiet option was used.
add mylist foo {ht56@springfield.org Albert Parker} &
{trans@springfield.org MaryLou Parker} &
{fort@machine.org The National Janitorial Crew}
will subscribe Albert Parker, MaryLou Parker, and The National Janitorial
Crew to MyList with their respective addresses. All will receive a welcome
message from ListProc. Notice that the subscriber from fort@machine.org
used a four-word name for the subscription. ListProc will accept up to
five separate words in a subscription, one word is used for the address
of the subscriber; the other four words can be used for the subscriber's
name. Note that the ampersand (&) is used here to indicate that
the ADD command is continued on the
next line.
Alias an existing subscriber to a new address. Used in cases where a subscriber needs to be able to send mail from another machine or the subscriber's email address can appear in multiple formats. Mail will be accepted from both the address-as-subscribed and from the new-address. The new-address pattern may be an extended standard UNIX regular expression. For more information on regular expressions, see the section on that subject at the end of this file.
Examples:
For a list named "mylist" whose owner password is "foo" the user ht56@nebbuch.org has informed the list owner that occasionally she would like to be able to send commands to ListProc from another machine but doesn't want to have to subscribe from that machine also. The list owner complied by setting up an alias for the second account.
alias mylist foo ret@kabb.net ht56@nebbuch.org
so that all mail from the second address, ret@kabb.net, is seen by ListProc as being from ht56@nebbuch.org. Using regular expressions, the list owner can map a whole range of e-mail addresses to aliases. For example, a second user has complained that she has an account on a system called whatsoever.net which has 3 machines networked together. Mail can be addressed to her at susie@whatsoever.net. However, when she logs into her account on whatsoever.net she can randomly log into any one of the three machines and her return address can be any one of the 3 machine addresses. The 3 machines are named red, blue, and green. So when she sends mail her message header can say that the mail is from susie@red.whatsoever.net or susie@blue.whatsoever.net or susie@green.whatsoever.net. This results in ListProc having her subscribed to MyList from only one of the three machines and when she is logged into either of the other two machines her commands to ListProc are rejected. This situation is very bothersome for her and she asks the list owner if he can do anything to help her. The list owner responds by sending to ListProc the command
alias mylist foo (.+)@.*\.whatsoever.net \1@whatsoever.net
The addresses being given to the ALIAS
command are regular expressions. The subject of regular expressions is
covered in another section later in this manual. The end result of the
above command is that whenever any mail comes in from any user whose address
ends in "whatsoever.net" the person's username is attached to
the string "@whatsoever.net" and the first portion, either red,
blue, or green, is stripped off.
Delete the specified user(s) from the list. Multiple names may be placed on one line. If the command spans more than one line an ampersand (&) must be placed at the end of each line to indicate that the command is continued on the next line. If the optional "quiet" switch is added before the command line, the user(s) will not be notified.
Examples:
For a list named "mylist" whose owner password is "foo"
delete mylist foo ht56@springfield.org
will remove ht56@springfield.org from MyList and this user will receive a notification that he has been dropped from the list.
quiet delete mylist foo trans@springfield.org
will delete trans@springfield from MyList, but this user will not receive any notification of being dropped because the quiet option was used on the command.
delete mylist foo ht56@springfield.org &
trans@springfield.org fort@machine.org
will remove, or unsubscribe, all three users from the list. All will
receive a notification message from ListProc that they have been removed
from the list. Note that the ampersand (&) is used here to indicate
that the DELETE command is continued
on the next line.
Add a user to a file of troublesome users whose mail to a list should be discarded. The address pattern may be an extended standard UNIX regular expression. For more information on regular expressions, see the section on this topic at the end of this file.
Examples:
For a list named "mylist" whose owner password is "foo" a user has been sending abusive messages to the list and the owner wants ListProc to ignore anything coming from this user. The owner sends ListProc a command saying:
ignore mylist foo ht56@springfield.org
which directs ListProc to totally ignore anything sent to it from ht56@springfield.org. The list owner is notified that this person is still sending messages to the list but none of the messages sent gets posted to the list. Using regular expressions, the list owner can have ListProc ignore a whole range of e-mail addresses. For example, suppose the list MyList is being run for the benefit of only people from the University of Southern Madagascar. The domain for that organization is usmaf.edu. By sending the command:
ignore mylist foo ~<.*\.usmaf.edu>
the list owner instructs ListProc to ignore any address that doesn't
end in "usmaf.edu". The subject of regular expressions is covered
in a section later in this manual.
Suspend execution of list-specific commands and queue them up for later processing. Owners may still issue such commands, unless the list is locked by the listprocessor manager. The list will still process messages.
Resume execution of list-specific commands, including those queued up while the list was locked. All owners may unlock a list, unless it's locked by the listprocessor manager.
Examples:
For a list named "mylist" whose owner password is "foo"
lock mylist foo
will prevent all user commands from being sent concerning the list called MyList. Messages posted to the list will still go out. Commands sent to ListProc concerning MyList will be held until the list is unlocked.
unlock mylist foo
will unlock the list and cause any commands being held from users to
be executed. Anytime a list owner sends an EDIT
command without using the -nolock option,
the list will be locked until the list owner sends an UNLOCK
command or PUTs the file that was EDITed.
Allows list owner to SET subscriber mail options for the subscriber(s). If quiet, the user(s) will not be notified. The SET command also allows the list owner to SET the amount of list control messages that are sent to the person who is designated to receive error messages.
Valid options and args are:
[quiet] SET list mail ack|noack|postpone|digest
- ack | noack determines whether sender of message gets a copy of his/her posted messages back from the list. When ack is set, the user gets a copy of all mail sent to the list. When noack is set the sender does not get a copy of his/her own mail sent to the list.
- postpone causes user's mail to be held until the user releases it. This is useful if a user goes on vacation for a period of time. When the user releases the mail by sending another SET command all held mail is sent.
- digest causes a user's mail to be sent collected into a digest. Certain places like CompuServe charge for mail on a per-message basis. In this case a user may want to have all mail from a list sent in a digest instead of separate messages.
[quiet] SET list password current-password new-password
change list password for user.
[quiet] SET list address password new-address
change the address by which the list knows a user. Using the SET address command you can change the address to which your user receives mail from the list.
[quiet] SET list conceal yes|no
hide user name in commands for lists of subscribers.
List owners can set for themselves any of the following:
[quiet] SET list preference CCoption
- determines which commands sent by users are copied to owners. When a user sends any command to ListProc concerning your list a copy of the output from ListProc will come to either the list owner or the designated recipient of error messages or both. CCoption can be one of:
CCSUBSCRIBE - The list owner gets a copy of all subscription requests.
CCUNSUBSCRIBE - The list owner gets a copy of all unsubscribe requests.
CCRECIPIENTS - The list owner gets a copy of all requests for list recipients.
CCINFORMATION - The list owner gets a copy of all requests for information.
CCSTATISTICS - The list owner gets copied on all statistics requests.
CCPRIVATE -
CCRUN - The ListProc manager gets copied on all run requests.
CCIGNORE - The list owner gets all messages sent by people on the ignore file.
CCERRORS - The list owner will receive a copy of all error messages.
CCREVIEW - The list owner will be copied on all review requests.
CCALL -The list owner and/or ListProc manager gets copied on all of the above. Be aware that this option will generate a lot of mail.
SET list preference CCoption is used to make changes from the defaults which are set by the owner using the 'configuration listname password default preference' command as detailed above.
In addition, options can be set for subscribers by appending the for userid@host.domain to the set command as follows:
[quiet] SET list address password new-address for user@host.domain
[quiet] SET list mail ack|noack|postpone|digest for user@host.domain
In this way, an owner can submit requests for users effecting only that
user account without the need to edit the subscribers file.
Examples:
For a list named "mylist" whose owner password is "foo"
SET mylist mail digest for mark@where.ever.com
will tell ListProc to send all mail from the list called MyList to user mark@where.ever.com as a digest instead of single messages. The user can, of course, send a SET mail digest command himself but if either the set command is disabled by the owner or the user is so unsure of himself that he asks the list owner to do it for him this allows the list owner to do it.
SET mylist mark@last.address foo mark@where.ever.com
will tell ListProc to change the address for mark@last.address in the list called MyList to mark@where.ever.com. This would be in the event that user mark@last.address suddenly lost his account and was unable to unsubscribe from the list. If mark@last.address remembered his list subscriber password, he might have been able to change his address on the list himself using the SET list-name password old-address new-address command which is detailed in the ListProc User Manual.
SET mylist preference ccsubscribe ccunsubscribe ccerrors
will tell ListProc to send all requests to subscribe or unsubscribe
and all error messages to the list owner or other designated recipient
of error messages. (See the section describing the Configuration
delivery-errors-to command above.)
SYStem list password user-address #user-command
Allows the list owner to issue any command on a user's behalf. This
command is a vestigal command from previous versions of ListProc and it
has been replaced by other commands. Its presence in this version of ListProc
is only for the convenience of list owners who are accustomed to previous
versions of ListProc.
[BACK] to the Command Reference Directory
[BACK] to the Table of Contents