peer-linked to the list, either directly or via one or more other peer servers. This information is used by the various list management com- mands to determine the "nearest" peer list to a given user. For exam- ple, when a SUBSCRIBE command is received from a user and it is deter- mined that there is a better (nearer) peer list for him, the subscrip- tion request is automatically forwarded to the appropriate LISTSERV. ****************************** * Renewal= Yearly | Monthly * ****************************** This keyword enables the automatic removal of subscribers to a list if they do not re-subscribe within a required time. The user is notified twice, via e-mail, of their pending removal, if they do not reply, the third message sent is notification of their removal from the list. (A nice way to help keep your list clean of dead users.) The default is "Renewal=" (disabled) Note: If this option is enabled for a list, the owners may alter the setting of an individual subscriber via the SET command. SET listname NORENEW FOR x@y ******************************************** * Reply-to= (destination),Respect | Ignore * ******************************************** Indicates whether the "Reply-to:" tag supplied by the sender of the mail file is to be preserved or discarded (if present), and, if discar- ded or omitted, what should be placed in the new "Reply-to:" generated by the server. The default value is "List,Respect". Note that some mailing systems are unable to process a "Reply-To:" field with multiple addresses correctly and may therefore disregard the "Reply-to= Both" option and treat it as "Reply-to= List". Respect: The original "Reply-to:" tag, if any, is kept. Ignore: The original "Reply-to:" tag is ignored and discarded. ************************** * Review= (access-level) * ************************** This keyword defines the category of users who are allowed to review the network addresses and names of the persons subscribed to a list. The default value is "Public". Note: Individual subscribers to the list can use the SET command to CONCEAL their names from the people who REFIEW the list. ********************************* * Send= (access-level) | Editor * ********************************* Defines the category of users who can mail or send files to the list. Possibly puts the list under control of an editor. The default value is "Public". When the list is controlled by an editor, any file or piece of mail sent to the list is forwarded to the editor, who is the only person (with the list owner) to be able to actually mail or send files to the list. The network address of the editor is defined by the "Editor=" keyword. ******************************** * Service= (area1),(area2),... * ******************************** Defines the 'service area' outside of which subcription requests must not be accepted. When a SUBSCRIBE command is received, the "Peers=" keyword is checked first to see if there is a nearer peer list in the network. If it is the case, the command is forwarded to this nearer server. If not, the service area is checked to ensure that the recipient is acceptable; if it is not, the subscription request is denied. When the command is forwarded, the destination server might still deny access to the list if the subscriber is outside its own service area, if any. It is important to note that the service area check is made only after the "best placement" check. This allows several servers in the same country to share an identical service area, eg "Service= Germany", and still have users subscribed to the best possible server. Code "Service= Local" if you want to allow access by MIT address only. ************************************************** * Stats= Normal | Extended | None,(access-level) * ************************************************** Indicates whether or not statistics are to be maintained for the list and if yes, which level of statistics is desired and who is able to retrieve the statistics reports. The default value is "Normal,Private". Normal statistics include number of mailings, number of outbound mail files, and total number of outbound 80-character records, for each user on the list, and a similar information for file distribution. Extended statistics include all of the above plus actual network load indication in "link.kbytes" units. ****************************************** * Subscription= By_owner | Open | Closed * ****************************************** This keyword defines whether or not new users are allowed to subcribe to the list, and if not, whether their subscription requests are to be forwarded to the list owner or not. Open: The users are allowed to subscribe to the list. By_owner: The users are not allowed to subscribe, but their requests will be forwarded to the list owner. This is the default. Closed: The users are not allowed to subscribe, and their requests are not to be forwarded to the list owner. *************************************** * Validate= Store only | All commands * *************************************** Under Revised LISTSERV, lists are protected by a password which must be specified by the list owner when he sends an updated version of the list back to the server. When "Validate= All commands", password valida tion applies to ALL the commands that modify the contents of the list, eg SIGNOFF, SET, etc. This implies that users cannot use these commands since they do not know the list password. A notable exception is the SUBscribe command, which can still be used (if enabled) to get on the list; however, sending a second SUBscribe command for the same list (to correct a spelling error in your name) would result in the command being forwarded to the list owner and not immediately executed. This is to protect you from UREP hackers who might issue a command "from" your userid@node to change the name under which you appear on the list to something impolite. The default is "Store only", but it is recommended that "serious" or "important" lists be changed to "Validate= All commands". ****************************** * X-Tags= Yes | No | Comment * ****************************** Indicates whether "X-To:" and "X-cc:" tags are to be included in the output mail files to list recipients of the original mail file (other than the list userid) or not, and how they should appear in the RFC822 header. Yes: This information must be provided in the form of "X-To:" and "X-cc:" tags in the RFC822 header (similar to the "To:" and "cc:" tags). This is the default. Comment: This information must be provided in the form of "Comment:" tags, ie "Comment: X-To:" and "Comment: X-cc:". No: This information must not appear at all in the mail haeder. ************************************************************************* ** Generic parameters ** ** ------------------ ** (net-address): Describes a RFC822-compatible network address, usually of the "userid@node.domain" form. (access-level): Controls which category of users has access to the information or service to which this para- meter applies. (access-level) can be either: Public Everybody has access to the information. Postmaster Only the postmaster (ie LISTSERV operations staff) has access to the information. A1,A2,... with Ai being either: Private Only users subscribed to the list have access to the information. (listname) Only the members of the specified list have access to the info. Owner Only the list owner can access the information. Owner(list) Only the owner of the indicated list can access the information. Service Only people in the service area of the list can see the info. Service(list) (destination): Indicates the destination of a piece of mail, message or reply. Depending on the type of reply, all the options listed below might not be effective. For example, "Reply-to= None" is functionally identical to "Sender", whereas "// JOB Reply-to=None" (in a batch command file) would actually suppress all replies. List The reply message is sent to the list. Sender The reply message is sent to the sender of the original piece of mail. Both The reply message is sent both to the list and to the original sender. None No reply message is sent at all. "address" The reply message is sent to the specified network address if enclosed in double quotes (interval): Is a time interval that indicates how frequent ly an operation is to be renewed. Note that depending on the operation being performed, some of the options may not be available. For example, "Notebook= Yes,A,Daily" is not avai- lable. Yearly Monthly Weekly Self-explanatory Daily Hourly Single The operation is to be done only a single time. (peer): Is the node-id or network address of a peer list server. If the name of the peer list is the same as the name of the local list (which will usually be the case), only the node name needs be given. If the list names are diffe- rent, the full list network address must be given, eg "REXX-L@UIUCVMD". (area): Is a means whereby a node or list of nodes can be identified. An area can be either: - The name of a network, eg EARN, BITNET - The name of a country, eg Germany, Canada - 'Local', in which case it is equated to the value of the "Local=" keyword (qqv). - A node name, eg FRECP11 - A simple wildcard nodename pattern such as FR*, *11, *ESA*, D*ESA*, etc (mon-address): Is a means whereby 'list monitors' can be iden tified (the term 'list monitor' refers to a human person who monitors the activity of a list). A 'mon-address' can be: - A single network address, eg INFO@TCSVM - 'Postmaster', which indicates the "main" postmaster - 'Postmasters', which indicates ALL the post- masters, main and alternate - 'Owner', which indicates the "main" list owner (the first to be listed in the "Owner=" keyword) - 'Owners', which indicates ALL list owners Whenever several keywords or operands are accepted, they will be separated by a logical OR sign (|). Unless specified otherwise, commas have "higher priority" than OR signs, that is to say, "Public|Private, Open|Closed" means "(Public|Private),(Open|Closed)", not "Public| (Private,Open)|Closed".