Installation guide for LISTSERV™ for Windows NT™

Version 1.8b Copyright © L-Soft International, 1996

Last update: 13 Feb 1996

Contents

1. Technical requirements for running under Windows NT™

LISTSERV for Windows NT™ requires the following products:

  1. Windows NT™ version 3.5 or higher.

  2. TCP/IP connectivity.

  3. L-Soft recommends 24-32M of memory for Intel® machines, although small to medium lists can be supported in a 16M machine with NT 3.5x. A 32M Intel® machine can support lists as large as 100,000 subscribers insofar as LISTSERV itself is concerned (the machine in charge of delivering all these messages would need a lot more capacity).

  4. An SMTP mail delivery agent is required. This could be L-Soft's LSMTP™ product for Windows NT™ or any other SMTP agent that will handle your load. An "SMTP listener" service is provided with LISTSERV for use with external, non-L-Soft mail delivery agents.

Please note, however, that due to the lack of a standard Windows Internet mail API, the use of LISTSERV's SMTP listener (SMTPL.EXE) requires full access to port 25 of your machine. This means that you will not be able to run LISTSERV on a machine that is already running an non-L-Soft SMTP server (e.g., the Microsoft Mail SMTP Gateway) that needs access to port 25. As a result, LISTSERV running with the SMTPL "listener" requires an external machine for the delivery of SMTP mail. The external machine can be any hardware, operating system and software with a SMTP implementation that meets your needs, in terms of volume and RFC compliance. L-Soft's LSMTP product includes the functionality of the "SMTP listener" and therefore bypasses this problem.

1.a. Running LISTSERV and LSMTP™ on the same machine

If you run LISTSERV and LSMTP on the same machine, you must disable the SMTPL "listener" (SMTPL.EXE), as LSMTP and SMTPL would be in conflict for port 25. Simply open the Control Panel, choose Services, and change the Startup parameters for the LISTSERV SMTP Listener to "Manual" or "Disabled". Note that we recommend that you install and test LISTSERV with the SMTPL listener before turning traffic over to LSMTP.

2. Installation overview

