Beijing Paradise BBS Backup

home *** CD-ROM | disk | FTP | other *** search

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / VMS220.ZIP / DOC / MANUAL.DOC < prev next >

Wrap

Text File | 1993-05-22 | 205.8 KB | 6,932 lines

V-MailServer User Manual Release 2.20 May 22, 1993 Vandenberg Systems Research V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Copyright (c) 1993 Richard Vandenberg ii ───────────────────────────── Table of Contents _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Limited Warranty . . . . . . . . . . . . . . . . . . . . . . . . 3 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 File Servers . . . . . . . . . . . . . . . . . . . . . . . . 5 Mailing Lists . . . . . . . . . . . . . . . . . . . . . . . 5 Automatic File Sending (AFS) . . . . . . . . . . . . . . . . 6 Message Processing . . . . . . . . . . . . . . . . . . . . . . . 7 Process Description . . . . . . . . . . . . . . . . . . . . 8 Header processing 8 Mailing list processing 8 AFS processing 8 Mail server command processing 9 Access Control Language (ACL) commands 9 Processing the Queued requests . . . . . . . . . . . . . . . 9 File Server Commands . . . . . . . . . . . . . . . . . . . . . . 13 Basic File Server Commands . . . . . . . . . . . . . . . . . 13 Advanced File Server Commands . . . . . . . . . . . . . . . 14 Basic Mailing List Commands . . . . . . . . . . . . . . . . 14 Advanced Mailing List Commands . . . . . . . . . . . . . . . 15 Administrative Commands . . . . . . . . . . . . . . . . . . 17 Miscellaneous Commands . . . . . . . . . . . . . . . . . . . 18 General Information . . . . . . . . . . . . . . . . . . . . . . . 19 Configurable Messages . . . . . . . . . . . . . . . . . . . 19 Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Global Macros 20 Macros specifically for the configurable messages 21 Command-specific macros 22 Special Macro Functions 23 Header Conversion . . . . . . . . . . . . . . . . . . . . . 26 Occurrences and Line numbers 28 Notes about Header Conversions 30 Multiple Header Conversion Files 31 Access Control Language . . . . . . . . . . . . . . . . . . 32 General ACL Operation 32 Command syntax 33 ACL Examples 37 User-Defined Commands . . . . . . . . . . . . . . . . . . . . . . 39 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Planning the configuration . . . . . . . . . . . . . . . . . 41 Basic Configuration . . . . . . . . . . . . . . . . . . . . 41 Installation Steps 41 Configuration File . . . . . . . . . . . . . . . . . . . . . . . 45 Mail Delivery Parameters . . . . . . . . . . . . . . . . . . 45 Copyright (c) 1993 Richard Vandenberg iii V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Mail Addressing Parameters . . . . . . . . . . . . . . . . . 45 Encoding parameters . . . . . . . . . . . . . . . . . . . . 46 Files and Paths Parameters . . . . . . . . . . . . . . . . . 48 Obsolete Configuration Parameters . . . . . . . . . . . . . 52 Configuring File Server Services . . . . . . . . . . . . . . . . 55 Setting up the SearchTree and ValidPaths files . . . . . . . 55 Header Conversions . . . . . . . . . . . . . . . . . . . . . 57 Configuring Mailing Lists . . . . . . . . . . . . . . . . . . . . 59 Master Mailing list file . . . . . . . . . . . . . . . . . . 59 Membership Files . . . . . . . . . . . . . . . . . . . . . . 60 Option files . . . . . . . . . . . . . . . . . . . . . . . . 61 Flag Values 61 Global Options 61 User Options 64 Making manual changes 65 Header Conversions . . . . . . . . . . . . . . . . . . . . . 65 Mailing List Owner Messages . . . . . . . . . . . . . . . . 66 Subscription requests 66 Authorized-Subscription Requests 67 Signoff Requests 67 Mailing List Administration . . . . . . . . . . . . . . . . 68 Off-Site Mailing List Administration . . . . . . . . . . . . 68 Configuring Automatic File Sending Services . . . . . . . . . . . 69 Controlling Access with a Reject File . . . . . . . . . . . . . . 71 Controlling Access with Passwords . . . . . . . . . . . . . . . . 73 Kill File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Traffic Monitoring . . . . . . . . . . . . . . . . . . . . . . . 77 Monitoring Operation . . . . . . . . . . . . . . . . . . . . . . 79 Command Line Options . . . . . . . . . . . . . . . . . . . . . . 81 VMAIL Options . . . . . . . . . . . . . . . . . . . . . . . 81 VMAILX Options . . . . . . . . . . . . . . . . . . . . . . . 82 Private User Directories . . . . . . . . . . . . . . . . . . . . 85 UserDir File and UserSecurity File . . . . . . . . . . . . . 85 Private Mailing List Files . . . . . . . . . . . . . . . . . 85 Additional Programs . . . . . . . . . . . . . . . . . . . . . . . 87 DIGEST . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 KILLTRAF . . . . . . . . . . . . . . . . . . . . . . . . . . 89 TRAF2CDF . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Copyright (c) 1993 Richard Vandenberg iv ───────────────────────────── Table of Contents _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ VINFO . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 VMEXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Upgrade Policy . . . . . . . . . . . . . . . . . . . . . . . . . 95 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 96 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Copyright (c) 1993 Richard Vandenberg v V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Copyright (c) 1993 Richard Vandenberg vi ───────────────────────────── Licensing Agreement _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ V-MailServer is Copyright (c) 1993 Vandenberg Systems Research and Richard Vandenberg. Mailing address: Richard Vandenberg Vandenberg Systems Research 2255 West 5th Avenue #204 Vancouver, BC Canada V6K 4K1 Telephone: (604) 739-6150 Fax: (604) 739-6148 Email: rick@vsystem.wimsey.bc.ca V-MailServer was developed by Richard Vandenberg and Vandenberg Systems Research, and is the sole property of Richard Vandenberg. The V-MailServer files are packaged together as a single PKZIP (TM) generated archive. UNDER NO CIRCUMSTANCES MAY ANYONE MODIFY THE V-MAILSERVER EXECUTABLE FILES, OR MODIFY THE ARCHIVE IN ANY FASHION, OR DISTRIBUTE V-MAILSERVER IN ANY OTHER FORM THAN THE PKZIP(TM) FORMAT ARCHIVE IT WAS ORIGINALLY ISSUED. The V-MailServer programs are "shareware programs" and are provided at no charge to the user for evaluation. Feel free to share them with your friends, but please do not give it away altered or as part of another system. The essence of "user-supported" software is to provide personal computer users with quality software at low prices, and yet to provide incentive for programmers to continue to develop new products. If you find these programs useful and find that you are using V-MailServer and continue to use V-MailServer after a 60-day trial period, you must register the software. This registration fee will license one copy of V-MailServer for use on any one computer at any time. You must treat this software just like a book. IE. - Only one person may use it at a time. Other licensing arrangements may be made by contacting us. You are encouraged to pass a copy of V-MailServer along to your friends for evaluation. Please encourage them to register their copy if they find that they can use it. The registration form is in the REGISTER.DOC file. Copyright (c) 1993 Richard Vandenberg 1 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Copyright (c) 1993 Richard Vandenberg 2 ───────────────────────────── Limited Warranty _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ V-MAILSERVER IS SUPPLIED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK RELATING TO THE QUALITY AND PERFORMANCE OF THE PROGRAMS IS ON YOU. IN THE EVENT THERE IS ANY DEFECT, YOU ASSUME THE ENTIRE COST OF ALL NECESSARY SERVICING, REPAIR, OR CORRECTION. SOME PROVINCES OR STATES DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS AND YOU MAY HAVE OTHER RIGHTS WHICH VARY FROM PROVINCE TO PROVINCE AND STATE TO STATE. Richard Vandenberg and Vandenberg Systems Research do not warrant that the functions contained in the programs will meet your requirements or that the programs will be uninterrupted or error-free. IN NO EVENT WILL RICHARD VANDENBERG OR VANDENBERG SYSTEMS RESEARCH BE LIABLE TO YOU FOR ANY DAMAGES (INCLUDING ANY LOST PROFITS, LOST SAVINGS, OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF OR INABILITY TO USE SUCH PROGRAMS EVEN IF RICHARD VANDENBERG OR VANDENBERG SYSTEMS RESEARCH HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES) OR FOR ANY CLAIM BY ANY OTHER PARTY. SOME PROVINCES AND STATES DO NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES SO THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU. Copyright (c) 1993 Richard Vandenberg 3 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Copyright (c) 1993 Richard Vandenberg 4 ───────────────────────────── Overview _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ V-MailServer is a file server that can be used to retrieve files via electronic mail. It also includes powerful features for administering mailing lists and Automatic File Sending (AFS) requests. File Servers File servers (or mail servers as they are also known) are used throughout the Internet and Usenet community to allow the retrieval of files through e-mail. A command language is available that allows the user to retrieve specific files, help files, the list of available files, or information on various topics. There are some well-known file servers for UNIX machines and IBM mainframes that provide a vast array of services for the user. You may be familiar with the BITNET LISTSERV mail servers. V-MailServer provides facilities similar to these servers. Of course, V-MailServer is not as powerful as the minicomputer-based LISTSERV software. However, it operates in a similar fashion. A message sent to V-MailServer with the command "/PDGET /public/pc/file.zip" will cause V-MailServer to send "file.zip" to you as several encoded e-mail messages. Sending the command "HELP" will fetch the help information, just as "INDEX" will get the list of available files. The "INFO" command can be used to obtain further information on any defined topic. These and other commands are discussed in more detail later in this guide. Mailing Lists Mailing lists provide a mechanism to make group communication easier. People with a common interest can join a mailing list dedicated to a specific topic. Examples of existing mailing lists are the 386-User's mailing list and the UUPC-info mailing list. Any message sent to the mailing list address is automatically forwarded to all members on the list. Operation of the mailing list differs, depending on what software is being used. Some lists are simply alias expanders that do nothing but relay messages to all people on the list. Others perform processing on each message, such as stripping off irrelevant header information. To join some mailing lists, the administrator must manually add you to the list of addresses. Other mailing lists provide a fully-automatic method of joining the list with SUBSCRIBE and SIGNOFF commands. To join a list you send a command such as "SUBSCRIBE VMAIL-L." This will generally add you to the mailing list immediately. The advantage to this is that it is much simpler for the user and the administrator. Existing software provides varying degrees of automation, from completely manual operation, to fully automatic. V-MailServer is Copyright (c) 1993 Richard Vandenberg 5 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── fully automatic. You use the 'SUBSCRIBE' and 'SIGNOFF' commands to join and leave a mailing list. Each mailing list can be configured to allow either public membership - where anyone can join, or restricted access - where a 'SUBSCRIBE' command is relayed to the list owner who may then authorize your subscription. Several commands are available to be used with the mailing list features; they are described later. Automatic File Sending (AFS) For some purposes, it is desirable to create an address that automatically sends files in response to any message sent to it. They are generally used to provide information about products and services. For example, sending a message to "vmail-info-request@vsystem.wimsey.bc.ca" will automatically retrieve a file containing a short blurb on V-MailServer. Copyright (c) 1993 Richard Vandenberg 6 ───────────────────────────── Message Processing _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ V-MailServer performs several different functions when processing e-mail messages. When first receiving a message, V-MailServer must decide whether it is addressed to a mailing list, an Automatic File Sending (AFS) address, or if it is a series of commands being issued to the mail server itself. After determining which function the message should be processed by, V-MailServer performs that task. All outgoing messages and files are placed in the QUEUE directory, for later processing by VMAILX. Below is a very simple diagram of V-MailServer message processing. ┌────────────────────────┐ │ Receive mail, │ │ Process header │ └───────────┬────────────┘ │ │ ┌────────────────────────┐ ├─│ Process mailing list ├──┐ │ │ │ │ │ └────────────────────────┘ │ │ │ │ ┌────────────────────────┐ │ ├─│ Process AFS request ├──│ │ │ │ │ │ └────────────────────────┘ │ │ │ ┌────────────────────────┐ │ └─│ Process mail server ├──│ ┌─│ commands │ │ │ └────────────────────────┘ │ │ │ │ ┌────────┴───────┐ └─────────────────────┤ Any additional │ Yes │ ACL commands │ └────────┬───────┘ No ┌────────┴───────┐ │ Finished │ │ Processing │ └────────────────┘ Copyright (c) 1993 Richard Vandenberg 7 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Process Description Header processing. V-MailServer determines the address to which the message applies by looking at the 'To:', 'Cc:' and 'Received:' headers. It first scans the message headers for a 'Received:' header with a 'for' address. This header is added by RMAIL whenever it delivers a message to its final destination. Failing that, the 'To:' and 'Cc:' addresses are compared against all mailing list and Automatic File Sending addresses. If the address doesn't match any of those addresses, the message is assumed to be a series of commands for the mail server, and is processed as such. Mailing list processing Processing a mailing list involves taking the body of the message and sending it to everyone on the mailing list. V-MailServer does more than simply resend the message, though. It strips unnecessary header information, sets up correct headers, such as 'Reply-To:', and then sends the message. Header control is managed through Header Conversion files, which are described later. V-MailServer can also be configured to execute a series of administrator-defined mail server commands after sending the messages. You may, for example, wish to inform submitters of a change in list operation. AFS processing Automatic File Sending (AFS) processing is very simple. Whenever any message is sent to an AFS address, a file is sent back in return. Header processing is also performed on these requests, as it is for everything else. Extra mail server commands can also be defined for these addresses. A good use would be to automatically add anyone who requests information to a mailing list. You can then use the mailing list to send out additional information later. Copyright (c) 1993 Richard Vandenberg 8 Message Processing ────────────────────────────────────────────────────────────────────── Mail server command processing Command processing involves reading each line of the message body and executing the commands in the order they are specified. An exception to this rule is if you have previously specified that your address is password-protected. In this case the entire message is scanned first to find a PASSWORD command. If one is not found, no processing will take place. Besides processing the commands, V-MailServer also creates a session transcript that shows how each command has been processed. That transcript is then mailed back to the user. Of course, this may be disabled if necessary. Access Control Language (ACL) commands During mailing list, AFS request or mail server processing, a series of additional commands may have been added for later processing. These ACL commands are used to perform specific tasks, such as automatically adding someone to a mailing list as mentioned above. Any regular mail server command may be executed, along with additional commands that affect the session transcript and other processing. The Access Control Language is still in its infancy, and will be expanded in later versions. Processing the Queued requests VMAIL will queue the requests in the QUEUE subdirectory. To pass these requests to the mailer to be delivered, you must run the VMAILX program. Each queued entry comprises two files - the data file and the execution file. The data files all have a file extension of '.D', while the execution files use '.X'. The execution files contain two lines - the 'D' line, which specifies the name of the data file, and the 'C' line which specifies the command line to use to process the given data file. Generally, the program specified in the 'D' line is either the one specified by the MAILPROGRAM configuration parameter, or the one specified by the QUEUEPROGRAM configuration parameter. These are usually RMAIL and VMAIL, respectively. If VMAIL detects a situation where not enough disk space is available to process a request, it will re-queue the request for later processing. The reason that is does this instead of exiting with an error code is to allow it to perform special processing in this situation. Copyright (c) 1993 Richard Vandenberg 9 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── When VMAIL re-queues the request, it loads in a special header conversion file, and executes an ACL script. These files are defined in the configuration parameters 'JustHeaderConversion' and 'QueueCommandFile'. The default script included in V-MailServer 2.2 sends a short message that says that the request has been placed in a "priority holding queue" for later processing. You can do anything you like with this script, perhaps even notifying an off-site administrator that disk space is low. To force this mode of operation, use the "-q" parameter when running VMAIL. VMAILX operates by taking each '.X' file in the QUEUE directory, opening the data file as the standard input, and executing the specified command line. Because the files in the QUEUE directory often will not appear in the order they were created, VMAILX reads the directory, sorts the files by the date and time they were created, and then processes them in that order. Currently, VMAILX can only load and sort 2000 requests. After the list of files has been processed, VMAILX will re-read the directory, and process up to 2000 more requests. This will continue until either all files have been processed, or the queue limit is reached. This is new in V-MailServer 2.2. There are a few cases where VMAILX will not process all the queued requests: If the mail program returns an error level other than 0. This indicates an error, and VMAILX will move on to the next file. However, the queued files are left intact. VMAIL re-queues the message, because disk space is too low. In this case, the '.X' file contains an extra parameter line - 'Q time-number'. The time that the file was re-queued is placed on the 'Q' line. VMAILX will check for this line, and if the time specified is later than the time VMAILX began operation, the file will be left for processing later. The queue limit specified on the command line is reached. To fine tune the processing function, VMAILX has several command line options available. They are described in detail on page 82. Briefly, the options allow you to process the requests based on file specification and to limit the number of bytes processed in a given session. You can, for example, process mailing list messages first, followed by file requests. This allows you to set priorities for the traffic in your particular situation. Copyright (c) 1993 Richard Vandenberg 10 Message Processing ────────────────────────────────────────────────────────────────────── Copyright (c) 1993 Richard Vandenberg 11 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Copyright (c) 1993 Richard Vandenberg 12 ───────────────────────────── File Server Commands _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ There are several commands for retrieving files, subscribing to mailing lists, obtaining help or other information. Below is a list of the commands, with descriptions of each. Basic File Server Commands These commands are used for accessing the basic file server features of V-MailServer. HELP Retrieves the help file. The name of help file is defined in the configuration file. See the configuration section on page 45 for details. INDEX [listname] Retrieves the master index list of available files. Again, this file is defined in the configuration file. See the configuration section on page 45 for details. If 'listname' is specified, the index file defined for that list is sent. See the 'Configuring Mailing Lists' section, page 62 for details. GET dir/filename [UUENCODE | XXENCODE] /GET dir/filename [UUENCODE | XXENCODE] SEND dir/filename [UUENCODE | XXENCODE] /PDGET dir/filename [UUENCODE | XXENCODE] Retrieve a file, optionally encoding using UU- or XX-encoding. These four commands are the most commonly used commands for requesting files. Depending on how the FILES area is configured, the user may need to specify a directory along with the filename - eg. "pc/info/inter31a.zip". UU- and XX- encoding can be specifically forced. Generally, UU-encoding is automatically performed. Deciding which files to encode is handled internally in Vmail.exe, and is controlled by the 'UU-MaxSize' and 'UU- EncodeSkip' configuration parameters. INFO [subject] Retrieves more detailed information on various subjects. INFO with no subject returns the INFO GENERAL information. The INFO command allows you to setup information files that are sent to the user upon request. For example, assume you are selling a product, and you wish to provide product information and pricing. You can create a set of files in the INFO directory Copyright (c) 1993 Richard Vandenberg 13 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── to maintain this information. The name you give the files is the same as the subject of the INFO command. For example the command "INFO prices" would retrieve the 'prices' file. INFO subjects may be up to 11 characters long. The filename uses the first 8 characters of the subject for the filename itself, and the last three characters for the file extension. For example, "INFO EXPANSION" would use the file "EXPANSIO.N". The INFO command uses a directory defined in the configuration file. See the configuration section on page 45 for details. Advanced File Server Commands PW ADD password CHANGE oldpassword newpassword DEL oldpassword This command allows the user to add, change, or remove a password from their account. If a password is enabled, V-MailServer will not allow access to the file server unless a PASSWORD command is included anywhere in the message. PASSWORD password If a password has been added to an account, the user must give the PASSWORD command before any others will be processed, including the PW command. Note that the PW and PASSWORD commands are not echoed in the session transcript, for security reasons. Basic Mailing List Commands These commands are used for accessing the basic mailing list features of V-MailServer. SUBSCRIBE MailingList [Subscriber's Real Name] Adds a user to the specified mailing list. If the list does not exist, he/she will receive a message to that effect in the session transcript. New in V-MailServer is the ability for the subscriber to add his or her real name. This is optional, of course. Copyright (c) 1993 Richard Vandenberg 14 File Server Commands ────────────────────────────────────────────────────────────────────── UNSUBSCRIBE MailingListName SIGNOFF MailingListName Removes the user's name from the specified public mailing list. REVIEW MailingListName Retrieves a list of all the members of a mailing list. Members who wish to hide themselves from the REVIEW command may do so with the "OPTION . . . REVIEW" command, described in the next section. Advanced Mailing List Commands ECHOMAIL MailListName This command causes all mail sent to the specified mailing list to be echoed back to the sender. Normally the default is to send the message to everyone except the sender. An option can be set for each mailing list that will determine whether echoes default to on or off for new subscribers. NOECHOMAIL MailListName Turns off the mail echoing feature for the given mailing list. Copyright (c) 1993 Richard Vandenberg 15 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── OPTION List-Name List-Option Value The OPTION command allows the user to set several options for the specified mailing list. ALIAS Return-Address The 'ALIAS' option allows the user to change the address V-MailServer sends the mailing list to. For example, if the user wishes to receive a mailing list to a mailbox other that subscribed to the list with, this option can change the address. Example: OPTION vmail-l ALIAS My-New-Address@some.site Note that this command only changes the address to which the message is sent, not the subscriber's original address. NAME Real-Name This option allows the subscriber to change the name that appears in the REVIEW listing. Example: OPTION test-l NAME Rick (the Boss) Vandenberg REPLY ON | OFF Many mailing lists are set up to have the 'Reply-To:' header set to the mailing list address. The user may turn this off if he/she wishes. Example: OPTION test-l REPLY OFF Note that this command will not have any effect if a 'Reply-To:' address is added using a Header Conversion 'UPDATE' command. Instead, use the 'REPLACE' command for 'Reply-To:' headers. Copyright (c) 1993 Richard Vandenberg 16 File Server Commands ────────────────────────────────────────────────────────────────────── REVIEW ON | OFF This option allows a member of a mailing list to remove their address and name from the REVIEW listing. Many people don't want others to know they read certain newsgroups or mailing lists. This command gives them the freedom to be anonymous. Of course, if they post, they won't be anonymous any longer, but that is by their choice. Administrative Commands FOR address [ENDFOR|FORRESET] This is one command that will find more use by the administrator than anyone else. It allows the user to specify that the following commands are to be used against the specified address. All file server commands will send files to the specified FOR address. Mailing list commands such as 'SUBSCRIBE' and 'SIGNOFF' will use the given address as well. This allows the administrator to change options for users by sending commands to the mail server. V-MailServer uses an internal address called the 'recipient'. This address is generally the address in the incoming 'From:' header, unless overridden by a 'Reply-To:'. The recipient address is the one to which all messages and files are sent. The only exceptions to this are for mailing lists, where the applicable commands use the original 'From:' address, without checking for a 'Reply-To:'. The 'FOR' command simply changes this recipient address to the one specified. The ENDFOR command (or FORRESET) will reset the recipient address to its original value. Whether are not you use this depends on whether the session transcript should be mailed to the original address or to the newly-defined recipient. LISTOPTION List-Name LIST|FILES Global-Option Value This command may only be used by the mailing list owner. It allows the administrator to set any global mailing list option. For more details about global mailing list options, see the Configuring Mailing Lists section. Copyright (c) 1993 Richard Vandenberg 17 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── OPTION List-Name ADDRESS SINGLE | MULTI Many mailing lists will address messages to more than one subscriber to reduce the volume of mail. If a site cannot handle multiple 'To:' addresses, the 'OPTION List-name ADDRESS SINGLE' command will disable this for the user, causing a singly-addressed message to be sent. This has been made an administrative command, as the list owner would be the one to receive any bounced messages. OPTION List-Name POST YES | NO This command is for mailing list owners only, and enables or disables the user's ability to post. For example, if you want to lock out a user - for whatever reason - use these commands: FOR A_N_Noying@somesite.com OPTION list-name POST NO Miscellaneous Commands /*, */ COMMENT, END-COMMENT These commands allow you to add comments to the session transcript delivered to the user. They are useful when used with the 'FOR' command, to add explanatory text. For example: /* Joe, I'm sending the file you requested. Let me know if you have any questions. Rick */ FOR Joe@somesite.com GET VMS200.ZIP XXENCODE The 'COMMENT' and '/*' commands are interchangeable, as are 'END-COMMENT' and '*/'. The lines containing the comment commands themselves are not included in the session transcript. Copyright (c) 1993 Richard Vandenberg 18 ───────────────────────────── General Information _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Configurable Messages V-MailServer uses administrator-configurable file server messages. These messages are used in the session transcript that is sent back to the requester. The messages are read in from files in the WORDS subdirectory. Below is a list of the files and where they are used. The name of the directory is specified with the Words-Path configuration parameter. ALIAS.TXT This message is used whenever a filename is aliased to another name. LISTJOIN.TXT The message sent when a 'SUBSCRIBE' command is successful. REJECT.TXT This file is sent whenever a user's request has been rejected. SCRIPT.PRE Makes up the header of the session transcript. SCRIPT.END The footer of the session transcript. SEND.TXT This file is added after each successful SEND command. SHORT.HLP This file is added to the session transcript if an invalid command is sent to the mail server. UNSUBFAI.TXT This file is added if an 'UNSUBSCRIBE' command failed. It is used to provide a short explanation of why the command might have failed. Other message files are included in the WORDS directory, but are not used in the creation of the session transcript. HELP.TXT The standard help file, sent in response to the 'HELP' command. QUEUE.WAI This message is referenced by the ACL script QUEUE.ACL. This file does not need to be used, and is provided simply as an example. A semi-colon (;) as the first character in a line is used to signify a comment line. These lines are not included in the session transcript. Copyright (c) 1993 Richard Vandenberg 19 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Macros Macros are used in the configurable messages to allow the administrator to include variable information in the messages. They operate much like a form-letter in a word processor, in that text is substituted for the variable in the final output. The macros may also be used in the ACL scripts. Variables are delimited by percent signs. Example: %File-Size%. Case of the variable name is not significant. Look at the supplied files in the WORDS subdirectory for examples. A list of each variable and its description follows. Global Macros The global macros may be used in any file, ACL script, or header conversion file, without restriction. They do not rely on any information that is specific to the command being processed, or other functions being performed. Date The current time in yyyy-mm-dd format. Header-Date Date string in the format: Day, dd Mon yy hh:mm:ss ZZZ. This macro uses the current time to create the string. Header-From The value of the 'From:' header in the incoming message. Header-Reply-To The value of the 'Reply-To:' header in the incoming message. MailGrade The UUCP grade parameter that will be given on the RMAIL command line, if applicable. MailOptions The value of the configuration parameter 'MailProgramOptions'. OwnerID The name of the mail server administrator, as entered in the configuration file. ReceivedID The temporary filename used to process the current outgoing message. This macro is used when adding a 'Received:' header in a header conversion file. It may be used anywhere, but probably has little use for other situations. Copyright (c) 1993 Richard Vandenberg 20 General Information ────────────────────────────────────────────────────────────────────── Recipient The requester's address, accounting for having a 'Reply-To:' header or a FOR command being used. Server-Name The address of the mail server. Eg. 'mail- server@vsystem.wimsey.bc.ca'. This address is taken from the MailServerName configuration parameter. TempFile A unique filename that can be used for whatever purpose you choose. This macro can be used in ACL scripts for whatever purpose you need a unique filename for. Time The current time in hh:mm:ss format. The hours use the 24-hour format. Macros specifically for the configurable messages Some macros are only available for use in the configurable message files. File-Requested The name of the file being requested. This only valid in SEND.TXT. File-Sections The number of mail sections that were queued to satisfy the request. File-Size The size of the original file, before any encoding. File-Size-UU The size of the requested file, after encoding. Queue-Count The number of '*.X' files in the queue directory, before processing the current requests. This is only useful in SCRIPT.PRE Queue-File-Count The number of queued file-request messages (VQ*.X) Queue-Mail-Count The number of queued mailing list messages being redistributed. (VM*.X). This is only useful in SCRIPT.PRE Queue-Queue-Count The number of queued requests that have not yet been processed. (VJ*.X). This is only useful in SCRIPT.PRE Copyright (c) 1993 Richard Vandenberg 21 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Queue-Status-Count The number of queued session transcripts. (VS*.X). This is only useful in SCRIPT.PRE Total-File-Sections The total number of mail sections sent to satisfy all the requests for this message. This is valid in SCRIPT.END. Total-File-Size The total number of bytes of requests sent. This is valid in SCRIPT.END. Total-File-Size-UU The total number of bytes (after encoding) of requests sent. This is valid in SCRIPT.END. Command-specific macros The macros are set if the specified command is executed. If an ACL script is executed while processing the specified command, then the macro may be used in the ACL script. Command-Filename The filename given on the command line, as it was given, for a User-Defined command. The macro assumes the command format: command [optional-password] filename other- arguments . . . Command-Line The command line given for processing in the incoming message, not including the actual command name. Set for User-Defined commands Legal-Path The full, validated filename given for a User- Defined command. If the filename cannot be validated, the legal-path variable returns an empty string. The macro assumes the command format: command [optional-password] filename other- arguments . . . Copyright (c) 1993 Richard Vandenberg 22 General Information ────────────────────────────────────────────────────────────────────── MList-Name The name of the mailing list referred to in the current SUBSCRIBE command or when a message is sent a mailing list. This macro is used in LISTJOIN.TXT, and can be used in ACL scripts also. Orig-Name The original file name used in the current command, before being converted by the filename aliasing functions. The macro assumes the command format: command [optional-password] filename other- arguments . . . New-Name The new file name, after being modified by the file aliasing functions. The macro assumes the command format: command [optional-password] filename other- arguments . . . Rest The remainder of the User-Defined command, after the filename. The macro assumes the command format: command [optional-password] filename other- arguments . . . Special Macro Functions: Several specialized macro functions are built into V-MailServer. For instance, there is one which allows you to access individual entries in mailing list option files. Listed below is the syntax for each macro. Type: Mailing list option entries Syntax: %/LIST[delimiter]list-name[delimiter]Flag[delimiter]Address[delimiter] option-name/% This macro allows you to access any entry in any defined mail option file. You specify the list name, the flag ('G' or 'X'), the address, and the option name. The [delimiter] in the syntax above is any single, unique character. It is defined as the first character after 'LIST', and must remain the same for each delimiter position. If the Copyright (c) 1993 Richard Vandenberg 23 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── specified entry is not found, an empty string ("") is returned. Note that this macro uses "%/" and "/%" to mark the beginning and end, instead of single ampersands. This allows you to nest another macro inside of it. Examples: %/LIST?vmail-l?G?LIST?address/% Returns the value SINGLE, or MULTI. %/LIST?test-l?X?%recipient%?alias/% Returns the alias of the recipient, if one exists. %/LIST?test-l?X?%recipient%?name/% Returns the name of the recipient, if one exists. Copyright (c) 1993 Richard Vandenberg 24 General Information ────────────────────────────────────────────────────────────────────── Type: Command parameters Syntax: %PARMn% This macro allows you to select any parameter from the current command given to the mail server. %PARM0% is the actual command name. %PARM1% is the next parameter, and so on. If the specified parameter does not exist, the macro returns an empty string (""). The parameters are parsed by using the space and tab characters as delimiters, just as they are for MSDOS batch files. There is no limit to the number of parameters you may have for user-defined command. Examples: (Using the command "RESEND PKZ204C.EXE 2 UUENCODE") %PARM0% . Returns the actual command itself - "RESEND". %PARM3% Returns "2". Type: File Security & conversion of a filename to a full, legal path Syntax: %/LEGAL:filename/% This macro takes the given filename, or partial path, and attempts to find a legal, accessible file. It will look first in the public file directories, and then in directories accessible to members of specific mailing lists. If the file cannot be accessed, either because it does not exist, or because the file security does not allow it, an empty string ("") will be returned. This macro uses the extended delimiters '%/' and '/%', to allow another macro to be used as the filename. Examples: %/LEGAL:%PARM3%/% Returns the full, legal name of the file specified in parameter 3 of the current command. Copyright (c) 1993 Richard Vandenberg 25 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Header Conversion V-MailServer provides a facility to add, modify or remove any header in the mail files. The headers can also be sorted in any order. This is managed with Header Conversion files. These files give V-MailServer instructions on what to do with each header. The header conversion command syntax is as follows: ADD HeaderName NewHeaderInformation This command adds a new header to the mail file. It does not overwrite an existing header of the same name. ORDER HeaderName This command is used to tell V-MailServer what order to put the headers in. Use multiple 'ORDER' commands and list all the headers to specifically order. The rest are added after these. Headers will be created in the order that the ORDER commands are listed. REPLACE HeaderName NewHeaderInformation This command changes an existing header, it will not add a new one if it does not exist. STRIP HeaderName This command tells V-MailServer to remove the specified header from the mail file. UPDATE HeaderName NewHeaderInformation This command changes an existing header, or adds a new header if one does not exist. Capitalization of the header names is not significant. However, in the interests of form, they should be capitalized in the most common way. This makes them stand out a little better. Copyright (c) 1993 Richard Vandenberg 26 General Information ────────────────────────────────────────────────────────────────────── Two examples of header conversion files are shown below. The first header conversion file is for use in generating "new" messages. ie, session transcripts and file requests. By default, V-MailServer passes all incoming headers through to the outgoing messages. This is fine for mailing lists, but unnecessary headers must be removed when sending files or other messages. UPDATE Reply-to: MailServer@vsystem.wimsey.bc.ca UPDATE Precedence: bulk ; ; ; Strip EVERYTHING ; STRIP * ; ; ; Order the headers. Any not listed will be added after the ; ordered headers ; ORDER From ORDER Received: ORDER Date: ORDER From: ORDER Subject: ORDER Sender: ORDER To: ORDER Cc: ORDER Message-ID: ORDER Reply-To: ORDER Organization: ORDER In-Reply-To: ORDER Precedence: This file will create mail messages that contain 'Reply-To: Mail-Server@vsystem.wimsey.bc.ca'. It will remove any unnecessary headers as well. The second header conversion example is one that might be used for mailing list processing. For this type of work, most headers should be passed through, without any modification. Note that lines should not wrap in the actual file; they only wrap here to fit the page. ; Let's use a different 'Sender:' address. This one looks like an ; "Internet" mailing list. REPLACE Sender: TEST-L-relay@%InsNode% Copyright (c) 1993 Richard Vandenberg 27 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── ; ; Set the precedence to 'bulk'. This is a sendmail parameter. UPDATE Precedence: bulk ; ; ; Eliminate some unwanted headers ; STRIP x-mailserver: ; ; Let's add a line to show that V-MailServer processed the ; message. ADD X-Our-Header: V-MailServer 2.2 processed this! /occ=-1 /line=0 ADD X-Our-Header: id %ReceivedID%; %header-date% /occ=-1 /line=1 ; ; Order the headers. Any not listed will be added after the ordered ; headers ; ORDER From ORDER Received: ORDER Date: ORDER From: ORDER Subject: ORDER Sender: ORDER To: ORDER Cc: ORDER Message-ID: ORDER Reply-To: ORDER Organization: ORDER In-Reply-To: ORDER Precedence: Occurrences and Line numbers In the example above, you may have noticed the "/occ" and "/line" parameters on the added Received: header. A discussion of the internal workings of the header conversion functions is needed. When the headers from a message are initially loaded, they are assigned occurrence numbers and line numbers. Each instance of a header is counted an occurrence. If the header has only one line, it is given line number 0. If it is a multi-line header, such as 'Received:', it may have several line numbers assigned to it, with a single occurrence number. Repeating headers, like 'Received:', have a different occurrence number for each repetition. When creating the outgoing message, V-MailServer groups the individual header lines together by header name, and by occurrence number. Multi-line headers are put together in line number order. Copyright (c) 1993 Richard Vandenberg 28 General Information ────────────────────────────────────────────────────────────────────── The "/occ=" parameter allows you to specify an occurrence number to perform the command on, while the "/line=" parameter lets you work on a specific line from a multi-line header. Each header conversion command assumes certain things about repeating and/or multi-line headers. The STRIP command, when used without a "/occ" or "/line" parameter, removes all the specified headers that have an occurrence number of 0 or greater. This lets you do things like the following: ADD Received: by vsystem.com (V-MailServer 2.2) /occ=-1 /line=0 ADD Received: id %ReceivedID%; %header-date% /occ=-1 /line=1 STRIP Received: Notice that the new 'Received:' header is added with an occurrence number of -1. The STRIP command, as it is used, will not remove this header. The ADD command adds headers using occurrence number 0 and line number 0 as a default. This only works for single-line headers. To add multi-line headers, you must specify a different line number for each line. In the previous example, the "/occ=-1" is used for two reasons. The first is to ensure that the STRIP command won't remove the header. The second is to force this header to precede any existing 'Received:' headers. If you want to add a new header, and have it precede any existing ones of the same name, use a negative occurrence number. If you want the new header to come after any existing ones of the same name, use a large positive occurrence number. A good value would be 30 or 40. Too large a value will slow V-MailServer processing slightly, because it loops through the headers, starting at the lowest occurrence number on through to the highest. The UPDATE command is used to replace an existing header, or add a new one if it does not exist. Again, the defaults for both occurrence and line number are 0. However, the UPDATE command is much like a combination of STRIP and ADD. It will remove any headers with the same name, that have an occurrence number greater than or equal to 0. The REPLACE command works the same as UPDATE, except that the header must previously exist. If it does not, nothing is added. Using line and occurrence numbers with any command except ADD is not recommended. The reason is the occurrence numbers are incremented for each incoming header, and will vary from message to message. For this reason, it is not reliable to refer to a specific header and occurrence number. In one message, the 'To:' header may have an occurrence number of 5, while in the next it may be 15. It depends on its placement within the headers. Copyright (c) 1993 Richard Vandenberg 29 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Notes about Header Conversions Using the header conversion facility provides you with great power to control the output of V-MailServer. With such power comes the need to use great caution. Before making changes to the default files supplied with V-MailServer, you should familiarize yourself with the applicable RFCs (Requests for Comments). The most important RFCs with respect to e-mail headers are: 822 Crocker, D. Standard for the format of ARPA Internet text messages. 1982 August 13; 47 p. (Format: TXT=109200 bytes) (Obsoletes RFC 733) 1123 Braden, R.T.,ed. Requirements for Internet hosts - application and support. 1989 October; 98 p. (Format: TXT=245503 bytes) 1049 Sirbu, M.A. Content-type header field for Internet messages. 1988 March; 8 p. (Format: TXT=18923 bytes) Other interesting RFCs: 1341 Borenstein, N.; Freed, N. MIME (Multipurpose Internet Mail Extensions) Mechanisms for Specifying and Describing the Format of Internet Message Bodies. 1992 June; 80 p. (Format: TXT=211117 PS=347082 bytes) 1342 Moore, K. Representation of Non-ASCII Text in Internet Message Headers. 1992 June; 7 p. (Format: TXT=15846 bytes) 1343 Borenstein, N. A User Agent Configuration Mechanism For Multimedia Mail Format Information. 1992 June; 10 p. (Format: TXT=29296 PS=59978 bytes) 1344 Borenstein, N. Implications of MIME for Internet Mail Gateways. 1992 June; 9 p. (Format: TXT=25873 PS=51812 bytes) Note the difference between From and From:. The From header is the envelope From line. eg.- From geo.org!SBODY Wed Aug 5 04:26:22 1992 remote from van-bc The From: header is the address of who sent the mail. eg.- From: Rick@vsystem.wimsey.bc.ca Copyright (c) 1993 Richard Vandenberg 30 General Information ────────────────────────────────────────────────────────────────────── Note that an 'Received:' header is always added to the mail. Multiple Header Conversion Files A default header conversion file is supplied that will handle many situations. For mailing lists, however, it is useful to have different headers. For example, you may operate a mailing list where you wish to not have a 'Reply-To:' header, or you might want to change the default 'Sender:' address. There are many cases where you might wish to change the headers. For these reasons, V-MailServer provides you with the ability to name a header conversion file to use. You can set this up on a per-mailing list basis also. Details on how to do this are in the Mailing list section. Copyright (c) 1993 Richard Vandenberg 31 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Access Control Language V-MailServer can process additional commands when it processes mail. The commands are contained in script files that may be loaded at the following times: Default commands each time any mail is processed When requesting a specific file When submitting a message to a mailing list When processing an AFS request When processing a User-Defined command Uses for ACL scripts include: Notifying people that about mail server operations Automatically subscribing people to a mailing list if they request a certain file Notifying people about changes in a mailing list format Sending more than one file as an AFS request Creating new commands The commands are structured as a very simple script language. We've coined the acronym ACL - Access Control Language. ACL is not nearly as powerful as it could be, but will be expanded over time. Note that you may mix both ACL commands and regular mail server commands together in scripts. Example: IF NOT MEMBER list-exec SUBSCRIBE list-regular General ACL Operation ACL commands are loaded into a Command Stack that is executed after V-MailServer has finished processing its current set of requests. Most commands are internal, and are processed by the ACL Preprocessor. The remainder are sent to the regular command processor for execution. Below is a simple chart that will hopefully outline the general operation: Copyright (c) 1993 Richard Vandenberg 32 General Information ────────────────────────────────────────────────────────────────────── ACL Flow of Operation Step Normal Command Processor (NCP) ACL Preprocessor (ACLP) 1 Original mail message is processed 2 An ACL routine begin to be executed 3 ACL passes a command to the NCP 4 Command is processed ( eg. file request, mailing list subscription, etc ) 5 ACL resumes processing commands 6 Commands continue to be processed via the NCP and ACLP. When using ACL, you can use all the general macro variables, on any line. Before each line is executed, the macro is evaluated. Command syntax CLEAR Commands This command is handled by the ACL Preprocessor. It clears any prior commands from the Command Stack. This command is useful if you have a set of default commands defined, and you wish to skip those commands and execute only the ones currently being loaded. This command erases all commands currently loaded, so use it only as the first line of an ACL routine. CLEAR Extra-Commands Accessing a file that has an ACL routine linked to it will cause those ACL commands to be executed after the mail message has been processed. If you need to disable this, CLEAR Extra-Commands will do it for you. It is used in the VIEW and EXTRACT User-Defined commands, because they are just looking at parts of files, not retrieving the file itself. Copyright (c) 1993 Richard Vandenberg 33 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── ECHO OFF|ON|EXPAND|text The ECHO command is used much like the MSDOS batch language equivalent. Using ECHO ON will cause all commands to be echoed to the screen. ECHO OFF will turn off the display. ECHO EXPAND is the same as ECHO ON, but expands any macros before displaying the command. ECHO followed by anything else will display the text. GOTO label Jumps to the specified label in the :label script. Label definitions must begin with a colon (:). This feature acts just like the MSDOS batch language command of the same name. GRADE g Sets the UUCP grade to 'g' if this is applicable. This allows you to control the grade depending upon the request. IF [NOT] Condition Command The IF command is used to conditionally execute other commands. The conditions are defined below. IF [NOT] EXIST filename Checks for existence of the specified file. The filename given must be the fully qualified name, as it is not parsed via the file aliasing or file security functions. This commands acts in the same fashion as the equivalent MSDOS batch language command. IF [NOT] MEMBER Listname If requester belongs to the specified mailing list or not. IF [NOT] MATCHADDRESS address1 address2 Compares two addresses, from right to left ( reverse ), up to the number of characters in the shortest address. The comparison is not case-sensitive. If either address is empty, IF MATCHADDRESS is false. If both are empty, it is true. This command allows you to compare either full addresses, or portions of the domain. It does not account for variations in addressing formats. Examples (assuming the command IF MATCHADDRESS): Copyright (c) 1993 Richard Vandenberg 34 General Information ────────────────────────────────────────────────────────────────────── rick@vsystem.com .com - True xyz.com!rick rick@xyz.com - False rick@XYZ.COM RICK@xyz.com - True rick@xyz.com @xyz.com - True REINDEX list-name This command allows you to reindex a mailing list. This is necessary if you make manual changes to either the membership or option files of the list. REQSTAT ON | OFF | NONE This command allows you to control the information in the session transcript message, or turn the message off completely. If set OFF, command processing is not acknowledged in the message. If set ON, the normal acknowledgement is included. If REQSTAT NONE is used, the session transcript message is not sent. SENDTEXT FileName The SENDTEXT command allows you to send text files. No security checking is performed, to allow you to send information files without including them in the regular file areas. UUencoding is NOT performed, so only specify text files. Message variables are allowed. For an example, see the QUEUE.WAI file, which sends a message anytime a request is queued for later processing. No information is recorded in the session transcript by this command, so REQSTAT is not needed to eliminate it. SHELL DOS-Command [arguments] Shell to DOS and execute the specified command. This is a very often used to run batch files. SUBJECT [New Subject] This command changes the subject line. You would probably use this command just before you send a file with either SEND or SENDTEXT. TRANSTEXT line of text Add the line of text to the session transcript, with a newline character at the end Copyright (c) 1993 Richard Vandenberg 35 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── TRANSTEXTC line of text Add the line of text to the session transcript, without a trailing newline character. This allows you to create a single line in the transcript, with multiple TRANSTEXTC commands. Notes about SHELL: SHELL loads a copy of the command shell (COMMAND.COM, 4DOS, etc), and passes it the given command line. If you are running a batch file, be aware of the way MSDOS handles parameters. When passing parameters to most executable programs, if a string is enclosed in double quotes, it is handled as a single parameter. When passing a string to a batch file, each parameter is delimited by a space. Enclosure with quotes has no effect. If you use a macro in the SHELL command line, it may expand into a string, with spaces included. An example is if you extract a user's name from a mailing list. Example: SHELL programA.exe "This is a test" ; one parameter SHELL batchB.BAT "This is a test" ; four parameters This may require you to perform some complicated batch-file programming in certain cases. Just be aware of the differences, and you can work around any obstacles. Copyright (c) 1993 Richard Vandenberg 36 General Information ────────────────────────────────────────────────────────────────────── ACL Examples # Turn off the request status for now. We do this because otherwise # the ACL commands are echoed in the session transcript. ReqStat OFF # Now subscribe the person to the mailing list. You would replace ListName # with your specific mailing list. subscribe ListName # This line sets the subject to be used in the next SEND command. subject V-MailServer 1.22 Notes # Send the named file to the requester. This file name must still pass all # the usual security checks. send \public\notices\vms122.not # Turn the request status back on ReqStat ON 1. This ACL script will automatically subscribe to a mailing list anyone who requests information from an AFS address. Copyright (c) 1993 Richard Vandenberg 37 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── # Command file to perform a text search of data files # reqstat off # # the following line is wrapped for display only. It # should be typed on one line. shell fgrep /%Command-Line%/ d:\public\data\*.dat > d:\public\results.txt shell pkzip -m d:\public\results.txt d:\public\results.zip subject Search Results reqstat on send \public\results.zip shell del d:\public\results.zip # # 2. Command file to perform a text search of data files. VIEW ACL Command file: shell c:\waffle\dev\srch.bat %LEGAL-PATH% clear extra-commands Subject Archive Contents send \public\ftp\results shell del d:\public\ftp\results SRCH.BAT rem Batch file to retrieve contents of an archive rem Called by VMAIL, via SHELL command if %1. == . goto end fv %1 > d:\public\ftp\results :end 3. ACL routine to create VIEW command Copyright (c) 1993 Richard Vandenberg 38 ───────────────────────────── User-Defined Commands _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ A User-Defined Command (UDC) is a mail server command that executes an ACL script. They are defined by the administrator to handle special mail server functions. Two examples are provided in this release - EXTRACT and VIEW. The format of a UDC to be processed is: Command [Password] [Filename] [Optional arguments] eg. EXTRACT VMS200.ZIP README The UDCs are configured in the UDCFILE. The format of this file is shown below. Note that the lines to not wrap in the actual file. ; Command Command-file password userid VIEW c:\vms\udc\search.cmd * * EXTRACT c:\vms\udc\extract.cmd * * VMAIL-GET c:\vms\udc\vmailget.cmd ABcDefgHu! rick@vsystem.wimsey.bc.ca UDCs may be defined to have a password, or to be used by only a specific address. If either does not apply, substitute an asterisk (*) for the field. The ACL commands loaded when processing a User-Defined Command are executed immediately, instead of at the end of processing as with the default script. Copyright (c) 1993 Richard Vandenberg 39 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Copyright (c) 1993 Richard Vandenberg 40 ───────────────────────────── Installation _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Before installing V-MailServer, you should plan your configuration. V-MailServer has many features and you may or may not need them all. Descriptions of all the configuration file options starts on page 45. Most of the terminology in this manual is directed toward installing V-MailServer with Waffle. However, V-MailServer is designed to be installed with any MSDOS UUCP system. If you are using UUPC, see the section "Using V-MailServer with UUPC," page 93. If you use any other packages, and are having any trouble installing V-MailServer, please contact us. We'll be glad to help you. Information on how to contact us is listed in the SUPPORT.DOC file. Planning the configuration V-MailServer can provide mail server, mailing list, and automatic file server capabilities. You must perform the basic configuration described below. After that you can set up any options you need. If you are upgrading from a previous version of V-MailServer, you should install this version to a different directory. After the installation finishes, modify the necessary VMS.CFG parameters to suit your needs. You may also need to modify the master mailing lists file and the master AFS file to include the new options available in the version. Basic Configuration The VINSTALL program can completely install V-MailServer, and setup example mail list and automatic file server features. Before running VINSTALL, you must unarchive the V-MailServer files using the PKUNZIP "-d" option. This will create several subdirectories that contain the V-MailServer installation source files. Installation Steps 1. To begin the installation, run the VINSTALL program. The first screen you will see is a warning that VINSTALL will overwrite any pre-existing files. Press 'C' if you wish to continue the installation procedure. 2. The next step is to fill in the pertinent information in the fields provided. VINSTALL uses this information to fill in fields in the installation source files. This will let you install V-MailServer with without needing to modify the many files it uses. 3. After filling in all the fields, VINSTALL will create the installation directories, and install all the files. Copyright (c) 1993 Richard Vandenberg 41 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── 4. There are a number of entries in the VMS.CFG file that may need to be changed, depending on your system configuration. They are outlined below: RmailLineMax - This entry allows multiple addresses in outgoing mailing list messages. You should leave it set at 0, until after you are comfortable with the operation of V-MailServer. UUEProg - This parameter specifies the uuencoding program to be used with V-MailServer. We suggest using Richard Marks' programs, as they provide services to split encoded files into multiple parts. If you use another program, you will need to modify the other uuencoding options also. The current release of Richard Marks' uuencoding/decoding software is called UUEXE515.ZIP, and is widely available. IndexFile - This specifies the name of the master index file, which is sent in response to the INDEX command. You will probably need to change this entry. DailyLimit and MessageLimit - These are the maximum number of bytes that a user may request, per day and per message. Change these to suit your needs. Minimum-Free-Disk - You may have multiple entries for this parameter. When VMAIL.EXE is executed, it checks the amount of free disk space against these entries. If not enough exists, the message is simply re-queued for later processing. You should set the appropriate entries to require enough disk space to hold any encoded files that may be requested. The formula for this is: The DailyLimit or largest available file, whichever is larger; multiplied by 2.5. This gives you the maximum amount of space any encoded files will need. You should then add the size of the help and index files, and then add approximately 25-50% for "slack". If you are running on a network, make sure that each drive specified in a Minimum-Free-Disk parameter is actually available. If the drive is not available, V-MailServer will treat the drive as if it doesn't have enough disk space. Drives C:, D:, E:, and F: are specified in VMS.CFG after the installation. You will need to modify these to suit your installation. Copyright (c) 1993 Richard Vandenberg 42 Installation ────────────────────────────────────────────────────────────────────── Mail-Spool-Drive - The mail spool drive, where outgoing messages are placed by the MTA (usually RMAIL). VMAILX uses this parameter to check for free disk space before calling the MTA (Message Transfer Agent). Not all MTA programs return an MSDOS errorlevel code when there is an error spooling the message. This parameter allows VMAILX to avoid calling the MTA when disk space is low. Minimum-Free-Spool - The number of bytes needed on the spool drive for VMAILX to process the queued requests. To-Format - This parameter takes ones of the two values "Same" or "Separate". "Same" causes all 'To:' addresses to appear on one line, while "Separate" folds the addresses onto separate lines. "Same" goes against recommendations made by RFC 822 regarding folding long lines, but is used to work around a bug in Waffle 1.65's RMAIL program. 5. You should create an environment variable 'VMS', which points to the configuration file. For example: SET VMS=C:\WAFFLE\VMS\VMS.CFG It's a good idea to add this line to your AUTOEXEC.BAT file, or to the batch file that starts up you mail system. VINSTALL will create a small batch file, VSET.BAT that contains the correct SET command for this. 6. You will now need to add a few lines to your 'aliases' file. Assuming you want to use the name 'mail-server' for access to V-MailServer, add this line to your 'aliases' file: mail-server | c:\waffle\vms\vmail.exe Again, after running VINSTALL, the file ALIASES.ADD contains the alias entries that are needed. 7. If you are upgrading from any previous version of V-MailServer, you'll need to modify the mailing lists slightly. See the 'Configuring Mailing Lists' section on page 59. 8. After completing any changes to the mailing lists, you will need to create the index entries in the membership file. The user- defined command REINDEX-LIST is provided that will do this automatically. The "TEST\REINDEX" file contains a sample message file containing a REINDEX-LIST command for 'test-l' and 'secure- l'. Add additional REINDEX-LIST commands as required, for all the lists that have been configured. Copyright (c) 1993 Richard Vandenberg 43 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── 9. The "VINFO -i" command will display the configuration of the mail server, and is useful for spotting areas which haven't been configured correctly. That completes the initial installation of V-MailServer. A number of sample mailing lists and AFS addresses have also been included. Modifications to other files, setting up Mailing Lists and Automatic File Sending addresses are covered in the configuration sections that follow. Copyright (c) 1993 Richard Vandenberg 44 ───────────────────────────── Configuration File _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ The VMS.CFG file is the main configuration file for V-MailServer. It contains parameters that set mail delivery options, file encoding, traffic logging, file and path information, addresses used in various header fields, and other information. The following parameters are used in the configuration file: Mail Delivery Parameters MailProgram The MTA (Message Transfer Agent) of your choice. Generally, it is RMAIL. You should specify the full path to it. MailProgramOptions If the MTA you are using requires other command line options, they may be listed here. GradeOption The grade option is the command line parameter used to control the grade when executing the mail program. For example, in Waffle 1.65's RMAIL, the option is -g. The actual grade parameter is not passed here. It is set in the mailing list, AFS request and other configuration files. RmailLineMax Used to specify the maximum length of the MAILPROGRAM command line. To use multiple-addressing in mailing lists, you must set this parameter greater that 0. A good figure is around 120. The maximum size for an MSDOS command line is 128 characters. Mail Addressing Parameters UUCPFrom Used to specify the UUCP From envelope line in the resulting mail files. Note that this line is different than the 'From:' header line, and that is should not include the node portion of your site. Node The node name of your site. It's used in various places in the system, notably the 'Message-Id:' header. Copyright (c) 1993 Richard Vandenberg 45 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── ServerName The name of the server, for use in the 'From:' field in the header. SenderName The name used in the header fields 'Sender:', and on the UUCP 'From ' path line. The SENDERNAME should be different from the SERVERNAME, so that bounce messages and the like are not sent back to the mail server address. To-Format This parameter takes ones of the two values "Same" or "Separate". "Same" causes all 'To:' addresses to appear on one line, while "Separate" folds the addresses onto separate lines. "Same" goes against recommendations made by RFC 822 regarding folding long lines, but is used to work around a bug in Waffle 1.65's RMAIL program. Owner-ID The Owner ID is used to identify the owner of the mail server. Any important status messages, such as security violations, are mailed to this address. Encoding parameters UUEProg The UU-encoding program. It should be able to place it's output into one or more files. UUEncodeOptions The option string to pass to the UUencode program specified above. These options are always passed, no matter which encoding method is chosen. UUEncode_Switch and XXEncode_Switch The UUEncode program's command line switches to enable UUencoding or XXencoding. The appropriate option is passed based on which Copyright (c) 1993 Richard Vandenberg 46 Configuration File ────────────────────────────────────────────────────────────────────── encoding option the request specifies. UUEncoding is the default. UUETemp The name of the output file for the UUencoder. Most UUDecoders will create multipart files, based on a prefix that you supply. If, for example, with Richard Marks' UUEncode program you supply the name C:\TEMP\VSRUX, the output files will be named in the following fashion: C:\TEMP\VSRUX1.UUE, C:\TEMP\VSRUX2.UUE, C:\TEMP\VSRUX3.UUE, and so on. Make sure that UUETemp points to a drive that has enough free disk space to hold all the encoded parts for the largest file available. UUEOutputSpec Used for multi-part Encoded requests. Most UUencoders will create multiple files for multi-part encodes. They should have simple format that they use to name the multiple files. Richard Mark's Uuencode will number the files sequentially, for example. Eg. VSRUUE1.UUE, VSRUUE2.UUE and so on. In this case, using VSRUUE*.UUE will find all the Encoded sections. After the file has been Encoded, V-MailServer will use the UUEOUTPUTSPEC as a search pattern to find the file(s) to send. UU-EncodeSkip This parameter allows you to choose the list of extension to skip encoding for. List each extension, separated by a period (.). For example: "UU-EncodeSkip .TXT.DOC.INF..". The two period at the end of the example represent files with no extension. All files with extensions not in this list are encoded. UU-MaxSize UU-MaxSize allows you to specify the maximum size a file may be before encoding is forced. Any file that is longer than the limit specified here will be encoded, regardless of the UU-EncodeSkip parameter. Copyright (c) 1993 Richard Vandenberg 47 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Files and Paths Parameters TempDir The name of the directory used to store temporary files. Examples are C:\TEMP and E:\. If you have a large RAM drive, make this your temporary directory. PasswordFile The name of the file that contains the password information. HelpFile The fully qualified name of the file to send in response to the 'HELP' command. IndexFile The fully qualified name of the file to send in response to the 'INDEX' command. ValidPaths Contains the directory names of all the valid directories that may be accessed via V-MailServer requests. It is used for security. More information about the VALIDPATHS file is in the section 'Configuring File Server Services'. SearchTree Contains the names of all the directories to search when requesting a file. When a file is requested, each of the paths listed in the SEARCHTREE file is used to form the full path specification of the file to be retrieved. More information about the SEARCHTREE file is in the section 'Configuring File Server Services'. Copyright (c) 1993 Richard Vandenberg 48 Configuration File ────────────────────────────────────────────────────────────────────── LogFile The name of the V-MailServer request log. Each request is logged in this file, along with the date, time, requester. LogType The LOGTYPE parameter allows you to select whether you want the message headers and/or message body included in the V-MailServer log file. To include the headers, place the keyword 'Headers' on the parameter line. To include the body, use 'Body'. To include the full message, just place both keywords on the line. Example: LogType Headers Body RejectFile Contains the addresses of any users or domains to disallow V-MailServer access for. Specifying a partial domain will disallow access to ALL users in that domain. New to V-MailServer 2.2 is the ability to specifically enable access to users or groups of users, as well as disabling. InfoPath The path to look in for file used by the INFO command. The subject of the INFO command may be up to 11 characters long. The INFO command simply retrieves the file with the same name as the subject of the INFO command. TrafficControl The file used to monitor traffic. UserDirFile Contains the address and the user directory for any people who you have set up a user directory for. UserSecurityFile Contains the legal user directories a user may access. Copyright (c) 1993 Richard Vandenberg 49 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── DailyLimit Allows you to limit the volume of requests from a user on a daily basis. Any requests which would create more traffic than this will be rejected. MessageLimit Allows you to limit the volume of requests from a user on a message basis. Any requests which would create more traffic than this will be rejected. AllowFirstRequest Is a flag that controls how V-MailServer will process the first request of the day. Say you have a daily limit of 100,000 bytes. You also have a number of files on your system that are larger than this. If ALLOWFIRSTREQUEST is 1, V-MailServer will allow a request for a very large file, but only if it the first request of the day. In this way you can allow access to large files without having high daily limits. AFSFile The list of addresses and the file to send in response to a message. MailingLists The "master" mailing list file, which contains the names of all the mailing lists and the files that contain each one, including the option file name. QueueDir The name of the directory that contains the files that are queued to be mailed. QueueLimitFile The QueueLimitFile is a file that holds totals used by the limit option of VMAILX. It will be automatically created if necessary. Copyright (c) 1993 Richard Vandenberg 50 Configuration File ────────────────────────────────────────────────────────────────────── Seqf Used to hold an integer used in creating temporary files. FileAlias The name of the file containing filename aliases and ACL script to execute. See the File Aliasing section for more details. HeaderConversion The name of the default header conversion file. JustHeaderConversion The name of the header conversion file to use when just queuing requests. QueueProgram The name of the program used in the .X file for queued request. Generally it's VMAIL.EXE. CommandFile The name of the default ACL script used whenever a request is processed by V-MailServer. QueueCommandFile The name of the script used whenever a request is queued for later processing. Minimum-Free-Disk drive space Used to determine the minimum free disk space required to process a command. If the free space is less than that specified, the request is queued for later processing. More than one of these parameters is permitted, to allow more than one drive to be checked. If this is the case, all specified drives must meet the minimum requirement before processing takes place. Copyright (c) 1993 Richard Vandenberg 51 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Mail-Spool-Drive The mail spool drive, where outgoing messages are placed by the MTA (usually RMAIL). VMAILX uses this parameter to check for free disk space before calling the MTA (Message Transfer Agent). Not all MTA programs return an MSDOS errorlevel code when there is an error spooling the message. This parameter allows VMAILX to avoid calling the MTA when disk space is low. Minimum-Free-Spool The number of bytes needed on the spool drive for VMAILX to process the queued requests. Words-Path The Words-Path parameter specifies the directory that contains the message files that are sent for various reasons. See the Configurable Messages section for more details. KillFile Specifies the name of the Kill file. See the Kill File section for more details. UDCFile Specifies the file used to handle custom commands. Obsolete Configuration Parameters The following parameters are obsolete, and should be removed from the configuration file. StatusWorkFile A temporary file for holding the 'status' message while it is being created during the execution of the request. Obsoleted because the filename is dynamically chosen at run-time. Copyright (c) 1993 Richard Vandenberg 52 Configuration File ────────────────────────────────────────────────────────────────────── TempMailFile The temporary file used when creating any mail. You can choose any name that suits you. If you have a RAM disk or other directory that is used for temporary files you should use that. Eg. - E:\VMTEMP or C:\TEMP\TEMPMAIL. Note: in V-MailServer 2.2 all temporary files are assigned a unique name. This parameter is no longer required. FileType The program specified here is used to determine whether or not to encode a file before sending it. It is generally CHKUUE. Obsoleted because encoding determination is now built into V-MailServer. Copyright (c) 1993 Richard Vandenberg 53 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Copyright (c) 1993 Richard Vandenberg 54 ───────────────────────────── Configuring File Server Services _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ In order to use V-MailServer as a mail based file server, you will need to tell V-MailServer where to look for the files, and which directories are valid. V-MailServer can be set up to access any drive or directory available. Two files are needed to use the File Server features. One is called the SEARCHTREE file. It's a list of directories to search for files. The other is the VALIDPATHS file. This file must list the full subdirectory name for each subdirectory that can be accessed. You will also need to provide a UUencoder program. UUEncode by Richard Marks is recommended, but you may use any UUencode program you wish. We chose Richard Marks' program because it will create multi- part encoded files, which V-MailServer needs to send large files. Setting up the SearchTree and ValidPaths files These two files control access to all files that may be retrieved using the GET (or equivalent) command. In order for V-MailServer to find a file, it must know where to look. It does this by using the Searchtree file. Here is a sample Searchtree file: c:\public d:\extra d:\misc If a GET command is processed - eg. 'GET xyz.zip' - V-MailServer will search for that file in each directory listed in the Searchtree file. It does this search by taking one of the directories listed, and appending the requested filename to it to create a full path to the file. The Validpaths files contains a list of all legal directories that may be accessed. Taking the above example, if the three directories were the only ones you wanted to have available you would simply put the following in the Validpaths file: c:\public d:\extra d:\misc By default, VINSTALL sets up the ValidPaths file to give access to the entire subdirectory structure under the named public files directories. Simply delete any lines that you wish to disable access to. For a more complex example, assume that you have the following directory structures. On drive 'c:' we want the 'pc' and 'misc' Copyright (c) 1993 Richard Vandenberg 55 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── subdirectories to be available. The '\other\private\share' subdirectory on drive 'd:' should not be accessible, but those below it should be. Let's also say that we want users to request files using the convention 'dir1/dir2/name' - IE. pc/asm/filename or misc/xyz. c:\public └───ftp ├───pc │ ├───asm │ └───c └───misc d:\other └───private └───share └───pc └───asm The first step is to have V-MailServer start off with the correct directories when searching. In the Searchtree file, put these lines: c:\public\ftp d:\other\private\share In the Validpaths file, you must name all of the valid paths: c:\public\ftp\pc c:\public\ftp\pc\asm c:\public\ftp\pc\c c:\public\ftp\misc d:\other\private\share\pc d:\other\private\share\pc\asm If a request has just the filename, V-MailServer will first try 'c:\public\ftp\filename', which will fail because this path is not listed in the Validpaths file. Then it will try 'd:\other\private\share\filename', which will fail for the same reason. If a request uses 'pc/asm/filename' for example, V-MailServer first tries c:\public\ftp\pc\asm\filename. It is a legal path, so it will attempt to find the file. If it doesn't exist, the next attempt uses 'd:\other\private\share\pc\asm\filename'. Copyright (c) 1993 Richard Vandenberg 56 Configuring File Server Services ────────────────────────────────────────────────────────────────────── V-MailServer will accept any legal MSDOS file specification. These include filename \filename c:filename c:\filename ..\filename .\filename c:..\dir11\dir2\dir3\..\dir4\filename and others. Each file specification is converted to a fully-qualified path name, which is then compared to the paths listed in the Validpaths file. Header Conversions There are two Header Conversion parameters specified in VMS.CFG - HeaderConversion (the default) and JustHeaderConversion (for queued messages). The default also handles headers for AFS requests. These two files are quite different from the Header Conversion files used for mailing lists. For normal mail server and AFS requests, the resulting messages are considered to have originated from the mail server. Therefore, it is permissible to remove any and all headers from the original message. This is vastly different from a mailing list, where almost all headers should remain intact. For this reason, the two conversion files supplied have a very large number of 'STRIP' commands. The idea is to remove every non-essential header. Of particular importance are the commands to remove the 'Content-Type:' and other MIME-related headers, as the message being queued is not in MIME format. Copyright (c) 1993 Richard Vandenberg 57 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Copyright (c) 1993 Richard Vandenberg 58 ───────────────────────────── Configuring Mailing Lists _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Mailing lists provide a mechanism to make group communication easier. People with a common interest can join a mailing list dedicated to specific topics. Members can subscribe and unsubscribe to the list at their option. Any message sent to the mailing list address is automatically forwarded to all members on the list. Each mailing list has two files associated with it - a membership file that contains the mail addresses of all subscribers, and an option file that contains all the list options. In addition, there is one master file that contains the name of each mailing list and the full filename of the files that contains the membership and option information. ┌───────────────────┐ ┌───────────────────┐ │ Master mailing ├───────┬─┤ Membership file │ │ list file ├──┐ │ │ │ └───────────────────┘ │ │ └───────────────────┘ │ │ ┌───────────────────┐ │ └─┤ Option File │ │ │ │ │ └───────────────────┘ │ │ └─────> Other mailing list files Master Mailing list file To set up a mailing list you must first create a master mailing list file. The name of this file is defined by the MAILINGLISTS parameter in the VMS.CFG file. This file is the master list of all mailing lists residing on your machine. Following the name of each mailing list is the name of the file that contains the membership information. Following that is the name of the option file. There is sample master file called 'mailmast' this is supplied with V-MailServer. You should modify this file to suit your needs. The format of each line is: mailing-list-name Membership-File-Name Option-File-Name Example: (Note that the line does not wrap in the actual file) test-l c:\uupc\vms\mail\test-l\test-l.mbr c:\uupc\vms\mail\test-l\test-l.opt Copyright (c) 1993 Richard Vandenberg 59 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Membership Files Membership information is maintained in a file, with one address per line. In addition there are a few options in the general membership file. The membership file is a simple ASCII file, with a single character flag followed by the address of the subscriber. Following the address is a 200 character string of hexadecimal numbers, which are the index entries into the option file. eg - TVMAIL-L V-MailServer Issues List Rvmail-l@vsystem.wimsey.bc.ca Ic:\user\vmail-l\vmail.int 1rick@vsystem.wimsey.bc.ca 0SomeOldID@some.other.site FFFFFFFF000001A8...... 1AnActiveName@abusy.site FFFFFFFF000001B9...... 2Somebody@else.UUCP FFFFFFFF000002A8...... The flag values are as follows: 0 - Old member that UNSUBSCRIBEd from the list 1 - Active members, echo disabled 2 - Active members, echo enabled There are also 'header' flags: T - The title of the mailing list. Used in the 'Sender:' line, and as a title for the REVIEW command. R - The full 'Reply-To:' address for the mailing list. If this line is defined, the given address is used in the Reply-To: field. Otherwise the address the original message was sent to is used. I - The name of the introduction file to send when people subscribe to the list. This file is very useful for providing an initial orientation to new subscribers. Suggestions for content include what the list is about, where to send submissions, and how to signoff the list. An example introduction file is supplied with V-MailServer. You may have any number of introduction files. To use more than one, simply use multiple 'I' lines. M - The address of the moderator. All incoming mail will be sent to the moderator. Only mail addressed from the moderator will be forwarded to the members. Copyright (c) 1993 Richard Vandenberg 60 Configuring Mailing Lists ────────────────────────────────────────────────────────────────────── O - Address of the owner of the list. The owner will receive messages regarding new subscriptions, sign-offs, and other information. If 'Authorized-Subscription' is enabled, the owner will receive the request. See below for more details. Note: The 'R' and 'T' options above are overridden by functions in the Option files and/or header control files. Option files Each mailing list has an option file. This file is used to hold all the list options and any options set by or for a user's address. Each line of the option file consists of a one character flag, the user's address, the name of the option and the option value. Each field is delimited by a space or tab, with the exception of the flag, which is proceeded immediately by the user's address. Two special addresses are used for options pertaining to the list as a whole - LIST and FILES. The flag field is used to determine whether the option applies globally or if it's a user option, or if the record is marked as deleted. Flag Values 'G' - Global list options 'X' - User list options 'Z' - Deleted record. The space will be re-used if possible. Global Options Global options always use 'G' for the flag, and either "LIST" or "FILES" for the address. For example: GLIST Reply-to: V-MailServer Issues List All options use the address "LIST", except for the "ROOT-" and "Valid-Path-" options, which use "FILES". Any global option may be set using the 'LISTOPTION' mail server command, described in the File Server section, under Administrative Commands. Copyright (c) 1993 Richard Vandenberg 61 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── The explanation of each option follows: Authorized-Subscription Authorized subscription relays a subscription request to the mail owner, along with instructions on what commands to send to the server to subscribe someone to the mailing list. The requester also gets a message sent back informing him that his request has been forwarded to the list owner. Valid values are YES and NO. Command Allows you to specify a script to execute after queuing the outgoing messages. Perhaps you want to send a message to submitters that says "Your message has been distributed to TEST-L". You can do this with an ACL script. Echomail This may be set to YES or NO, to set the default ECHOMAIL mode for new subscribers. Grade Allows you to set the UUCP grade for this list. This would let you prioritize different mailing lists. Your mail delivery program must be capable of grading requests for this option to work. Specify a single letter with this option. HeaderConversion This option specifies the Header Conversion file to use for outgoing messages from this list. Index The full path of the index file defined for the list. This file is sent in response to the command "INDEX list". Non-Member-Posting Allows you to set whether or not a submitter must be joined to the list before posting to it. This option is set to either YES or NO. Reject-Command-File Allows you to specify a script to execute if the message is rejected because Non-Member-Posting is set OFF. Copyright (c) 1993 Richard Vandenberg 62 Configuring Mailing Lists ────────────────────────────────────────────────────────────────────── You can send instructions on how to join the mailing list with this. Reply-To: The Reply-To: option is used to set the Reply-To: header in the outgoing messages. Restricted-Posting Disables the ability to post to the list except for those members who have the POST option set to YES. See the User Options section for details on the POST option. Valid values are YES and NO. Restricted-Reject-File Specifies a file to send to the user if posting is disabled for that user. Restricted-Reject-Subject Sets the subject for the message sent with the Restricted-Reject-File. Review ON|OFF Enables and disables the REVIEW command for the mailing list. The default is 'ON', if the entry does not exist. The mailing list owner can always use this command, regardless of this setting. ROOT-x The ROOT- option specifies the initial directory for file access. The file areas specified using this option and "Valid-Path-" are used to provide file access based on being a member of a mailing list. The 'x' in the option represents an integer used to differentiate multiple "ROOT-" options. eg.- GFILES ROOT-1 C:\PUBLIC GFILES ROOT-2 D:\USR\SPOOL Note: Numeric extensions must be contiguous; that is, they must begin at 1, and there may be none missing. They may be listed in any order, however. Sender: The Sender: option sets the Sender: header to the specified value. Copyright (c) 1993 Richard Vandenberg 63 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Valid-Path-x The list of legal paths for file access. The 'x' in the option represents an integer used to differentiate multiple "Valid-Path-" options. eg.- GFILES Valid-Path-1 C:\PUBLIC\FTP GFILES Valid-Path-2 C:\PUBLIC\PC GFILES Valid-Path-3 C:\USR\SPOOL\Z Note: Numeric extensions must be contiguous; that is, they must begin at 1, and there may be none missing. They may be listed in any order, however. User Options A number of user options have been defined for use in the option files. All user options use the flag 'X'. Address SINGLE|MULTI Informs V-MailServer that mail to this address by be sent singly. This only takes effect when Multiple addressing is enabled for the list. It is used to eliminate problems with sending mail with multiple address to sites that cannot handle mail in that fashion. This entry is set by the OPTION mail server command. Alias new-address If a user needs mail sent to a different address from the one subscribed with, this option will tell V-MailServer the new address to address the message to. It is set with the OPTION mail server command. Name user's-real-name The user's real name. It is added when subscribing to a mailing list, or by using the OPTION mail server command. The value of this entry is displayed in the REVIEW listing. Post YES|NO To specifically allow or disallow posting to a mailing list by a user. If the global option 'Restricted-Posting' is set to 'YES', members must have this entry set to 'YES' to post. In other cases, set it to 'NO' to disable posting Copyright (c) 1993 Richard Vandenberg 64 Configuring Mailing Lists ────────────────────────────────────────────────────────────────────── for that user. It is set with the OPTION mail server command, but may only be used by the mailing list owner. Reply ON|OFF Enables and disables the inclusion of the Reply-To: header in the messages sent to the user. Normally, Reply-To: points back to the mailing list. In some cases, however, users may wish to reply back to the poster of the message. This entry is set by the OPTION command. Be aware, of course, that if you force a Reply-To: header with a Header Control command, this entry will have no effect. Review ON|OFF Enables and disables the display of the user's address and name in the REVIEW command. The default it 'OFF', if the entry does not exist. It is set with the OPTION mail server command. Subdate yyyymmdd This is simply an informational entry that contains the user's subscription date. Making manual changes Because the mailing list files are in text format, it is possible to make manual changes to the files. However, if you do, you must reindex the mailing list. A User-Defined Command - 'REINDEX-LIST' is provided to make this easy. Header Conversions There are two Header Conversion parameters specified in VMS.CFG - HeaderConversion (the default) and JustHeaderConversion (for queued messages). The default also handles headers for AFS requests. These two files are quite different from the Header Conversion files used for mailing lists. For normal mail server and AFS requests, the resulting messages are considered to have originated from the mail server. Therefore, it is permissible to remove any and all headers from the original message. This is vastly different from a mailing list, where almost all headers should remain intact. For this reason, each mailing list may be set to use its own Header Conversion file. Copyright (c) 1993 Richard Vandenberg 65 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── In particular, MIME and Content-* headers should never be removed from the message. In addition, the Received: headers should not be removed either. Mailing List Owner Messages The mailing list owner will receive a number of messages that relate to the operation of the mailing list. These messages are generally informational only - subscription and signoff requests. Some may require intervention of the mailing list owner - when a signoff fails, for instance, or when Authorized-Subscription is enabled for the mailing list. The various messages are detailed below. Subscription requests Subscription request for list SOME-LIST for SOME-ADDRESS. Requested by ORIGINAL-FROM-ADDRESS. This message tell the mailing list administrator that someone has used the SUBSCRIBE (or equivalent) command to join a mailing list. The list "Requested by ORIGINAL-FROM-ADDRESS" is only added if the address added to the list is not the same as the From: address in the header. This could happen if someone uses the FOR command to subscribe a new user. Example: Some headers . . . From: jim@xyz.com FOR User@some.other.site.com SUBSCRIBE test-l This request will generate this message to the mailing list owner: Subscription request for list test-l for User@some.other.site.com. Requested by jim@xyz.com. Copyright (c) 1993 Richard Vandenberg 66 Configuring Mailing Lists ────────────────────────────────────────────────────────────────────── Authorized-Subscription Requests When the mailing list option 'Authorized-Subscription' is set to 'YES', the following text is append to the mailing list owner's Subscription message: Send a message to the mail server with the following commands: FOR SOME-ADDRESS SUBSCRIBE SOME-LIST The following text is added to the session transcript for Authorized-Subscription requests: Your request for a subscription to the SOME-LIST mailing list has been sent to the list administrator - LIST-OWNER - for approval. Signoff Requests Signoff requests are sent to the mailing list owner whenever someone attempts to signoff from a list. They are formatted much like the subscription requests: SIGNOFF request for list SOME-LIST for SOME-ADDRESS. Requested by ORIGINAL-FROM-ADDRESS. One additional line - "NOT Successful!" - is appended in the case where V-MailServer cannot find the requester's address in the associated membership file. This can happen if the user changes addresses, or if the headers are modified during message delivery. In this case, manual intervention is necessary. Copyright (c) 1993 Richard Vandenberg 67 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Mailing List Administration Mailing list administration is not a very difficult task, but may be time-consuming for some large lists. The most important issue for any "secure" list is to ensure that a password is used with the mail owner's address. This is handled with the "PW ADD some-password" mail server command. This will prevent someone for using the LISTOPTION and other secure commands, even if they forge the list owner's address. Another issue is one in which an ALIAS has been set for a list address. This does not change the address needed to signoff a mailing list, only the address to which mail is sent. You will need to be aware of both of addresses if a signoff request fails. The REVIEW command always works for the mailing list owner, even if the Global Option "REVIEW" is set "OFF". Other administration issues are discussed in RFC 1211 - "Problems with the Maintenance of Large Lists", by A. Westine and J. Postel. RFC 1211 is available by ftp, from nic.ddn.mil, or by mail server request from the V-MailServer support system. See the SUPPORT.DOC for instructions on how to access our mail server. Off-Site Mailing List Administration In some cases, the mailing list administrator may be located at a different site from where V-MailServer is being used. For these situations, the following commands are very useful - FOR, LISTOPTION, OPTION, PASSWORD, REVIEW, SIGNOFF, SUBSCRIBE. See the File Server Commands section for more details. Of course, they can be used on- site also, but sometimes it's easier to use a text editor on the files when the list is administered locally. Copyright (c) 1993 Richard Vandenberg 68 ───────────────────────────── Configuring Automatic File Sending Services _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ For some purposes, it is desirable to create a address that automatically sends files in response to a message sent to it. For example, sending a message to vmail-info-request@vsystem.wimsey.bc.ca will automatically retrieve a file containing a short blurb on V-MailServer. V-MailServer 2.2 enhances this functionality by allowing an ACL script to be executed in response to a message to an AFS address. AFS is implemented using a file that contains, one per line, an address followed by the name of the file to send. Following the file name to send is another filename that specifies an ACL script to execute. Each of these fields is optional, and if it is not used, it should be filled with an asterisk ('*'). One extra field follows these - the subject for the outgoing message. The default is "Information Request". Do not use an asterisk for this field. Each time a message is processed through V-MailServer, the master AFS file is checked to see if the mail is addressed to an AFS address. If so, the corresponding file is queued, and/or the ACL script is executed. The master AFS file is defined by the configuration parameter AFSFILE, and is usually called 'AFSMAST'. Example AFSFILE: ; This file contains the list of AFS address to which V-MailServer ; will send the specified file and/or execute the specified script. ; ; Format: ; ; AFS-address File-to-send Command-file-to-execute Subject ; ; If there is file to send, only an ACL file to execute, use an ; asterisk in the File-to-send field. ; ; Here's the sample ( note lines in the actual file do not wrap ) ; sample-info-request c:\vms\afs\sample c:\vms\afs\sample.acl ; Bad-server-address is one that automatically sends a message ; to often-used, incorrect mail server addresses. ; bad-server-address c:\vms\afs\badserv c:\vms\afs\badserv.acl Invalid Address ; An example of an ACL-only address ; test-l-request * c:\vms\afs\testlreq.acl Copyright (c) 1993 Richard Vandenberg 69 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Copyright (c) 1993 Richard Vandenberg 70 ───────────────────────────── Controlling Access with a Reject File _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ The reject file allows you to enable or disable access to the file server features, based on who is making the request. For example, you may wish to disable access for people who cause trouble, all users at a particular site, or even an entire domain. Or you may want to disable access for everyone, except those to whom you specifically give access. Setting up the reject file is simply a matter of entering any addresses you wish in enable or disable access for. One word of caution, though - V-MailServer 2.2 does not do any address transformations. For example, it treats "rick@vsystem.com" and "vsystem.com!Rick" as two separate addresses. V-MailServer 1.22 used a slightly different format for the reject file. It was not possible to specifically allow access to users; the reject file was used only for disabling access. V-MailServer 2.2 will use an existing reject file, but in "reject-only" mode. To use it to it's fullest potential, you must tell V-MailServer to use the new format. To do this, make sure there is a line that begins with "#!VMS200". This informs V-MailServer that the entries following this line use the new format. The format of the reject file is given below, along with some examples of processing certain addresses. A semicolon (;) or number sign (#), in column one, is used to indicate a comment line. address - old address format - reject addresses only address2 #!VMS200 - Tag to declare remaining entries use the new format Aaddress - "A" declares accept Raddress - "R" declares reject Pattern matching occurs from right to left, and matches the right-most portion of an address. The algorithm also makes a 'best-fit' when matching; ie - it finds the longest address which matches the incoming address. Then it rejects or accepts the message, depending on what mode is used. Copyright (c) 1993 Richard Vandenberg 71 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Example: (Note that the old "reject-only" format is used until the line "#!VMS200") * - reject everybody (!) jerk@some.site.com - rejects only this address @some.site.com - rejects everyone at this site .subdomain.com - reject entire subdomain, but not users @site.com site.com - reject any address with site.com on the right NOTE !!! This format is dangerous, in this messages from anysite.com will also be rejected. The match is done strictly on the number of characters in the entry, and doesn't check if the site name matches exactly. #!VMS200 - specify that the remaining entries are the new format A* - Accept everyone Rjerk@some.site.com - reject the trouble-maker Another method, to allow only specific users to have access. #!VMS200 R* - reject everyone, for a start ARick@vsystem.com - allow Rick access AOwner@your.site.com - allow access to yourself A.edu - allow access to entire .edu domain Rbad.site.edu - except this site Copyright (c) 1993 Richard Vandenberg 72 ───────────────────────────── Controlling Access with Passwords _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ One of the potential problems with an automated mail server is abuse. While not very common, it is possible to forge a 'From:' address, and execute mail server commands on someone else's behalf. Someone could, for instance, request files for a hundred other users, or forge the mail server owner's address and execute protected commands. To help combat that, users may define passwords. When a password is defined, no commands may be executed unless the 'PASSWORD' command is given somewhere in the message. It is very important that the administrator define a password for him/herself, as should all mailing list owners. The administrator has access to the 'LISTOPTION' command, and certain 'OPTION' subcommands that should not be accessed by the public. Mailing list owners can always execute 'REVIEW' for their lists, even if the 'REVIEW' command is disabled for the list. The passwords are stored in a file defined in the configuration parameter 'PasswordFile'. The default filename is 'PASSWORD.DAT'. The structure of the password file is: struct PASSWORDRECORD { char id[80]; time_t datetime; char password[20]; }; Copyright (c) 1993 Richard Vandenberg 73 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Copyright (c) 1993 Richard Vandenberg 74 ───────────────────────────── Kill File _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ The Kill file allows the administrator to disable processing for messages that meet criteria based on the existence or value of header lines. Using the Kill file is instrumental in eliminating bounce loops in mailing lists. The format of the lines in the file is: Search-Type Header-Name Value SearchType may be either 'EXACT' or 'CONTAINS'. The Header-Name is the name of the header. Value is the string to search for. If a value is not given, the message is killed if it contains the header, period. Fields are separated by spaces or tabs. Case is not significant for any of the fields. Examples: CONTAINS Comment: Vacation Droid EXACT From: Mailer-Daemon@troublesome.site.com The Kill file is very useful in eliminating mail loops caused by other sites. Some vacation daemons, in particular, cause a great deal of grief with mailing lists, as they don't create a typical bounce message. Instead of responding back to the 'Sender:' address or the envelope, they respond to the 'Reply-To:' address, which may be the mailing list. When a message is killed, no response is sent back to the originator. However, the entire message is written to the log file. Copyright (c) 1993 Richard Vandenberg 75 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Copyright (c) 1993 Richard Vandenberg 76 ───────────────────────────── Traffic Monitoring _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ The Traffic Control file maintains a record of all outgoing V-MailServer messages. All file and AFS requests or logged, as well as all mailing list activity. The traffic file is used for two purposes - rate limiting, and for generating statistics. For rate limiting, the traffic file is scanned before a message is processed, and any applicable traffic control entries are totalled to determine if the request should be accepted or not. For generating statistics, the 'VINFO' program is supplied. See the section on 'VINFO', page 90, for more details. Two utility programs are supplied to remove old traffic records and create a comma-delimited format file of the traffic information. The two programs (KILLTRAF and TRAF2CDF) are documented in the 'Additional Programs' section, Page 87. Copyright (c) 1993 Richard Vandenberg 77 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Copyright (c) 1993 Richard Vandenberg 78 ───────────────────────────── Monitoring Operation _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Monitoring operation is a very important part of administering a mail server. Users will occasionally send incorrect commands, or perhaps try to get around the server security. To aid you in this, all commands are logged to the VMSLOG file, including the address of the requester and the date and time of the request. You may also tell V-MailServer to copy the headers, body, or both to the log file. Use the 'LogType' configuration parameter to do this. See page 49 for details on the 'LogType' parameter. Copyright (c) 1993 Richard Vandenberg 79 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Copyright (c) 1993 Richard Vandenberg 80 ───────────────────────────── Command Line Options _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ V-MailServer has a number of command line options. They are listed below, along with the options for the utilities that are supplied with V-MailServer. VMAIL Options -c Configuration File Allows you to specify an alternative configuration file to that specified in the VMS environment variable. -d, -x level Debug mode. -d turns on basic debugging, while -x allows you to enter a debugging level. Debugging displays all kinds of useless information, and the level has little bearing on what information is display. Try values between 1 and 20 and see what happens. -f FileName Use the supplied file instead of reading from the standard input. -t ToAddress Force V-MailServer to use the specified 'To:' address instead of the one in the header. -q Force V-MailServer to queue the message. At one time, this allowed you to have the message queued for later processing, if you were running VMAIL.EXE from within a mail user agent (like Waffle, or UUPC's mail program). This eliminated the waiting period while VMAIL processed large mailing lists. The VMEXEC program included with this distribution is better suited for this. If you don't use it, however, you should use the -q parameter when running VMAIL from the MUA. Copyright (c) 1993 Richard Vandenberg 81 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── VMAILX Options -c Configuration File Allows you to specify an alternative configuration file to that specified in the VMS environment variable. -d Debug mode. -s FileSpec Process only those queued requests that match the given file specification. You must use '.X' as the extension. For example, VMAILX -s VS*.X will process all the status messages that are queued. -l limit Only process requests up to the specified limit. The total number of bytes processed is held in the QueueLimitFile. VMAILX will defer processing any queued files that would cause the limit to be exceeded. You must periodically use the -r option to erase the QueueLimitFile, or manually delete it. Using the limit option may cause the files to be sent in the wrong order, because any that are too large are bypassed, and smaller ones sent. VMAILX will not process any requests larger than the limit specified. If you need to flush the queue, either specify an abnormally large limit, or do not use the limit function one time to process all queue requests. -n Don't check the amount of free disk space before processing each request. If you have lots of free space, use this option to speed up processing -r Reset (erase) the QueueLimitFile before processing the queued items. Copyright (c) 1993 Richard Vandenberg 82 Command Line Options ────────────────────────────────────────────────────────────────────── A few examples: VMAILX will process all the queued requests ( flush the queue ). VMAILX -r Flush the queue, and reset the QueueLimitFile VMAILX -l 600000 Process a maximum of 600000 bytes of queued requests VMAILX -l 600000 -r Process a maximum of 600000 bytes of queued requests, but reset the QueueLimitFile before starting. VMAILX -s VS*.X Process only the status messages. Copyright (c) 1993 Richard Vandenberg 83 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Copyright (c) 1993 Richard Vandenberg 84 ───────────────────────────── Private User Directories _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ UserDir File and UserSecurity File Before any user may have access to the private mailing list features, a user directory must be set up. Two files are used to control user access to other directories - the UserDir file and the UserSecurity file. These two files are used for the same purposes as the SearchTree and ValidPaths files. In the UserDir file, you specify the user's 'home' directory. In the UserSecurityFile you specify the legal paths that a user may access. You may give partial domain names in both of these files. Private Mailing List Files Private mailing lists are set up at the discretion of the system administrator. Files and mailing lists may be manipulated in user directories assigned to specific users. This type of functionality is useful for providing information or files to a private group of people. A brief summary of these commands: PUT - send a file to a user directory CREATELIST - create a mailing list file RESENDLIST - resend a file using a mailing list FILES - retrieve the list of files in a user directory KILL - erase a file in a user directory Note: This functionality will most likely be removed in future versions. It may or may not be replaced. Please remember this if you are planning to use it. Copyright (c) 1993 Richard Vandenberg 85 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Copyright (c) 1993 Richard Vandenberg 86 ───────────────────────────── Additional Programs _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ DIGEST The digest program is provided to allow you to create a mailing list digest. Digest takes a Unix-, Waffle-, or UUPC-style mailbox file and creates a digest file, which may then be mailed. Command Line format: DIGEST [-p parameter file] [-v] [-n] [-i IncludeFile] [input] [output] [-t 0|1|2] All parameters are optional. The default parameter file is DIGEST.INF, in the current directory. The default input file is DIGEST.IN, in the same directory as the parameter file. The default output file is DIGEST.OUT, in the same directory as the parameter file. If the file DIGEST.PRE exists in the same directory as the parameter file, it will be included in the digest, between the list of Today's Topics and the top of the digest. This file is used to hold pertinent information, like how to obtain files from the mail server. This file may also be explicitly specified using the '-i' parameter. The parameter file will be renamed with a .BAK extension, and an updated version will replace it after each run. The '-v' parameter will change the output filename to Volume.Issue format. The file will be created in the same directory as the original output file. If you use this option, and also specify an output path, make sure that the path either ends with a backslash (\), or something resembling a filename (eg *). DIGEST will strip of the file name portion of the path, and replace it with the Volume.Issue filename. If the output path ends with a subdirectory name, it will be stripped instead, and the output file will end up in the wrong directory. The '-n' parameter disables the headers in the output file. The '-t' option allows you to modify how DIGEST detects the beginning of a new message. Using '-t0' (the default), DIGEST will split messages when it finds either a series of Control-As or the string "From " at the beginning of a line. '-t1' uses just the Control-As, and '-t2' uses just "From ". For Waffle or UUPC mail files, '-t1' will probably give the best performance. Copyright (c) 1993 Richard Vandenberg 87 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── The DIGEST parameter file contains the following information: List Name leave out the word "digest" Host the host where the digest lives From who sends the digest out To who the list is sent to Volume Volume nn : Issue nnn Date Day, dd Mon yyyy hh:mm:ss ZZZ Example: Vmail-l vsystem.wimsey.bc.ca Rick Vandenberg <vmail-l-admin@vsystem.wimsey.bc.ca> VMail-l-digest@vsystem.wimsey.bc.ca Volume 1 : Issue 3 Mon, 04 Jan 1992 22:00:23 GMT The "From" line must contain a valid RFC 822 mail address. The issue number must start at 0; it is incremented BEFORE generating each digest. Volume numbers must be incremented by manually. The parameter file is modified by the program after generation of each digest. The original version is renamed with the ".bak" file extension. The input file should contain a set of mail messages in the format of a UNIX, Waffle, or UUPC mailbox. These messages will be read into memory, and a list of "Today's Topics" generated from the subject lines. The messages will then be sorted so that all the messages on the same topic come out together in the digest. All messages that have "Administrivia" as the first word in the subject line are guaranteed to come out first in the digest. The digest will be placed in the output file. The default file name is "digest.out", in the same directory as the parameter file. To mail the output file you can use either of the following commands: RMAIL address < digest.out VMAIL < digest.out Copyright (c) 1993 Richard Vandenberg 88 Additional Programs ────────────────────────────────────────────────────────────────────── There is one problem with the sorting of messages by subject line to group by topic. DIGEST eliminates "Re:" strings, but if someone changes the subject, the new messages will be grouped separately. Examples: DIGEST This runs the DIGEST program with all necessary files in the current directory. The input file defaults to "digest.in", the output file to "digest.out", the parameter file to "digest.inf". DIGEST -v -p c:\user\list\digest.inf c:\user\list\mailbox.f d:\public\ftp\digest\ Use a specific parameter file, a Waffle mailbox, and place the output file in a different directory. Also name the output file using the Volume.Issue format (eg. 10.002). DIGEST -n -i c:\mail\info Digests using the default input, output, and parameter files, but includes c:\mail\info instead of 'digest.pre', and does not include the message headers. KILLTRAF The KillTraf program is used to remove old traffic records from the traffic control file. This version of KillTraf will remove the records from the traffic file, compressing the file as it removes them. The version supplied with V-MailServer 1.22 simply copied the records to a different file. Usage: KILLTRAF [-k] [-d mm-dd-yyyy] [-t hh:mm:ss ] [-o offset] -k Remove the records. If not specified, KillTraf will not pack the file. -d mm-dd-yyyy Set the date for which prior records will be removed. -t hh:mm:ss Copyright (c) 1993 Richard Vandenberg 89 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Set the time for which prior records will be removed. -o offset Specify an offset, in seconds, from the current time, instead of using the -d and -t parameters. 1 day = 86,400 seconds. 1 week = 604,800 seconds. 30 days = 2,592,000 seconds. 1 year = 31,536,000 seconds. The maximum value you can enter is 2^31 -1 seconds (68 years). If the date is not specified, KillTraf uses the current date. If the time is not specified, KillTraf uses 00:00:00. TRAF2CDF The Traf2CDF program will create a comma-delimited format file containing the traffic records. The output is produced on the standard output, and hence must be redirected for any useful purpose. This program may be useful if you want to perform traffic analysis using database software such as dBase. There are no command line options. VINFO VINFO is a dual-purpose program that can display configuration information and generate traffic statistics. VINFO can provide the following information: Listing of configuration file options List of mailing lists and options set for the lists List of file aliases and scripts defined for each file List of AFS request addresses and scripts defined for them Summary of mail server traffic by traffic type, by file path, and/or by requester address. Estimate costs of traffic, based on a cost per 1000 characters. Copyright (c) 1993 Richard Vandenberg 90 Additional Programs ────────────────────────────────────────────────────────────────────── Command line arguments: VINFO [-?|-h] [-t] [-sT,F,U,M] [-bD|W|H] [-d StartDate] [-e EndDate] [-o] [-c Configfile] [-f TrafficFile] [-i] [-a] [-u Select-ID] -? | -h Print this help. -c ConfigFile Use the specified configuration file. -t Show traffic summaries -sT,F,U,M Select a traffic summary: T - Traffic type F - File name U - User address M - Mailing list You may combine these options, eg -sTU -bD|W|M Break the traffic summary by Day,Week, or Month. Use only one option -d MM-DD-YYYY The start date of the records to include -e MM-DD-YYYY The end date of the records to include -o Use the address of the recipient instead of the poster. This will show all recipients in mailing lists -f TrafficFile Use a specific traffic file -i Display Configuration info -a Display all information (enables all options) -k Cost [unit] The cost per 1000 characters to transmit, and an optional unit to show on the report. eg. Pounds, DM, $ -u SelectID The address to select records for, or the mailing list name when choosing a Mailing list summary Examples: VINFO -t -sM -bM -k0.002 DM -u listname - gives a monthly listing of mailing list traffic for a specific list, along with the estimated costs. VINFO -t -sF -bW -k0.002 $ - gives a weekly listing of traffic, by filename, along with estimated costs. Copyright (c) 1993 Richard Vandenberg 91 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Uses for System Administrators: You can have mail server traffic summaries mailed to you nightly by specifying the following command in your CRON or SCHEDULE file: VINFO -t | RMAIL You@your.site VMEXEC VMEXEC is a small utility program that will check for the specified amount of free memory, and run the given program if there is enough, or queue it for later processing if there isn't. The format of the command line is: VMEXEC #-of-K-needed program arguments Example: VMEXEC 300 h:\vmail.exe -t mail-server The program specified may be any program whose input is redirected to the standard input. Examples are VMAIL, RMAIL and RNEWS. VMEXEC is used primarily where there is not enough free memory available to run the specified program. For example, if you run a large disk cache in conventional memory, or have a large number of TSRs loaded, there may not be enough free memory to run a large program like VMAIL.EXE. In this case, you can change your ALIASES entries to use VMEXEC, which takes only 20K free to run. Example ALIASES entry: mail-server | h:\vmexec.exe 300 h:\vmail.exe -t mailserver Copyright (c) 1993 Richard Vandenberg 92 ───────────────────────────── Using V-MailServer with UUPC _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Much of the terminology in this manual is directed towards installing V-MailServer with Waffle. This guide will give you a list of differences between Waffle and UUPC-Extended that affect the installation. Aside from these small changes, there are no other changes necessary. Throughout this manual, the terms "ALIASES file" and "ALIASES entry" are used to describe the list of system aliases used by Waffle. The equivalent files in UUPC are the FORWARD files in each user directory. To have Waffle spawn VMAIL.EXE to handle mail delivery and processing, an entry is created in the system aliases file, like this: mail-server | h:\vmail.exe [arguments] To do this with UUPC, you need to create an entry in the SYS\PASSWD file, such as: mail-server:*:::V-MailServer:d:/uupc/mail/server You will also need to create a FORWARD file in the uupc/mail/server directory to tell UUPC to run VMAIL.EXE. This file should contain the line: |h:\vmail.exe [arguments] Note that there should be no space after the "|" symbol. These are the only required changes to use V-MailServer with UUPC. Some other differences between Waffle and UUPC are listed below: Waffle has a built-in scheduling facility. To most efficiently use V-MailServer, the processing by VMAILX should be performed at scheduled intervals. A good place to do this is just before calling your host, or just after incoming messages are processed. Memory requirements for the UUPC MAIL program are uncertain. If free memory is a concern, you should use the VMEXEC program, as outlined in the Additional Programs section. Copyright (c) 1993 Richard Vandenberg 93 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Copyright (c) 1993 Richard Vandenberg 94 ───────────────────────────── Upgrade Policy _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Registered users of V-MailServer 2.20 will receive free upgrades to the next release. This free upgrade will include the registered version of the software on either 3½- or 5¼-inch diskettes. On the diskette will be two versions of this documentation - a plain text version, and a printer-dependent version. You may select any standard WordPerfect 5.1 (MSDOS) driver you wish, and a printer-ready file will be created using that driver. Of course, soft fonts cannot be used. Upgrades to printed documentation may be purchased at a nominal price that covers materials and shipping fees. In addition, registered users are also eligible to join the beta test program, which gives them access to current beta-release versions of V-MailServer. Copyright (c) 1993 Richard Vandenberg 95 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── ───────────────────────────── Acknowledgements _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ A number of people have contributed in a very large way to the development of V-MailServer. For this, I would like to thank them: The Beta-Test Team: Mathew, Mike Batchelor, Johannes Blankenstein, Gess Shankar, Manfredo Tichauer Bruce Peltzer, for allowing me to use his doubly-linked list routines. Without these, I would not have been able to develop much of the functionality in Version 2.2. J.D. Frazer, who owns the LEGACY role-playing list, which runs from my system. This list provided a good testing platform for developing V-MailServer. Copyright (c) 1993 Richard Vandenberg 96 ───────────────────────────── Index _________________________________________▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ /GET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 /PDGET . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5, 13 Access Control Language . . 7, 9, 10, 19-23, 32, 33, 37-39, 51, 62, 69 :label . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 CLEAR Commands . . . . . . . . . . . . . . . . . . . . . . . . 33 CLEAR Extra-Commands . . . . . . . . . . . . . . . . . . . . . 33 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 GOTO label . . . . . . . . . . . . . . . . . . . . . . . . . . 34 GRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 IF [NOT] Condition Command . . . . . . . . . . . . . . . . . . 34 IF [NOT] EXIST filename . . . . . . . . . . . . . . . . . . . 34 IF [NOT] MEMBER Listname . . . . . . . . . . . . . . . . . . . 34 REQSTAT ON | OFF | NONE . . . . . . . . . . . . . . . . . . . 35 Scripts . . . . . . . . . . . 10, 19, 20, 22, 37, 39, 51, 62, 69 SENDTEXT FileName . . . . . . . . . . . . . . . . . . . . . . 35 SHELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 SUBJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 TRANSTEXT . . . . . . . . . . . . . . . . . . . . . . . . . . 35 TRANSTEXTC . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . 96 Additional Programs . . . . . . . . . . . . . . . . . . . . 77, 87, 93 AFS processing . . . . . . . . . . . . . . . . . . . . . . . . . . 8 ALIASES.ADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Authorized-Subscription . . . . . . . . . . . . . . . . 61, 62, 66, 67 AUTOEXEC.BAT . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Automatic file sending . . . . . . . . . . . . . . . . . 5-8, 44, 69 Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . 41 CHKUUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Command Line Options . . . . . . . . . . . . . . . . . 10, 45, 81, 90 Command processing . . . . . . . . . . . . . . . . . . . . . . 9, 35 Configurable Messages . . . . . . . . . . . . . . . . . 19-21, 52, 19 ALIAS.TXT . . . . . . . . . . . . . . . . . . . . . . . . . . 19 HELP.TXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 LISTJOIN.TXT . . . . . . . . . . . . . . . . . . . 17, 61, 68, 73 QUEUE.WAI . . . . . . . . . . . . . . . . . . . . . . . . 19, 35 REJECT.TXT . . . . . . . . . . . . . . . . . . . . . . . . . . 19 SCRIPT.END . . . . . . . . . . . . . . . . . . . . . . . . 19, 22 SCRIPT.PRE . . . . . . . . . . . . . . . . . . . . . . 19, 21, 22 SEND.TXT . . . . . . . . . . . . . . . . . . . . . . . . . 19, 21 SHORT.HLP . . . . . . . . . . . . . . . . . . . . . . . . . . 19 UNSUBFAI.TXT . . . . . . . . . . . . . . . . . . . . . . . . . 19 Configuration . . 9, 10, 13, 14, 19-21, 30, 41-45, 52, 69, 73, 79, 81, 82, 90, 91 Configuration File . . . . . . . . . . . . . . . . . . . . . . . . 45 Configuration Parameters AFSFILE . . . . . . . . . . . . . . . . . . . . . . . . . 50, 69 ALLOWFIRSTREQUEST . . . . . . . . . . . . . . . . . . . . . . 50 COMMANDFILE . . . . . . . . . . . . . . . . . . . . . . . . . 51 DAILYLIMIT . . . . . . . . . . . . . . . . . . . . . . . . 42, 50 FILEALIAS . . . . . . . . . . . . . . . . . . . . . . . . . . 51 GRADEOPTION . . . . . . . . . . . . . . . . . . . . . . . . . 45 HEADERCONVERSION . . . . . . . . . . . . . . . . . 51, 57, 62, 65 Copyright (c) 1993 Richard Vandenberg 97 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── HELPFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 INDEXFILE . . . . . . . . . . . . . . . . . . . . . . . . 42, 48 INFOPATH . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 JUSTHEADERCONVERSION . . . . . . . . . . . . . . . 10, 51, 57, 65 KillFile . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 LOGFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 MAILINGLISTS . . . . . . . . . . . . . . . . . . . . . . . 50, 59 MAILPROGRAM . . . . . . . . . . . . . . . . . . . . . . . 9, 45 MESSAGELIMIT . . . . . . . . . . . . . . . . . . . . . . . 42, 50 Minimum-Free-Disk . . . . . . . . . . . . . . . . . . . . 42, 51 NODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 PASSWORDFILE . . . . . . . . . . . . . . . . . . . . . . . 48, 73 QUEUECOMMANDFILE . . . . . . . . . . . . . . . . . . . . . 10, 51 QUEUEDIR . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 QUEUELIMITFILE . . . . . . . . . . . . . . . . . . . . 50, 82, 83 QUEUEPROGRAM . . . . . . . . . . . . . . . . . . . . . . . 9, 51 REJECTFILE . . . . . . . . . . . . . . . . . . . . . . . . . . 49 RMAILLINEMAX . . . . . . . . . . . . . . . . . . . . . . . 42, 45 SEARCHTREE . . . . . . . . . . . . . . . . . . . . 48, 55, 56, 85 SENDERNAME . . . . . . . . . . . . . . . . . . . . . . . . . . 46 SEQF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 SERVERNAME . . . . . . . . . . . . . . . . . . . . . . . . . . 46 STATUSWORKFILE . . . . . . . . . . . . . . . . . . . . . . . . 52 TEMPMAILFILE . . . . . . . . . . . . . . . . . . . . . . . . . 53 To-Format . . . . . . . . . . . . . . . . . . . . . . . . 43, 46 TRAFFICCONTROL . . . . . . . . . . . . . . . . . . . . . . . . 49 UDCFile . . . . . . . . . . . . . . . . . . . . . . . . . 39, 52 USERDIRFILE . . . . . . . . . . . . . . . . . . . . . . . 39, 52 USERSECURITYFILE . . . . . . . . . . . . . . . . . . . . . 49, 85 UUCPFROM . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 UUENCODE_SWITCH . . . . . . . . . . . . . . . . . . . . . . . 46 UUEOUTPUTSPEC . . . . . . . . . . . . . . . . . . . . . . . . 47 UUEPROG . . . . . . . . . . . . . . . . . . . . . . . . . 42, 46 UUETEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 VALIDPATHS . . . . . . . . . . . . . . . . . . . . 48, 55-57, 85 Words-Path . . . . . . . . . . . . . . . . . . . . . . . . 19, 52 XXENCODE_SWITCH . . . . . . . . . . . . . . . . . . . . . . . 46 ECHOMAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . 15, 62 File Server Commands . . . . . . . . . . . . . . . . . 13, 14, 17, 68 Administrative Commands . . . . . . . . . . . . . . . . . 17, 61 Advanced File Server Commands . . . . . . . . . . . . . . . . 14 Advanced Mailing List Commands . . . . . . . . . . . . . . . . 15 Basic File Server Commands . . . . . . . . . . . . . . . . . . 13 Basic Mailing List Commands . . . . . . . . . . . . . . . . . 14 File Server Services . . . . . . . . . . . . . . . . . . . . . 48, 55 File Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 FOR address . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 General Information . . . . . . . . . . . . . . . . . . . . . . 13, 19 GET . . . . . . . . . . . . . . . . . . . . . . 5, 13, 18, 39, 55, 79 Copyright (c) 1993 Richard Vandenberg 98 Index ────────────────────────────────────────────────────────────────────── GRADE . . . . . . . . . . . . . . . . . . . . . . . . . 20, 34, 45, 62 Header Conversion . . . . . . . . 8, 10, 16, 20, 26-31, 51, 57, 62, 65 ADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 ORDER . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 REPLACE . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 STRIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Header processing . . . . . . . . . . . . . . . . . . . . . . . . . 8 HELP . . . . . . . . . . . . . . . . . 5, 13, 19, 41, 42, 48, 73, 91 INDEX . . . . . . . . . . . . . . . . . 5, 13, 42, 43, 48, 60, 62, 97 INFO . . . . . . . . . . . . . . . . . . 5, 6, 13, 14, 49, 69, 89, 91 Installation . . . . . . . . . . . . . . . . . . . 41, 42, 44, 93, 41 KILLTRAF . . . . . . . . . . . . . . . . . . . . . . . . . 77, 89, 90 Limited Warranty . . . . . . . . . . . . . . . . . . . . . . . . . 3 LISTJOIN.TXT . . . . . . . . . . . . . . . . . . . . . . . . . 19, 23 Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Command-Filename . . . . . . . . . . . . . . . . . . . . . . . 22 Command-Line . . . . . . . . . . . . . . . . . . . . . . . . . 22 Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 File-Requested . . . . . . . . . . . . . . . . . . . . . . . . 21 File-Sections . . . . . . . . . . . . . . . . . . . . . . . . 21 File-Size . . . . . . . . . . . . . . . . . . . . . . . . . . 21 File-Size-UU . . . . . . . . . . . . . . . . . . . . . . . . . 21 Header-Date . . . . . . . . . . . . . . . . . . . . . . . . . 20 Header-From . . . . . . . . . . . . . . . . . . . . . . . . . 20 Header-Reply-To . . . . . . . . . . . . . . . . . . . . . . . 20 Legal . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Legal-Path . . . . . . . . . . . . . . . . . . . . . . . . . . 22 LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 MailGrade . . . . . . . . . . . . . . . . . . . . . . . . . . 20 MailOptions . . . . . . . . . . . . . . . . . . . . . . . . . 20 MList-Name . . . . . . . . . . . . . . . . . . . . . . . . . . 23 New-Name . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Orig-Name . . . . . . . . . . . . . . . . . . . . . . . . . . 23 OwnerID . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Parm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Queue-Count . . . . . . . . . . . . . . . . . . . . . . . . . 21 Queue-File-Count . . . . . . . . . . . . . . . . . . . . . . . 21 Queue-Mail-Count . . . . . . . . . . . . . . . . . . . . . . . 21 Queue-Queue-Count . . . . . . . . . . . . . . . . . . . . . . 21 Queue-Status-Count . . . . . . . . . . . . . . . . . . . . . . 22 ReceivedID . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Rest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Server-Name . . . . . . . . . . . . . . . . . . . . . . . . . 21 TempFile . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Total-File-Sections . . . . . . . . . . . . . . . . . . . . . 22 Total-File-Size . . . . . . . . . . . . . . . . . . . . . . . 22 Copyright (c) 1993 Richard Vandenberg 99 V-MailServer User Manual ────────────────────────────────────────────────────────────────────── Total-File-Size-UU . . . . . . . . . . . . . . . . . . . . . . 22 Mailing List Files . . . . . . . . . . . . . . . . . . . . 59, 65, 85 Mailing List Options Authorized-Subscription . . . . . . . . . . . . . . . . . . . 62 Command . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Echomail . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Grade . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 HeaderConversion . . . . . . . . . . . . . . . . . . . . . . . 62 Non-Member-Posting . . . . . . . . . . . . . . . . . . . . . . 62 Reject-Command-File . . . . . . . . . . . . . . . . . . . . . 62 Reply-To: . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Restricted-Posting . . . . . . . . . . . . . . . . . . . . . . 63 Restricted-Reject-File . . . . . . . . . . . . . . . . . . . . 63 Restricted-Reject-Subject . . . . . . . . . . . . . . . . . . 63 Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 ROOT-x . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Sender: . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Valid-Path-x . . . . . . . . . . . . . . . . . . . . . . . . . 64 Mailing list processing . . . . . . . . . . . . . . . . . . . . 8, 27 Mailing List User Options Address . . . . . . . . . . . . . . . . . . . . . . . . . 18, 64 Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Post . . . . . . . . . . . . . . . . . . . . . . . 17, 18, 63, 64 Reply . . . . . . . . . . . . . . . . . . . . . . . . . . 16, 65 Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Subdate . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Mailing Lists . . 5, 13, 16-18, 25, 27, 31, 41, 43-45, 50, 57, 59, 62, 65, 75, 81, 85, 90, 91 Message Processing . . . . . . . . . . . . . . . . . . . . . . . . 7 NOECHOMAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Non-Member-Posting . . . . . . . . . . . . . . . . . . . . . . . . 62 OPTION List-Name List-Option Value . . . . . . . . . . . . . . . . 16 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 owner . . . . . . . . . . . . . . . . 6, 17, 18, 46, 61-63, 65-68, 73 Owner-Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 PASSWORD . . . . . . . . . . . . . . . . . . . 9, 14, 39, 48, 68, 73 Planning the configuration . . . . . . . . . . . . . . . . . . . . 41 Process Description . . . . . . . . . . . . . . . . . . . . . . . . 8 PW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14, 68 Queued requests . . . . . . . . . . . . . . 9, 10, 21, 43, 52, 82, 83 Reject-Command-File . . . . . . . . . . . . . . . . . . . . . . . . 62 Reply-To: . . . . . 8, 16, 17, 20, 21, 27, 28, 31, 60, 61, 63, 65, 75 Restricted-Posting . . . . . . . . . . . . . . . . . . . . . . 63, 64 Restricted-Reject-File . . . . . . . . . . . . . . . . . . . . . . 63 Restricted-Reject-Subject . . . . . . . . . . . . . . . . . . . . . 63 REVIEW . . . . . . . . . . . . . . . . . . . 15-17, 60, 63-65, 68, 73 SEND . 5, 8, 13, 15, 17, 19, 21, 35, 37, 38, 37, 38, 47, 48, 50, 55, 60, 62, 63, 67, 69, 79, 85 Copyright (c) 1993 Richard Vandenberg 100 Index ────────────────────────────────────────────────────────────────────── Sender: . . . . . . . . . . . . . . . . . . 27, 28, 31, 46, 60, 63, 75 SIGNOFF . . . . . . . . . . . . . . . . . . . 5, 6, 15, 17, 60, 66-68 SUBJECT [New Subject] . . . . . . . . . . . . . . . . . . . . . . . 35 SUBSCRIBE . . . . . . 5, 6, 14, 17, 19, 23, 32, 37, 59, 60, 62, 66-68 TRAF2CDF . . . . . . . . . . . . . . . . . . . . . . . . . . . 77, 90 Traffic Control File . . . . . . . . . . . . . . . . . . . . . 77, 89 UNSUBSCRIBE . . . . . . . . . . . . . . . . . . . . . . . . 15, 19, 59 Upgrade Policy . . . . . . . . . . . . . . . . . . . . . . . . . . 95 USERDIRFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 UUENCODE . . . . . . . . . . . . . . . . . . . . . . . 24, 46, 47, 55 UUENCODEOPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . 46 UUPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 UUPC-Extended . . . . . . . . . . . . . . . 5, 41, 59, 81, 87, 88, 93 Variables . . . . . . . . . . . . . . . . . . . . . . . . . 20, 33, 35 VINSTALL . . . . . . . . . . . . . . . . . . . . . . . . . 41, 43, 55 VMAIL Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 VMAILX . . . . . . . . . . . . . . . 7, 9, 10, 43, 50, 52, 82, 83, 93 VMAILX Options . . . . . . . . . . . . . . . . . . . . . . . . . . 82 VMEXEC . . . . . . . . . . . . . . . . . . . . . . . . . . 81, 92, 93 VMS.CFG . . . . . . . . . . . . . . . . . . . . 41-43, 45, 57, 59, 65 VSET.BAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 XXENCODE . . . . . . . . . . . . . . . . . . . . . . . . . . . 18, 46 Copyright (c) 1993 Richard Vandenberg 101