We recommend that you take a few moments to read this installation guide before starting the installation of LISTSERV. The software is provided in a compressed file format, available from our ftp site (ftp://ftp.lsoft.com). To install LISTSERV, you need only uncompress the software into a "scratch" or temporary directory and do the following:

Here are a few considerations not addressed by the automatic installation program that you should do after it exits:

  1. Optionally, you can create a LISTSERV userid with the group/profile you use for normal, unprivileged users, and use File Manager to give it full access to C:\LISTSERV. The administrator should also have full access, normal users (the little "earth" icon) do not need any access at all. You are of course free to change this policy to better meet your security needs, as long as LISTSERV has full access.
  2. If you choose not to configure the SITE.CFG file with the automatic installation program, type CD MAIN, REN SITE_DEFAULT.CFG SITE.CFG, and edit the SITE.CFG file with a plain-text editor such as Notepad (do not use a word processor). This is LISTSERV's main configuration file, and it should be self-documented. If you have any question, write to SUPPORT@LSOFT.COM for assistance.
  3. Still in the MAIN directory, create a file called LICENSE.MERGE with the License Activation Key (LAK) you received from L-Soft. This license key activates the software in the mode corresponding to the options and capacity you have licensed from L-Soft.
  4. You are now ready to start the software interactively, to make sure that everything is working correctly. Type START to create a second CMD window and, still from the MAIN directory, type SMTPL START. This will start the SMTP listener, which should quickly announce that it is has initialized successfully.
  5. In the other CMD window, type LSV START. Various tables will then be rebuilt (the software is shipped without pre-built tables to make the ZIP files smaller, and as a test of your successful installation). The license key will be validated, and the server will start. You can now enter commands from the keyboard, such as SHOW LICENSE or SHOW VERSION (if you are migrating from the VMS™ or unix® version of LISTSERV, please note that with the NT version you should not press Ctrl-C before entering your command).
  6. Send Internet mail to LISTSERV with some random command, such as HELP, to check that the SMTP listener and outgoing mail interface are working correctly. If you have any problem, contact SUPPORT@LSOFT.COM. Note that LISTSERV will not see any mail you send it via MAPI unless you have a MAPI/SMTP gateway for your LAN. This version of LISTSERV does not include a MAPI gateway.
  7. When you are satisfied that the server is working, type STOP in the LSV window to stop the server, and just Ctrl-C in the SMTPL window. Then type SMTPL DEFINE and LSV DEFINE to define LISTSERV and the SMTP listener as NT Services. You can view the services from Control Panel, and change the login userid or startup option. Finally, start the services and repeat the test in point 8 to make sure that everything still works. You will get daily log files in the C:\LISTSERV\LOG directory. If the service cannot start, use Event Viewer to examine the Application log for an explanatory error message.

3. Things to watch out for

4. The LISTSERV directory tree

The LISTSERV directory tree contains the following subdirectories:

Directory

Description

LOGThe directory where the server log files are created. These files can be viewed with Notepad or equivalent, but the active (i.e. today's) file should not be modified. These files are for your convenience in troubleshooting problems or monitoring server activity. LISTSERV does not use them for anything.
MAINLISTSERV's main directory. This is where configuration files, executables, lists and the like are located. Some of these files can be modified directly by the administrator, using Notepad, but unless this is specifically indicated in the present installation guide, you should assume that the files are private to LISTSERV and cannot be edited.
SPOOLThe directory where incoming and outgoing requests are stored until they can be processed or sent. You should not modify any of the files in this directory. Some are binary files and cannot be viewed.
TMPA directory for temporary files. If the server ever crashes when processing a command, you should save the contents of that directory before restarting it, in case they prove useful in troubleshooting the problem.

5. Security

For Windows NTÖ installations, L-Soft recommends that you run LISTSERV and the SMTP listener or LSMTP in a non-privileged account, and using a NTFS partition with a private directory (no world access). You are, however, free to run either or both services from the local System account, and this is the way the software is configured when you install it. The reason for this apparent conflict is that the installation procedure cannot know what your local account creation policy is (user groups, profiles, etc), and lets you create the LISTSERV account yourself. To run the two Services from the LISTSERV account, you must modify their startup options from Control Panel and indicate "Log in as LISTSERV". Control Panel will add the "Log in as system service" privilege to LISTSERV's profile, and this should not be removed. LISTSERV does not, however, need any other privilege.

6. Starting up LISTSERV

LISTSERV can be started interactively, for debugging purposes, or as an NT Service. However, you can only run one copy of LISTSERV at any given time. That is, you cannot start LISTSERV interactively if it is already running as a service, or vice-versa, nor can you start LISTSERV in multiple CMD windows. The same applies to the SMTP listener.

When running as a service under Windows NTÖ, LISTSERV and the SMTP listener are stopped or started using the Services applet of Control Panel. This is the normal production mode. The services create log files in the C:\LISTSERV\LOG directory (assuming you installed LISTSERV in C:\LISTSERV) but, for performance reasons, the file buffers are not flushed with each and every write. If you attempt to TYPE the log file, it may appear to be empty. If you wait a few minutes, the buffers will be flushed and you will be able to examine the files. Critical errors are reported to the system event log and can be examined with Event Viewer (select the Application log).

To start LISTSERV or the SMTP listener interactively on Windows NTÖ, open a CMD window, go to the C:\LISTSERV\MAIN directory (assuming you installed LISTSERV in C:\LISTSERV) and type LSV START or SMTPL START. You can also use the icons created by the installation program in Program Manager or the Start menu. In this mode, the log files are also created but the file buffers are flushed continuously. This mode should be used only when you are trying to troubleshoot a problem. Flushing the logs continuously ensures that, in the event of a severe program failure, the logs will always contain information about the cause of the failure. To stop LSV, simply type STOP. To stop SMTPL, wait until there is no more activity and type Ctrl-C. LSMTP should be stopped from its own control panel.

7. IMPORTANT - License Activation Key

Before you can start up LISTSERV, you will need to install a License Activation Key (LAK). This is usually accomplished during the automatic setup process, but it can be done manually as well. To install the LAK, simply create a file called LICENSE.MERGE in the C:\LISTSERV\MAIN directory (assuming you installed LISTSERV in C:\LISTSERV) with the contents of the license key. If you received the LAK electronically or on a floppy, you can simply copy it to LICENSE.MERGE. Note that LISTSERV must be restarted in order for the new LAK to be activated.

Note that LSMTP, if installed, requires a separate LAK, which is installed in the LSMTP home directory in an identical manner. Your LISTSERV LAK will not work with LSMTP.

8. Registering the server

NOTE: This section does not apply to evaluation kits. Evaluation copies of LISTSERV should not be registered because they are (presumably) temporary servers running test lists, whose existence should not be broadcast.

Once the server is ready for production use (that is, once you have installed a permanent License Activation Key, and once you have arranged for LISTSERV to be started automatically when the system boots), you should register it with L-Soft by filling in the enclosed registration form, and returning it to SUPPORT@LSOFT.COM. Registering the server is necessary to broadcast its existence to the other LISTSERV servers. Once you have registered, your server will be sent periodic updates about the lists hosted by other LISTSERV sites, among other things, and, similarly, other LISTSERV sites will receive information about the public lists you are hosting. Here is the registration form (the fields you must fill in are represented as XXXXXXXX, or a suggested value is provided):

------------------------------- Cut here ------------------------------- :node.XXXXXXXX ! Internet hostname :userid.LISTSERV ! Username under which LISTSERV runs :net.Internet ! :site.XXXXXXXX ! XYZ Corporation, city, state, country :country.XX ! Two-letter ISO country code :system.NT 3.5 (Intel) ! NT version (architecture) :machine.XXXXXXXX ! Hardware - P90, AXP 3000-00,etc :contact.XXXXXXXX ! Contact person, in the following format: ! (Joe Manager) JOE@XYZ.COM (+1 301 871.2727) :type.NT ! Do not change this - must be "NT" :version.1.8b ! Version you are currently running :backbone.XXXXXXXX ! YES or NO, depending on whether you want to ! participate in the LISTSERV backbone; L-Soft ! will advise you on this keyword. ------------------------------- Cut here -------------------------------

9. List creation

In order to create a new list, you must:

  1. Prepare a "list header", for instance using the sample provided below. You can also get the header of an existing (L-Soft) LISTSERV list and use it as sample.
  2. Fill in the PW=CCCCCCCC on the first line with the "CREATEPW" you chose when configuring LISTSERV. The PW=XXXXXXX line at the end defines the password you want to assign to your list. This is the password that the list owner will have to supply with sending commands via mail, if you select "Validate= Yes". Alternatively, you can select "Validate= Yes,Confirm" to use the "OK" mechanism, which does not require any password.
  3. Mail the resulting file to the LISTSERV address, from a username defined as "postmaster" in the LISTSERV configuration, and using Internet mail. For instance, from a VMSÖ system, you would do:
     $ mail
    
     MAIL> send newlist.create
    
     To: in%"listserv@xyz.com"
    
     Subj:
    
     
    
     MAIL>
    Or, from a unix® system:

    $ mail listserv@xyz.com < newlist.create

    On a PC, you would use the graphical interface that came with your mail product. Make sure to cut+paste the file via the Clipboard and not send it as an "attachment" or use drag and drop. "Attachment" mechanisms are often proprietary or PC-specific and cannot be guaranteed to work. Sending plain text from the Clipboard always works.

    If you have questions about list creation, keywords, list management and other high-level or system-independent LISTSERV topics, the best place to ask them is the LSTOWN-L list, an open forum of LISTSERV list owners.

    Please note that, for security reasons, LISTSERV will not create archive directories automatically. You must create the directory and set the protections before storing the list. LISTSERV will need read, write and delete access to the directory.

    For assistance with problems specific to evaluation kits, join the LSTSRV-E list or contact Support@LSOFT.COM for a prompt reply. Please don't forget to tell us which hardware and software you are using!

    ------------------------------- Cut here ------------------------------
    
    PUT SAMPLE.LIST PW=CCCCCCCC
    
    *
    
    * Title of sample LISTSERV list
    
    *
    
    * Review= Public          Subscription= Open               Send= Public
    
    * Notify= Yes             Reply-to= List,Respect           Files= No
    
    * Stats= Normal,Private   Validate= No
    
    * Notebook= Yes,C:\LISTS\PUBLIC,Monthly,Public
    
    *
    
    * Owner= someone@somewhere.COM
    
    *
    
    * PW= XXXXXXXX
    
    ------------------------------- Cut here -------------------------------
    Note: There is no special command to delete a list. To delete a list, simply move any archives or other related files that you wish to save to a safe place (delete them if you don't want to keep them) and then use the DOS prompt or File Manager to delete the list file itself.

    10. Note to VM customers

    VM lists can be migrated to Windows NTÖ with a much simpler procedure:

    You can also FTP the archive files (xxxx.LOGyymm) directly to the directory selected in point C.

    11. File server functions

    There are three file server systems currently in use or under development for LISTSERV:

    In general, the three systems are compatible, with the understanding that the temporary system does not include all the possible options. However, the mechanism for registering files (defining them to the file server system) is different. With the traditional system, you create files called "xxxx FILELIST", which contain definitions for all the files belonging to a particular archive. With the temporary system, you store these definitions in a file called SITE.CATALOG, in the MAIN directory. While you can create files called "xxxx FILELIST" and users can retrieve them, they do not in turn define further files. The new file server system will eliminate this confusion, but in the meantime you should be aware of the differences between VM and PC file server functions as many list owners use a VM server with different conventions, and may give you incorrect advice.

    To register a new file to the server, you add a line to the SITE.CATALOG file in the MAIN directory (create it if it did not exist). Do not modify the SYSTEM.CATALOG file, as it is part of LISTSERV and may be replaced when you apply service. Here is what a typical SITE.CATALOG entry looks like:

    MY.FILE MY.FILE.C:\FILES\XYZ XXX YYY

    The first item, MY.FILE, is the name by which the file is known to LISTSERV. That is, the users will use GET MY.FILE to order a copy of that file. The name should only contain one period. Only the first 8 characters of the name and the first 8 characters of the extension are shown by the INDEX command. This restriction will be removed with the new file server system.

    The second item, MY.FILE.C:\FILES\XYZ, is the name LISTSERV will use for the actual disk file: filename, period, extension, period, directory. The strange format is because LISTSERV uses an operating system abstraction layer for file accesses, where all system-dependent attributes are relegated to the last item. Note that the directory must be created before you register the file. For security reasons, LISTSERV will not create the directory (or set the protections) for you. Note that LISTSERV will normally need full access to these files.

    The third and fourth items are "File Access Codes" (FACs). The first is for read accesses, and the second for writing. The following file access codes are available:

    Access Code

    Description

    ALLuniversal access
    CTLLISTSERV administrator ("postmaster" in SITE.CFG) only.
    N/Ano access. This is normally used (in SYSTEM.CATALOG) for files that are maintained internally by LISTSERV and should not be updated using the file server functions, but you can use it for your own purposes as well.
    PRIVATE(xxx)only members of the xxx list have access.
    OWNER(xxx)only the owners of the xxx list have access.
    SERVICE(xxx)only users in the service area of the xxx list have access.
    NOTEBOOK(xxx)same access as the archives of the xxx list.
    user@hostthe user in question is granted access.

    Except for ALL and CTL, which must occur on their own, you can specify multiple file access code entries, separated by a comma with no intervening space. For instance:

    MY.FILE MY.FILE.C:\FILES\XYZ JOE@XYZ.EDU,JACK@XYZ.EDU,PRIVATE(XYZ-L) CTL

    defines a file that Joe, Jack and the subscribers of the XYZ-L list can order via the GET command, but that only the LISTSERV administrator can update.

    IMPORTANT: These "file access codes" apply to LISTSERV commands (GET, PUT, INDEX) only, and do not affect native Windows NTÖ file and directory security. It is your responsibility to protect the actual disk file by setting the file protections for the directory in which they are created.

    12. Documentation and where to get more help

    You should be aware that there are several documentation files included with LISTSERV. They are located in the MAIN directory and include the following:

    Filename

    Description

    LISTSERV.MEMOA General Introduction to LISTSERV
    LISTPRES.MEMOA presentation of LISTSERV for the general user
    LISTOWNR.MEMOA List Owner's Manual for LISTSERV 1.8b
    LISTKEYW.MEMOA manual of the various list header keywords and what they do
    LISTALL.REFCARDA quick reference card for LISTSERV commands

    The List Owner's Manual can also be viewed on the World Wide Web at the URL

    http://www.lsoft.com/manuals/ownerindex.html

    Additionally, the following files are available for downloading from L-Soft's anonymous ftp site, ftp.lsoft.com :

    LISTSERV for the non-technical user

    Filename

    Description

    NSC93US.PSPostScript(tm) version formatted for 8-1/2" x 11" paper
    NSC93A4.PSPostScript(tm) version formatted for A4 paper
    NSC93.MEMOPlain text version

    List Owner's Manual for LISTSERV version 1.8b

    OWNER.DOCWord for Windows 6.0
    OWNER.PDFAdobe Acrobat .PDF (Portable Document Format)
    OWNER.MCWWord for Macintosh 5.1
    OWNER.RTFRich Text Format
    OWNER.WPFWordPerfect for Windows 5.x
    OWNERPS.ZIPPostscriptÖ (8-1/2 x 11 paper size) (DOS ZIP)
    OWNER.PS.GZPostscriptÖ (8-1/2 x 11 paper size) (Unix gzip)
    OWNER.PS.ZPostscriptÖ (8-1/2 x 11 paper size) (Unix compress)
    OWNA4PS.ZIPPostscriptÖ (A4 paper size) (DOS ZIP)
    OWNERA4.PS.GZPostscriptÖ (A4 paper size) (Unix gzip)
    OWNERA4.PS.ZPostscriptÖ (A4 paper size) (Unix compress)

    There are several mailing lists dedicated to the support of LISTSERV.

    List Name

    Description

    LSTSRV-L@SEARN.SUNET.SEfor LISTSERV maintainers and interested list owners
    LSTOWN-L@SEARN.SUNET.SEfor LISTSERV list owners
    LSTSRV-E@SEARN.SUNET.SEfor LISTSERV evaluation kit users

    To subscribe to any of these lists, send mail to LISTSERV@LISTSERV.NET with the following command in the body of the message:

    SUBSCRIBE listname Your Name


    L-SOFT, LISTSERV and LSMTP are trademarks of L-Soft international, Inc.
    Unix is a registered trademark of UNIX Systems Laboratories, Inc.
    Alpha AXP and VMS are trademarks of Digital Equipment Corporation.
    Microsoft is a registered trademark of and Windows NT and Windows 95 are trademarks of Microsoft Corporation.
    Intel is a registered trademark of Intel Corporation.
    MIPS is a registered trademark of MIPS Computer Systems, Inc.
    All other trademarks, both marked and not marked, are the property of their respective owners.