Copyright (c) L-Soft international, Inc. 1994-2006
Last update: 1 Sep 2006
For changes to LISTSERV from version 14.4 to 14.5, please view the LISTSERV 14.4 release notes at http://www.lsoft.com/manuals/1.8e/index.html .
There are two versions of LISTSERV: A "Classic" version and a "Lite" version. For a description of the differences between LISTSERV Classic and LISTSERV Lite, please see the URL
LISTSERV Lite is user-supported, via the mailing list
Please do not send questions regarding LISTSERV Lite to L-Soft's normal support addresses.
Please see http://www.lsoft.com/y2k-faq.html .
LISTSERV version 14.1 (formerly 1.8e-2002a) was the last version for several operating systems which have become obsolescent over the life of this product cycle. The following unix operating systems are no longer supported in version 14.1 and following:
Sites running these operating systems should migrate to a different operating system. Please contact your sales representative for further information.
It should be noted that L-Soft dropped support for the following operating systems with the original release of LISTSERV 14 (in other words, LISTSERV 13 or 1.8d was the last version for these platforms):
Windows NT 3.5, 3.51, 4.0 pre-SP6 (Intel)
Windows NT (Alpha AXP)
SunOS 4.x (SPARC)
On the plus side, L-Soft now formally supports FreeBSD (Intel) and Linux (S/390) since LISTSERV 14, and MacOS beginning with LISTSERV 14.4.
A comprehensive list of operating systems (and versions) under which LISTSERV is supported can be found at
LISTSERV Classic Distribution
LISTSERV Classic for UNIX(R) is distributed as two compressed "tar" archive files (the original method of distribution) or as a single binary installation kit (used in the "simplified" installation), depending on your needs. The installation guide, which is the file you are currently reading, is also available independently of the archives.
In the original distribution scheme, one of the tar files (common.tar.Z) contains data files common to LISTSERV on all UNIX(R) platforms, including the Makefile, and the other (`uname`.tar.Z, where `uname` corresponds to your OS-specific distribution) contains the compiled version of the LISTSERV server, object files for recompilation, and the 'wa' CGI for the web archive interface. In order to simplify the process of removing extraneous files created during the installation procedure, you should copy the tar files to a scratch directory, install LISTSERV, and then "rm -fr /tmp/scratch" (or whatever you name the staging area).
The "simplified" distribution is a single binary that is run at the shell prompt. This installer asks a number of questions related to the installation and then installs LISTSERV accordingly.
LISTSERV Lite Distribution
LISTSERV Lite for UNIX(R) is distributed as a single compressed "tar" archive file, `uname`-Lite.tar.Z (the original method of distribution), or as a single binary installation kit (used in the "simplified" installation), depending on your needs.
In the original distribution scheme, all files needed, including the "common" files, are shipped in the single archive.
The "simplified" distribution is a single binary that is run at the shell prompt. This installer asks a number of questions related to the installation and then installs LISTSERV accordingly.
A simplified installation procedure for LISTSERV for Unix platforms is now available. A new configuration script replaces the need to manually configure LISTSERV's Makefile and go.user site configuration file.
In the 14.4 release and following, the installation kit can be downloaded as a single compressed binary, shipped as `uname`.bin.Z. Simply uncompressing the kit (with either compress(1) or gunzip(1)), setting its minimum permissions to 500 (owner r-x), and running it from a scratch directory will allow you to install LISTSERV without having to unpack .tar.Z files, modify the Makefile, etc. While the old two-part kits will remain available for the foreseeable future for sites requiring more control over the installation, this new one-part kit is is designed for first-time installers or those who simply wish to install LISTSERV with most of its default settings. It is thus necessarily limited in its scope and does not provide user control over every aspect of the installation, but rather, allows the installer to set several basic options and relies on Makefile defaults for the rest.
If it is desired to have complete control over all aspects of the LISTSERV installation, it will be necessary for installers to continue with the current document.
The simplified installation procedure can be viewed on the Web at http://www.lsoft.com/manuals/1.8e/unixinst-sim.html .
If you're very familiar with software installations on your system and would prefer terse, matter of fact steps rather than complete instructions, skip to the section entitled "The Bare Facts About Installing LISTSERV" near the end of this document.
LISTSERV for UNIX is shipped with both:
· pre-compiled lsv and lsv_amin binaries which will run with the default settings; and
· an lsv.o object file and C source for lsv_amin that can be linked locally if you need to modify the Makefile or simply prefer to compile the server yourself.
The installation of LISTSERV consists of the following steps:
· creating a "listserv" username,
· extracting the files in the archive file(s) into a 'scratch' directory,
· customizing the Makefile, including deciding what directories you want used for incoming mail, as well as for the LISTSERV program and data files,
· depending on whether or not you are using the precompiled binaries:
· if you are using the precompiled binaries: renaming 'lsv_amin-precompiled' to 'lsv_amin'.
· if you do not have a compiler, moving or deleting the 'lcmd.c' and 'jobview.c' files from the 'scratch' directory.
· running "make install", which creates the necessary directories and copies the programs generated in the previous step to the proper places, and sets file and directory permissions so that lsv_amin and 'listserv' can have access to their files,
· modifying the "go.user" shell script to accurately describe your system,
· appending entries to your /etc/aliases file to handle mail sent to your LISTSERV username, and directing your sendmail daemon to use the new aliases,
· creating a "license.merge" file to make license key information available to your server,
· (Classic) subscribing to the LSTSRV-E forum to join others in discussing experiences with the evaluation copies of LISTSERV,
· (Lite) subscribing to the LISTSERV-LITE forum to join others in discussing experiences with LISTSERV Lite,
· and finally (optional; Classic only), registering your LISTSERV server so that other LISTSERV servers around the Internet will know about your server.
All of these steps are described in greater detail in the sections below. They should be performed in the order they are presented since some steps rely on the results of earlier steps. Once you've finished the above steps, you will be able to start your LISTSERV server and verify that it's working. You'll then be ready to create mailing lists and start using your LISTSERV server.
In the past, many commercial unixes were shipped with sendmail version 5. If your sendmail is at a version less than version 8, note that you will probably experience long turnaround times on requests to LISTSERV that could run to several hours. This is because earlier Sendmail versions could handle only 1-2K deliveries per day. L-Soft strongly recommends that any Unix site running LISTSERV with Sendmail upgrade to at least Sendmail version 8.7.x, and at this time, for anti-spam and general security purposes, Sendmail version 8.11.x or later should be preferred.
If you are running a sendmail earlier than 8.7.x, please note that at least one sendmail archive site (see ftp://ftp.cs.berkeley.edu/ucb/sendmail/.message) currently notifies users that "8.6 is not supported, not secure, and should not be run on any network-connected machine."
If you are running sendmail out of a restricted shell (for instance the smrsh shell), note that the lsv_amin mailer program that you will install below must be registered as a trusted application that may be executed by sendmail, or mail sent to LISTSERV and to lists will be rejected (typically with a sh: lsv_amin not available for sendmail programs error, although this may depend on how you have sendmail set up). Registering an application with the restricted shell typically involves placing symbolic links from /usr/adm/sm.bin/ to the programs which are authorized. If you need more information on restricted shells, please refer to the sendmail documentation.
LISTSERV requires exclusive access to the mail sent to one username. Unless you have a very good reason to do otherwise, the username "listserv" should be used for that purpose. Many people around the world are already familiar with LISTSERV, and will assume that mail sent to <email@example.com> will reach the server. The LISTSERV account is just an ordinary user, it doesn't need privileges, doesn't require access to restricted directories, and it doesn't need to have any particular UID or GID.
BEFORE STARTING: Please note that the Makefile should be run from a temporary directory rather than the target directory. Otherwise some 'mv' commands will produce unexpected results.
For LISTSERV Classic, the two archive files you receive will be called common.tar.Z and either AIX.tar.Z, or SunOS.tar.Z, or Linux.tar.Z, etc... depending on the version of UNIX(R) you are using. The filename is taken from the string returned by the "uname" command on each UNIX(R) platform.
For LISTSERV Lite, you will receive only one archive file, which will be called AIX.tar.Z, or SunOS.tar.Z, orLinux.tar.Z, etc... depending on the version of UNIX(R) you are using. Again, the filename is taken from the string returned by the "uname" command on each UNIX(R) platform. For LISTSERV Lite installations simply ignore further references in this document to common.tar.Z as all of the "common" files are contained in your `uname`.tar.Z file.
Please note that some FTP sites may change the name of the files slightly to adhere to system specific naming conventions. If you're used to dealing with compressed tar files already, then just extract the contents using whatever commands you prefer. If you'd like the sample commands listed below to work as shown, rename the files you received to common.tar.Z and `uname`.tar.Z before continuing. For example, if the system specific file you received is called aix.tar-z, you would enter the command mv aix.tar-z `uname`.tar.Z. Copy or move the two files to a scratch directory first. (The advantage of using a work directory for the installation is that you can easily clean up afterwards.) Once the files have been copied, "cd" to that directory and enter, uncompress *.tar.Z to restore them to their original state. Then enter, tar xf common.tar and tar xf `uname`.tar to unbundle the programs, data files, etc... needed to install LISTSERV. Afterwards you should find the following files have been created in your current directory,
Makefile lcmd.c lsv_amin.c
go license.merge lsv_amin.h
go.sys listview.c sf90m
go.user.sample lsv u-install.memo
home lsv.o wa
and the ./home directory will contain the following files.
aliases.names linkswt2.file listlpun.memo lsvinfo.file
bitearn.nodes listall.refcard listmast.memo peers.names
country.file listcat.file listownr.memo service.names
default.mailtpl listfile.memo listpres.memo site.catalog
default.wwwtpl listjob.memo listqs.memo stdcmd.file
errfac.file listkeyw.memo listserv.memo sysff.file
intpeers.names listkwd.file lsvhelp.file system.catalog
Note however that LISTSERV Lite kits will not contain bitearn.nodes or linkswt2.file as they are not needed for LISTSERV Lite.
Sample commands for this step:
cp common.tar.Z `uname`.tar.Z /tmp/scratch
tar xf common.tar
tar xf `uname`.tar
If you plan to use the precompiled lsv binary, you can skip this section as it uses the defaults for these locations.
Before you can continue with the installation of LISTSERV, you need to choose where you want several things to be placed. The installation process needs the full path names of three directories. All of them are defined by macros in the Makefile (which was extracted from the common.tar archive in the preceding step).
The directory where the mail interface and command line interface programs should be installed is defined by the BINDIR macro. The Makefile is distributed with BINDIR set to /usr/local/bin by default. Whether you choose to use the default directory, or redefine it, the installation procedure assumes the directory already exists. If you choose a new directory, you will need to create it before running the final "make install". This directory is only referenced during the installation of the mail interface. Neither the mail interface program, the command line interface utility, nor the LISTSERV server process requires write access to this directory afterwards.
Incoming mail is written to the directory defined by the LSVSPOOL macro in the Makefile. The default value is $(LSVROOT)/spool. Unlike the BINDIR directory, the LISTSERV spool directory is assumed to be a new directory. In fact, no other users or daemon processes should write to this directory since LISTSERV scans this directory for incoming mail. If the directory doesn't exist when the "make install" command is executed, it will be created, and the LISTSERV account will be made the owner.
The LISTSERV executable, as well as associated directories and data files will be installed in the directory pointed to by the LSVROOT macro in the Makefile. Any directory can be used, so long as LISTSERV has write access to it. When the final "make install" is run, the LSVSPOOL directory, and several subdirectories, will be created if necessary. The LISTSERV account will be made the owner of those directories. The Makefile is distributed with the LSVROOT macro set to /home/listserv. If you choose the default setting, the directories /home/listserv, /home/listserv/home, and /home/listserv/tmp will be created as a result.
To use different directories, edit the Makefile and change the BINDIR, LSVSPOOL, and/or LSVROOT macros.
Documented restriction: Please note that under unix, all files and directory paths accessed by LISTSERV must be in lower case. In other words, you cannot install LISTSERV under the LSVROOT path of /home/users/LISTSERV ; you must use the path /home/users/listserv instead (or in any case, a path that is in lower case).
Sample commands for this step:
If you do not have a compiler (or are planning to use the precompiled binaries in the kit), skip to the section entitled "Using the precompiled binaries".
Note that L-Soft does not necessarily recommend using the precompiled executables if you have a compiler. It is always preferable to compile and link with your own local libraries rather than to assume that ours are the same as yours. However it is not required to do so.
The program that handles incoming mail is called lsv_amin and is distributed in source form. The file lsv_amin.c is a standalone program that can be modified to suit your local mail system as needed. It should work as distributed with unmodified Sendmail systems.
If you are running an older version of ZMailer instead of Sendmail, you must change the value of the Makefile macro LSVAMIN_TYPE from "flags" to "links". This causes LISTSERV to use symbolic links to "lsv_amin" for each LISTSERV e-mail address. Backleveled ZMailer users must choose this option since programs run from ZMAILER "aliases" files can't have arguments. Current versions of ZMailer do not appear to have this restriction.
If you are running PP instead of Sendmail, you can compile the standard mail interface with -DMAIL_PP. To compile lsv_amin, first check the CC and CFLAGS macro in the Makefile to make certain the compiler and options specified are appropriate for your system. Second, if you have enabled the syslog daemon on your system, note that the lsv_amin program logs informational and error level messages using the syslog facility. By default, lsv_amin logs those messages as part of the mail system. That is, LOG_MAIL is used on the openlog() call. If you would prefer to log the LISTSERV mail interface entries separate from the other mail software on your system, edit lsv_amin.h and change the line
#define LOG_FACILITY LOG_MAIL
replacing LOG_MAIL with LOG_LOCAL1, or whatever category is appropriate for your site. If you are using a system on which the openlog() routine only takes two parameters, an older Ultrix system for example, just change LOG_MAIL to 0.
The "lcmd" utility is also distributed in source form. Once you've compiled and installed "lcmd", users can use it to send commands to your LISTSERV server rather than having to use a mail program. Users familiar with the Bitnet version of LISTSERV will find "lcmd" works much like the VM "tell" and JNET "send" commands. The primary differences are that LISTSERV sends back mail in response to commands submitted with "lcmd", and only your local LISTSERV can be reached. In addition to providing a simple command line interface to LISTSERV, sending commands with "lcmd" obviates the need for password validation of protected commands. Since the origin of the command is determined by the username of the person running "lcmd", not by parsing mail headers, password checking can be skipped by LISTSERV. The lcmd.c program should compile without modification. Site specific information needed by "lcmd" will be provided by the Makefile when building the program.
If you have decided to link the lsv.o file and make your own lsv binary, there should be no need to modify anything in the Makefile to perform this step.
Sample commands for this step:
(See the Developer's Guide to LISTSERV for more information on DBMS support.)
LISTSERV 14.5 for unix kits support Oracle, DB2, and MySQL (via unixODBC) in a single, universal kit. This kit contains both a precompiled 'lsv' executable (which does not support any database), and a set of object files allowing you to link a new 'lsv' that supports any combination of databases for which you have a run-time environment on the machine running LISTSERV. The following object files are included:
Main object file for linking 'lsv'
Link with lsv.o to disable OCI (Oracle) support
Link with lsv.o to disable CLI (DB2) support
Link with lsv.o to disable unixODBC (MySQL) support
If a particular database is not available for your operating system, the corresponding noxxx.o file will have been pre-linked into lsv.o and will not be included in the kit.
Note, however, that you may relink LISTSERV with only the following combinations of DBMS support:
· OCI and unixODBC
LISTSERV cannot be relinked with support for both CLI and unixODBC at the same time. This is due to the fact that the two implementations are quite similar and share function names inside LISTSERV.
The current kits contain a revised Makefile which is set up to relink 'lsv' without any DBMS support by default. A new "OS-specific flags" section has been added where you can add or remove DBMS support simply by adding or removing the reference to the appropriate no*.o file. For instance, if you are running Solaris, the default flags line is
CFLAGS_Solaris=nooci.o nocli.o -lsocket -lnsl
If you want to relink 'lsv' with Oracle support, simply change this line to
CFLAGS_Solaris=nocli.o -lsocket -lnsl
If you want to relink 'lsv' with DB2 support, you would change the line to
CFLAGS_Solaris=nooci.o -lsocket -lnsl
Relinking 'lsv' with unixODBC support is not quite as intuitive. You would use the following flags line:
For unixODBC, you must leave CLI support enabled because CLI and unixODBC share internal function names in LISTSERV, as noted above. In addition, you must also link explicitly to the unixODBC library (the -lodbc flag). Please see the Developer's Guide to LISTSERV for more detailed information on configuring unixODBC support.
As noted in the Makefile, Solaris requires that -lsocket and -lnsl must be linked in all cases, so don't remove these references from CFLAGS_Solaris under any circumstances.
The other supported unixes are configured in a similar manner.
PLEASE NOTE CAREFULLY that you should not relink with DBMS support unless you have the appropriate DBMS support (SQL*Net, DB2, unixODBC) installed on your machine. Without this support, the link option will fail.
While you will still want to review the section below on installing LISTSERV's web archive and administration interface, if you want the installation procedure to properly install and set ownership/permissions on the 'wa' executable, you need to provide the path to your cgi-bin directory in the Makefile macro CGIDIR and uncomment that line in the Makefile. By default this installation feature is commented out:
The example setting appears to be a common default for most current Apache versions, but it is your responsibility to ensure that you define the correct directory if you uncomment and use this feature. L-Soft does not recommend taking this default blindly as it may differ on your server.
If you do not uncomment this line, neither 'make install' or 'make update' will try to install 'wa', and you will have to copy it to your cgi-bin directory manually per the instructions below.
Note that this procedure does not attempt to make any directories or files required by the web archive interface. You still need to follow the instructions below to fully install the interface.
(If you are not planning to use the precompiled binaries, please skip to the next section.)
If you do not have a compiler, or if you have just decided to use the precompiled binaries from the kit, you now need to rename the lsv_amin-precompiled binary to lsv_am
in . This will prevent 'make' from trying to call 'cc'.
Please note that there is no precompiled lcmd binary. This is because lcmd requires that the LSVSPOOL directory specification be compiled into it, and there is no way to know ahead of time whether or not your site will be using the defaults. Therefore sites that elect to use the precompiled binaries will not be able to run 'make lcmd'.
If you are using the precompiled binaries because you do not have a compiler, you should move or delete the 'lcmd.c' and 'jobview.c' files from the 'scratch' directory before running 'make install', so that the Makefile doesn't try to compile them and crash because it can't find 'cc'.
Sample commands for this step:
mv lsv_amin-precompiled lsv_amin
If you do not have a compiler:
The command, "make install" will copy the "lsv", "lsv_amin", and "lcmd" programs to the appropriate directories, as specified by the BINDIR and LSVROOT macros in the Makefile. In addition several directories will be created and a number of data files copied to those directories. While there are scenarios in which you can complete this step from the LISTSERV account, in most cases you will need to become "root" to run the "make install" command.
SOLARIS SPECIFIC: When issuing the commands below be sure to follow them exactly. If you issue "su - root" instead of "su root" LISTSERV will be installed but will fail when you attempt to start it.
Sample commands for this step:
LISTSERV needs to know a variety of things about your system, and also how to communicate with the people that will be maintaining the software. All of the settings that you are likely to want to change are defined in the "go.user" shell script, which is created in the LSVROOT directory when you enter "make install". There are a number of environment variables that you can set to reflect things like the Internet domain name of the machine that will be running LISTSERV, the e-mail address of the LISTSERV postmaster, etc... You'll need to edit the go.user file in the LSVROOT directory, and set each of the variables as appropriate. There are comments in the file explaining the purpose of each variable, and we will discuss the basic settings that must be made before you can start the software below.
After 'make install' finishes, it will tell you that you need to chdir into the ~listserv directory and edit the go.user file before you can start the server. You will need to gather some information before you start.
To configure the server, first open LISTSERV's go.user file with any text-based editor (emacs, vi, pico, etc.). There are four basic settings that must be configured before LISTSERV can be run.
Sample commands for this step:
# -- The fully qualified domain name for this host.
The NODE setting is the fully-qualified domain name as registered in DNS for the machine LISTSERV is running on. As noted above, it is possible to insert a square-bracketed dotted-decimal IP address in this box for testing purposes, but L-Soft neither recommends nor supports this in production. This is the host name that LISTSERV will always identify itself with when it sends mail out.
# -- All possible domain names for this machine. SPACE SEPARATED!
It is usually best to leave this set to the default, ie, $NODE, but under some circumstances it may be necessary to deviate from the default.
MYDOMAIN does not refer to your corporate Internet domain. MYDOMAIN is the space-separated list of all possible host names your machine might be known as. In many cases the value of MYDOMAIN is the same as NODE, but for instance some machines running LISTSERV also run the enterprise's World Wide Web server, and may thus be identified in DNS as something like "WWW.EXAMPLE.COM". If you have users who receive mail on this machine, you might also have a DNS record for "MAIL.EXAMPLE.COM" pointing to it. And of course we'll assume that NODE has been set above to something like LISTSERV.MYCOMPANY.COM. Using this as an example, you would set the MYDOMAIN setting to contain, in space-separated format, all of these names that mail might come in to LISTSERV under, with the NODE value coming first:
MYDOMAIN="$NODE WWW.MYCOMPANY.COM MAIL.MYCOMPANY.COM"
This way if someone accidentally writes to LISTSERV@MAIL.EXAMPLE.COM, LISTSERV will recognize MAIL.EXAMPLE.COM as equivalent to LISTSERV.EXAMPLE.COM and will process the mail as if it had been addressed to LISTSERV@LISTSERV.EXAMPLE.COM. Otherwise the mail may bounce as LISTSERV has no other way to know what other names the machine might be known by in DNS.
# -- The e-mail address(es) of the LISTSERV maintainer(s). SPACE SEPARATED!
This is a space-separated list of firstname.lastname@example.org type email addresses belonging to people who have authority to manage LISTSERV--specifically the people who are allowed to create lists, but also who have pretty much global authority on the server to look at lists, modify list headers, and so forth. There are some advanced options for this setting but for right now you will probably just want to insert your own email address so that you can test the server.
Please note carefully that the POSTMASTER should NEVER be LISTSERV@ anywhere or POSTMASTER@ anywhere. These userids are reserved and mean specific things to LISTSERV. If you need to use a generic name for a postmaster account, it is recommended that you use something like "listmaster" or "lstmaint" instead.
# -- The password to be used when sending "put" commands to create files
The password that will be used to create lists and perform certain management functions (such as administering LISTSERV's user password feature). Note that when using the web management features, you do not use the CREATEPW= value, but rather your own personal LISTSERV password, to validate your identity. See the main LISTSERV documentation for information on how to create a personal LISTSERV password.
Please note that the file you need to edit in this step, and the commands you need to issue will require root privileges. Also, while the procedure for manually modifying the sendmail aliases file is described below, you can also enter "make aliases" to have the installation program complete this step automatically. The automated procedure assumes that your sendmail stores aliases in the file /etc/aliases, that the "newaliases" command will rebuild the aliases database, and finally that "kill -HUP `cat /etc/sendmail.pid`" will cause Sendmail to read in the updated alias list. (On some systems this last item is not required as it is taken care of when you run 'newalises'.)
LISTSERV accepts and responds to several e-mail addresses. Even before you setup mailing lists, mail sent to listserv and owner-listserv should be handed to LISTSERV. The link between LISTSERV and your mail system is the lsv_amin program. If you are running Sendmail, the best way to route incoming mail to lsv_amin is by adding entries to your "aliases" file. Refer to the manual pages for sendmail on your system if you are not sure where the alias file is stored. On many systems the file will be called /etc/aliases. Once you have located the file, add the following lines,
listserv: "|/BBB/lsv_amin /SSS listserv"
owner-listserv: "|/BBB/lsv_amin /SSS owner-listserv"
to the file, replacing /BBB with the directory where the lsv_amin program was installed (the BINDIR macro in the Makefile), and replacing /SSS with the LISTSERV spool directory (the LSVSPOOL macro from the Makefile). Other than that, the lines should look exactly like the examples above. The double quotes should be entered into the alias file.
For example, if you changed BINDIR to /usr/lbin, and kept the default LSVSPOOL directory, the new lines in /etc/aliases would look like the following.
listserv: "|/usr/lbin/lsv_amin /home/listserv/spool listserv"
owner-listserv: "|/usr/lbin/lsv_amin /home/listserv/spool owner-listserv"
After updating the alias file, you will need to issue two Sendmail commands. First enter "newaliases" to compile the alias file into the format the sendmail daemon expects. Then on some systems you may also need to direct the sendmail daemon currently running on your system to read the newly compiled list of aliases. Refer to the manual pages for sendmail if you are unsure of how to do so. The command, "kill -HUP `cat /etc/sendmail.pid`" will work on AIX and SunOS systems. If you are running a syslog daemon, sendmail will log the fact that it has loaded the new aliases file. You can check the syslog output after issuing the command to make sure your changes are in place.
Sample commands for this step:
LISTSERV can be used with Wietze Venema's Postfix product, which was designed as an alternative to sendmail. Postfix has a number of advantages, not the least of which is that it is much simpler to configure than sendmail. However, L-Soft does not have any test machines running Postfix and has not run any performance or interoperability tests with Postfix.
In general, the instructions for interfacing LISTSERV with sendmail are all you need to follow for Postfix. It is possible that you may have to modify the ALIASES macro in LISTSERV's Makefile to point to /etc/postfix/aliases instead of the /etc/aliases, depending on how Postfix is installed on your system (a default installation on Red Hat Linux 9.0, for instance, places the alias file in /etc/postfix/aliases). Otherwise, LISTSERV is happy to work with Postfix as a replacement for sendmail.
For more advanced help with postfix, please see http://www.postfix.com/documentation.html . Some large LISTSERV sites are running with postfix and you can probably get help from their admins by joining and writing to the LSTSRV-L mailing list (see the end of this document for information on L-Soft's support mailing lists).
LISTSERV can be used with Dan Bernstein's qmail product. However, L-Soft does not have any test machines running with qmail so the procedure as outlined is based on correspondence with customers who have made this combination work rather than based on tests run on our own systems.
Assuming defaults for everything else, you should include a file called /home/listserv/.qmail that has the following statement in it:
|/var/qmail/bin/preline /usr/local/bin/lsv_amin -s /home/listserv/spool -t listserv
You must also create another file called ~alias/.qmail-default with the following line in it:
|/var/qmail/bin/preline /home/listserv/bin/lsv_amin -s /home/listserv/spool -t $LOCAL
(Note that ~alias is a link to /var/qmail/alias .) This entry "generalizes" the aliases that under sendmail would have to go into /etc/aliases.
For more advanced help with qmail you should contact the appropriate qmail support lists and newsgroups (see http://www.qmail.org/ for the qmail home page). Some large LISTSERV sites are running with qmail and you can probably get help from their admins by joining and writing to the LSTSRV-L mailing list (see the end of this document for information on L-Soft's support mailing lists).
LISTSERV can be used with either of these products. You still need to make the same aliases but since neither Post.Office or Netscape Mail Server use /etc/aliases, the procedure is significantly different. L-Soft does not have any test machines running either of these products so the procedure as outlined is based on correspondence with customers who have made this combination work rather than based on tests run on our own systems.
First, you must make a mailbox (login) for each of the aliases discussed in the previous section.
Next, you must use the mail server's configuration GUI to create "program delivery" aliases for each of the mailboxes you have created in the previous step. The "program delivery" aliases must point to the lsv_amin executable, which is responsible for passing incoming mail to LISTSERV in the correct format.
Note that this procedure is identical for both the server aliases and for the eight aliases that need to be created for each mailing list (see below under "List Creation"). If you are not familiar with "program delivery" and creating aliases under Post.Office or Netscape Mail Server, please consult the documentation for the respective program. L-Soft cannot help you with the configuration of Post.Office or Netscape Mail Server.
Current versions of these products may also require that you configure them so that lsv_amin is known as a "trusted" program. For more information, again please consult the documenentation for the respective program.
If you do change the username under which LISTSERV runs (which for the reason noted above is not recommended by L-Soft), you must make sure that the following points are observed as you work through the installation:
· You must set the LSVNAME macro in the Makefile to the username you have selected.
· If you have a compiler, you must edit lsv_amin.c and change the line
#define LISTSERV "LISTSERV"
#define LISTSERV "USERNAME"
where USERNAME is the username you have selected.
· You must ensure that the lsv_amin mailer, when run, is invoked suid userid, where "userid" is the username LISTSERV is running under. Otherwise mail sent to LISTSERV will be treated as if it were being sent to a list with the name "userid".
· If you do not have a compiler and must use the precompiled lsv_amin executable, you will have to modify the aliases in /etc/aliases that are normally made by the 'make aliases' stage of the Makefile. For instance if you have decided to run LISTSERV under the username 'listmanager', you would have to make the aliases
listmanager: "|/usr/local/bin/lsv_amin -t listserv"
owner-listmanager: "|/usr/local/bin/lsv_amin -t owner-listserv"
In other words, lsv_amin will be invoked suid listmanager but will feed the userid 'listserv' to LISTSERV. Since you cannot change the name used internally by LISTSERV unless you have a compiler, this is required to keep mail to 'listmanager' and 'owner-listmanager' from being treated as list mail rather than administrative mail.
Please note that this step is handled automatically for evaluation kits. The necessary file, called "license.merge", is provided in the common.tar archive and the "make install" command will copy it to the proper directory.
Before you can start up LISTSERV, you will need to install a License Activation Key (LAK) for 'LISTSERV-xxx' (xxx = SUNOS, AIX, BSDI, etc...). In order to offer the same range of services to all LISTSERV sites, regardless of the operating system used, we had to develop our own "license key" scheme. Using system supplied license managers where available and L-Soft LAKs elsewhere would have required us to develop multiple authorization schemes, and would also complicate the task of issuing license keys to customers.
Since the LAK manager is part of LISTSERV, installing the LAK is done last, after all the programs have been built and moved to their proper directories. The process is quite simple, you just create a file called license.merge in the $LSVROOT/home directory and start the LISTSERV server to compile the information. The instructions for doing so are described in the License Registration Form that came with your installation materials.
Once you've customized the "go.user" shell script, you're ready to start LISTSERV. To do so, change your current directory to LSVROOT (as defined in the Makefile) and enter "./go". LISTSERV will print some startup messages, then since this is the first time your server has been run, LISTSERV will generate a number of files needed to route mail. You should see messages similar the ones below.
05 Mar 2002 14:31:12 LISTSERV-TCP/IP for unix version 1.8e starting...
05 Mar 2002 14:31:12 Copyright L-Soft international 1986-2002
05 Mar 2002 14:31:12 SIGNUP files are being compressed...
05 Mar 2002 14:31:12 -> No entry removed.
05 Mar 2002 14:31:13 The network tables are outdated and must be rebuilt.
* Network tables generation process started - be patient...
Currently processed 500 nodes.
Currently processed 1000 nodes.
And once the table generation steps have finished you will see,
* Step 6 complete - link weights file successfully compiled.
* Network tables generation completed successfully.
05 Mar 2002 14:31:19 Nearest backbone host is LISTSERV@PEACH.EASE.LSOFT.COM
05 Mar 2002 14:31:19 Nearest NJE host is LISTSERV@PSUVM
05 Mar 2002 14:31:19 Initialization complete.
which confirms that you've successfully installed the LISTSERV server. To issue LISTSERV commands, press Ctrl-C and you will be prompted to enter a command. You can verify that your customized version of "go.user" was used with the RELEASE command. It will display, among other things, the address(es) of the LISTSERV postmaster(s) you entered in "go.user". If not, then stop the server and make certain that LISTSERV owns the "go.user" file, and that execute permission is set for the file. To stop LISTSERV, hit Ctrl-C then enter "stop".
Once you've verified that your LISTSERV server starts and accepts commands, you should check to make sure the mail interface is working properly. If you stopped LISTSERV, then restart it. After restarting LISTSERV, login to a different username and send mail to the LISTSERV account on your machine. Include one or more LISTSERV commands in the body of the mail message. Since you have yet to define any mailing lists to your server, commands like RELEASE, INFO and THANKS would be good choices. The mail interface notifies the server immediately upon arrival of new mail. So unless your system is heavily used when you try sending the message, a response should arrive within a few moments. If you don't receive mail back from LISTSERV, check for syslog entries generated by the mail interface, lsv_amin. Also, check to see if there are any errors on the terminal/window where you're running LISTSERV. If you started the server with "go bg" check the file "listserv.log" for error messages.
Running LISTSERV in the foreground is primarily useful for debugging purposes only. When running in production, LISTSERV should be run in the background, which also causes a 'listserv.log' file to be generated by redirection of standard output.
To start LISTSERV in the background, issue './go bg' at the shell prompt.
To stop LISTSERV when it is running in the background, you do one of the following:
in the body (not the subject) of the message. This command is validated with the value you have coded into the CREATEPW= go.user variable.
A discussion group for sites that have installed evaluation copies of LISTSERV has been created to facilitate communication between LISTSERV maintainers, list owners and L-Soft support staff. The list is called LSTSRV-E, and you can subscribe by sending mail to LISTSERV@LISTSERV.NET, with the command "SUB LSTSRV-E Your Name" in the body of the mail message. If you have any questions, comments, helpful hints, etc., please post them to LSTSRV-E for distribution to other people participating in the evaluation. Don't forget to mention which version of UNIX(R) you are using when posting. The purpose of the list is to share your experience and problems with other users of evaluation kits. Because there are so many versions and brands of unix, the kits haven't been tested equally on all possible platforms. Knowing which kit you are using will streamline the process of finding an answer to your questions.
NOTE: This section does not apply to evaluation kits or to LISTSERV Lite or Shareware kits. Evaluation copies of LISTSERV should not be registered because they are (presumably) temporary servers running test lists, whose existence should not be broadcast. LISTSERV Lite and Shareware kits are automatically registered via a different process.
Once the server is ready for production use (that is, once you have purchased and installed a permanent License Activation Key, and once you have arranged for LISTSERV to be started automatically when the system boots), you should consider registering it with L-Soft. Registering the server is necessary to broadcast its existence to the other LISTSERV servers and to receive automatic, periodic updates of LISTSERV's networking tables. Once you have registered, your server will also be sent periodic updates about the public lists hosted by other LISTSERV sites, and, similarly, other LISTSERV sites will receive information about the public lists you are hosting. Registration also makes it possible to assign the most efficient DISTRIBUTE routing path for your server.
Please note the following requirements for registration:
L-Soft registers only sites that have unlimited (UNITS=0) licenses or sites licensed for DISTRIBUTE-only use, which are running version 1.8d or higher of LISTSERV Classic or LISTSERV Classic HPO. (Versions prior to 1.8d are not Y2K compliant and therefore sites seeking new LISTSERV registrations must be running the release version of 1.8d or later.)
In order to qualify for registration, a LISTSERV site must also:
· Be running in NETWORKED runmode. If you have RUNMODE=STANDALONE or RUNMODE=TABLELESS in SITE.CFG, you must remove the RUNMODE line (or change it to RUNMODE=NETWORKED) and stop and restart the server before registering.
· Be readily accessible via the Internet by e-mail from outside users.
· Have a name that is unlikely to change any time soon. For instance, LISTSERV.EXAMPLE.ORG, LISTS.EXAMPLE.EDU, and LSV.EXAMPLE.COM are completely acceptable (although we strongly suggest using "LISTSERV" rather than "LISTS" or "LSV", simply because that is what most users are familiar with), whereas something like A8B703A.CC.EXAMPLE.EDU is not. If you are running a test server that you plan to rename later when it goes into production, do not register the server until it is running under its final name. Note also that a hostname containing "LISTSERVE", "LISTSERVER", or any other misspelling of "LISTSERV" is not acceptable.
· Have an A or MX record in DNS corresponding to the value you place in the NODE section (an A record is recommended at minimum).
L-Soft does not register sites running evaluation kits, LISTSERV Lite, or LISTSERV shareware. Requests to register such sites will be discarded.
L-Soft cannot register intranet sites since by definition such sites are not accessible via the Internet. Registration requires that your LISTSERV site be readily accessible via e-mail by outside users.
If your LISTSERV Classic site does not meet the above criteria, there are other options for keeping your LISTSERV networking tables current (which is the most important reason for registering the software). See http://www.lsoft.com/table-updates.html for more information.
You may submit an online registration form at http://www.lsoft.com/regform.html . If there are special considerations for your site that are not covered by the standard form, or if you are unable to access the web site, you can contact email@example.com obtain a registration form. When contacting the site registrar, please tell us what operating system LISTSERV is running under so that we can send you the proper form.
LISTSERV Lite servers are registered automatically when you start the software for the first time. This auto-registration is not optional for Free Edition servers, but may be disabled for non-Free Edition Lite servers by specifying STANDALONE runmode (see "RUNMODE=" in Appendix C of the Site Manager's Operations Guide).
The auto-registration allows you to take part in the global List of Lists and CataList services maintained by L-Soft. Registrations are verified on a regular basis by a central L-Soft server, which sends out several informational commands that return non-privileged information about your server (anyone can issue these commands). Since these registrations are maintained by regular communication with your server, please note that, should you decommission the server, registration verifications will continue to be mailed to your server for several days until the central server decides that your server is actually gone, and not simply unable to receive mail for some reason. Please note carefully that it is not possible for L-Soft to stop these registration queries manually even if you write to us and tell us that the server has been shut down permanently. They will stop after several days without a response.
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. For instance:
mail firstname.lastname@example.org < newlist.create
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 LISTSERV will not create archive directories automatically. You must issue the appropriate "mkdir" command yourself. And when creating such directories, remember that the file permissions must grant the LISTSERV account write access to the directory. Also, directories should be specified as full path names.
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 brand and version of unix you are running!
Following is a sample list header file that can be modified, then cut and pasted into a mail message to be sent to your LISTSERV server. For help with the various header keywords (not all are shown here), please refer to the LISTSERV List Owners Manual.
------------------------------- Cut here --------------------------------
PUT SAMPLE.LIST PW=CCCCCCCC
* Title of sample LISTSERV list
* Review= Public Subscription= Open Send= Public
* Notify= Yes Reply-to= List,Respect Validate= No
* Notebook= Yes,/some/directory,Monthly,Public
* Owner= email@example.com
* PW= XXXXXXXX
------------------------------- Cut here --------------------------------
(If you use this sample, be sure to change "/some/directory" in the Notebook= keyword specification to a directory that actually exists on your machine. Also be sure to put a valid e-mail address in the Owner= keyword.)
Once you have constructed a list header file, and sent it to your LISTSERV, you need to instruct your mail system to route mail for that new list to the LISTSERV mail interface.
(If you are running Software.Com's Post.Office or Netscape Mail Server as your MTA rather than sendmail, please see the section above entitled "Telling Post.Office and Netscape Mail Server about LISTSERV" for specifics on how to create "program delivery" aliases.)
Telling the MTA how to route mail to LISTSERV involves adding entries to your Sendmail aliases file, much like you did when installing the server itself. For each new list, you'll need to add eight entries to the aliases file. The format of those lines is as follows,
NAME: "|/BBB/lsv_amin /SSS NAME"
owner-NAME: "|/BBB/lsv_amin /SSS owner-NAME"
NAME-request: "|/BBB/lsv_amin /SSS NAME-request"
NAME-search-request: "|/BBB/lsv_amin /SSS NAME-search-request"
NAME-server: "|/BBB/lsv_amin /SSS NAME-server"
NAME-signoff-request: "|/BBB/lsv_amin /SSS NAME-signoff-request"
NAME-subscribe-request: "|/BBB/lsv_amin /SSS NAME-subscribe-request"
NAME-unsubscribe-request: "|/BBB/lsv_amin /SSS NAME-unsubscribe-request"
where "NAME" is the name of the mailing list, "/BBB" in the directory where the mail interface was installed (BINDIR in the Makefile), and "/SSS" is the LISTSERV spool directory (LSVSPOOL in the Makefile).
For example, assuming the default values were chosen for BINDIR and LSVSPOOL, and LSVROOT is /home/listserv, the aliases for a new list called "newt" would be,
newt: "|/usr/local/bin/lsv_amin /home/listserv/spool newt"
owner-newt: "|/usr/local/bin/lsv_amin /home/listserv/spool owner-newt"
newt-request: "|/usr/local/bin/lsv_amin /home/listserv/spool newt-request"
newt-search-request: "|/usr/local/bin/lsv_amin /home/listserv/spool newt-search-request"
newt-server: "|/usr/local/bin/lsv_amin home/listserv/spool newt-server"
newt-signoff-request: "|/usr/local/bin/lsv_amin /home/listserv/spool newt-signoff-request"
newt-subscribe-request: "|/usr/local/bin/lsv_amin /home/listserv/spool newt-subscribe-request"
newt-unsubscribe-request: "|/usr/local/bin/lsv_amin /home/listserv/spool newt-unsubscribe-request"
(Note that /etc/aliases does not use line continuation characters and will not operate properly unless each alias is on a line by itself. Thus, all of the aliases above should be on a single physical line, and never wrapped.)
Once you've added the new aliases to the file, you need to issue the "newaliases" command and send your Sendmail daemon a hangup (HUP) signal before they will take effect.
As with the earlier step where adding mail aliases was necessary, the commands documented above can be automatically invoked by using the "make" command. If you system stores aliases in /etc/aliases, and the newaliases command can be used to compile that file, and if the command "kill -HUP `cat /etc/aliases`" will cause your Sendmail to reload the alias file, then the automated method should work. To add the mail aliases for a new list, and to direct your Sendmail to use those new aliases immediately, enter "make list name=XXX" where "XXX" is the name of the new list.
While there is no LISTSERV command to delete a list, the procedure is quite simple. Log in to the listserv account (or any other account with privileges in LISTSERV's directories, e.g., root), copy or archive any files (list archives, etc.) that you want to keep to a safe place, and then use the Unix 'rm' command to delete the list file. For instance, if you are deleting a list called 'test.list', simply 'rm test.list' from the LISTSERV 'home' directory (by the Makefile default, this directory is /home/listserv/home). Optionally you may also remove the Sendmail aliases from /etc/aliases, but once the '.list' file is gone, it has been deleted as far as LISTSERV is concerned.
VM lists can be migrated to unix with a much simpler procedure:
A. Stop LISTSERV on unix, and go to its /home directory.
B. FTP a copy of the xxxx.LIST file from the VM system, in ASCII mode. Note that you must grab the file as it appears on the VM server's "A-disk". If you send a REVIEW command to the VM LISTSERV, you may be sent a file called xxxx.LIST, but it is not suitable for migration: among other things, it will not list subscribers with the "conceal" flag.
C. If the list is archived, edit the xxxx.LIST file (which is an ordinary text file) to insert a suitable directory name in the "Notebook=" keyword (see example above). Do not modify the lines with subscriber names! The only lines you may edit at this stage are the ones starting with an asterisk.
D. Start the unix LISTSERV. It will issue a warning about incorrect list format, and automatically convert it to the format used on unix.
You can also FTP the archive files (xxxx.LOGyymm) directly to the directory selected in point C.
The "go" shell script can be called from an inittab entry if you would like LISTSERV to be started whenever your system is rebooted. If you choose to treat LISTSERV like other daemon processes, it is advisable to redirect the standard output of the "go" script to a file. Otherwise, information needed to track and resolve problems will not be available for reference. In order to do this, you should start the server with the command "go bg". The "bg", or "background", option will redirect LISTSERV's informational and error messages to a file called "listserv.log" in the LSVROOT directory. By way of example, here is the inittab entry used on one of the L-Soft development machines (this one happens to be a Linux machine):
ls:235:once:/home/listserv/go bg >/dev/console 2>&1
Please note that this method may not work if you don't have sh as the default shell for 'listserv'. You also need to ensure that the default runlevel for the machine is specified in the inittab entry.
Please refer to the manual pages for init and inittab on your system for specific information on how such mechanisms work on your version of UNIX(R).
There are three file server systems currently in use or under development for LISTSERV:
The VM (mainframe) version of LISTSERV continues to support the "traditional" file server system. While it is very powerful, this file server system dates back to 1986 and suffers from a few annoying limitations. In addition, it is written in a non portable language. This will be replaced eventually with the "new" file server system, currently under development.
The non-VM versions of LISTSERV 1.8d and later enhance further the new file server system introduced in non-VM 1.8c, which includes most of the functionality of the "traditional" file system. Notably, GIVE and file "packages" are now available. Most end user commands will continue to work as before. However, there is no guarantee that the internal data files manipulated by the file server functions will remain as before. Note that SITE.CATALOG files from versions 1.8a through 1.8c are still supported and will not need to be changed in order to work with 1.8d and later.
The non-VM versions of LISTSERV 1.8a and 1.8b supported a "temporary" file server system, to provide an interim solution while the new system was being developed. This temporary system only supports a subset of the functions of the traditional system. This system is no longer supported by L-Soft as it has been superseded by the new non-VM file server referenced above.
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 (VM) system, you create files called "listname 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 LISTSERV "home" directory (by the Makefile default, this directory is LSVROOT/home). You create files called listname.catalog and register them in site.catalog in order to provide access to them. Please be aware that there are major differences between the way files are registered on VM and workstation systems as many list owners use (or are used to) a VM server with different conventions.
To register a new file to the server, you add a line to the "site.catalog" file in the LSVROOT/home directory (create "site.catalog" if it does not exist; L-Soft does not ship it with the software). Do not modify the "system.catalog" file, as it is part of LISTSERV and may be replaced when you apply software updates; however, site.catalog is formatted identically to system.catalog. Here is what a typical "site.catalog" entry for a file looks like:
MY.FILE /aaa/bbb/my.file 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 is case-insensitive and must contain one and only one period (in other words, all files served by LISTSERV must have a file name and file extension separated by a "." character). It is recommended that this identifier consist of a filename of no more than 13 characters and a file extension of no more than 15 characters. For instance
VERYLONGFILENAME.VERYLONGFILEEXTENSION /aaa/bbb/my.file XXX YYY
will work, but the display of this name in the output of an INDEX command will look like this:
* filename filetype GET PUT -fm lrecl nrecs date time
* -------- -------- --- --- --- ----- ----- ---------- --------
TEST CATALOG ALL OWN V 73 6 1998-02-18 11:18:31
VERYLONGFILENAME VERYLONGFILEEXTENSION ALL CTL V 39 3 1998-04-09 08:48:25
PEERS NAMES ALL LMC V 108 1681 1998-01-13 20:01:20
The second item, "/aaa/bbb/my.file", is the name LISTSERV will use for the actual UNIX file. 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. This item should be typed in lower case.
Note: if you are upgrading from LISTSERV 1.8a or 1.8b to 14.4, the preceding represents a change in the format of site.catalog entries. For compatibility, the old style entries are also acceptable.
Note that if you are not creating special subdirectories for file archives and they will reside in the LSVROOT/home directory, you can simplify the site.catalog entry by using "A" instead of the full path, e.g.:
MY.FILE my.file.A XXX YYY
If you are running a large production server, however, this is not advised; it is much better to create separate directories for each list and put archive files belonging to each list in those directories rather than to store them all in the LSVROOT/home directory.
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:
· ALL: universal access.
· CTL: LISTSERV administrator only.
· 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@host: the 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 /pub/my.file 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.
NOTE CAREFULLY that you cannot use the VM-specific FAC codes PRV or OWN under the unix version of LISTSERV. You MUST use the PRIVATE(xxx) or OWNER(xxx) FACs from the list above (and you MUST specify the listname) or the outcome will not be what you expect.
IMPORTANT: LISTSERV does not set file protections to ensure that only the people listed are allowed to access the files. These attributes apply to LISTSERV commands (GET, PUT, INDEX) only; it is your responsibility to protect the actual UNIX file and parent directory by setting the file protections and/or ownership (UID and GID) to prevent unwanted access by local users. Please keep in mind that the LISTSERV username must be able to read the files it is to distribute to people, and it must have read/write access to files you want people to be able to update via PUT commands.
For more information on running the LISTSERV file archive server on your machine, including how to set up sub-catalogs, please consult chapter 8 of the Site Manager's Operations Manual for LISTSERV, available from L-Soft's ftp and World Wide Web sites.
The `uname`.tar.Z archive (or for LISTSERV Lite, the `uname`-Lite.tar.Z archive) contains a little executable called 'sf90m'. This executable is provided by L-Soft as a convenience to sites that wish to compare delivery times between sendmail and (typically) L-Soft's LSMTP(R) product. 'sf90m' is meant to be run against your sendmail log and produces a small table of delivery times. The syntax is simply 'sf90m sendmail_logname', where sendmail_logname is the full path and name of the log file that contains sendmail log entries. On some systems this may be the syslog; on others it may be a file called 'messages'. Typically this file is found in /var/log/ or similar.
There is no support for 'sf90m'; it is provided only as a convenience, and is documented here only because so many people have asked about it.
This section assumes you are using sendmail as your MTA.
· Create a listserv account on your system.
· Make a temporary directory, say /tmp/lsvinst or whatever is convenient.
· Copy the files, common.tar.Z and `uname`.tar.Z to that directory, uncompress and untar them.
· Edit the Makefile (if necessary), changing the BINDIR, LSVROOT and LSVSPOOL macros to point to the appropriate directories.
· Enter "make mailer" to compile the sendmail interface, "lsv_amin", and enter "make lcmd" to build the command interface utility "lcmd". If you don't want to use the precompiled lsv binary, enter "make server" to make the LISTSERV server "lsv". You can make all three of them with "make all" if you prefer.
· Copy the file go.user.sample to go.user, edit go.user, and set the environment variables as directed by the comments in the file.
· Enter "make install" to create the LISTSERV work directory and spool directory, copy "lsv" and the data files in the "home" directory to wherever you defined LSVROOT, and also to copy "lsv_amin" to the BINDIR directory.
· Add the lines,
listserv: "|/BBB/lsv_amin /SSS listserv"
owner-listserv: "|/BBB/lsv_amin /SSS owner-listserv"
(where /BBB is the BINDIR directory, and /SSS is the LSVSPOOL directory) to your sendmail aliases file. Then rebuild the aliases and send the appropriate signal to your sendmail daemon to load the new aliases.
· Delete all the files in /tmp/lsvinst (or whatever you called the work space in step 1). All the files needed to run LISTSERV have been copied to either LSVROOT or BINDIR already, so there's no need to keep anything that's left in the work directory.
· Follow the instructions in the License Registration Form you received with your installation materials to install your License Access Key (LAK). If you are installing an evaluation copy of LISTSERV, this step is handled automatically by the "make install" command listed above.
· Ensure that you have set file and directory permissions in such a way that lsv_amin and the 'listserv' user have read/write/execute authority where needed. This is the most common problem reported by evaluation kit users.
· To start the LISTSERV server, change directories to LSVROOT and enter either "go" to run the server with output logged to the terminal, or "go bg" to run in the background with the log written to listserv.log in the LSVROOT directory.
· Test the server by sending mail to "listserv" from any account other than "listserv" itself with some command in the body of the mail message. Since you haven't defined any mailing lists yet, commands that don't requires lists, like INFO, RELEASE or even THANKS commands might be best.
· Subscribe to the LSTSRV-E mailing list by sending the command "SUB LSTSRV-E Your Name", in the body of a mail message, to LISTSERV@LISTSERV.NET.
· Once you've tested your server sufficiently, fill out the sample registration form given in the "Register your Server" section and return it to L-Soft. Please note that if you are installing an evaluation copy of LISTSERV you should skip this step.
If all went well, you're ready to add mailing lists to your server. Please refer to the "List creation" section of this guide for instructions on how to do so.
1. Copy the 'wa' executable from your source scratch directory to the CGI script directory for your web server. You can call it something else, but a short name will help keep the HTML documents small! Note that you need to make 'wa' run suid listserv in order to allow it to access LISTSERV archive files (the correct permissions for 'wa' should be 4755 and it should be owned by 'listserv'). (See above for instructions on how to do this automatically at install time.)
2. Create a subdirectory on your web server to contain the various files LISTSERV will be creating. You should not use your main directory as LISTSERV will create quite a few files! The suggested name is 'archives'. This directory must be rwx accessible by the 'listserv' user.
3. Create a
world-readable file called /etc/lsv-wa.config with the
following two statements:
where 'xxx' is the absolute path to the directory you've just created and 'yyy' is the URL to this directory (preferably relative). For instance:
4. Modify LISTSERV's configuration to add two variables, as follows:
· WWW_ARCHIVE_CGI is the relative URL that leads to the CGI script you have just installed. Typically this will be something like '/cgi-bin/wa' or '/scripts/wa'. This is a URL, not an OS path name.
· WWW_ARCHIVE_DIR is the full path name to the directory you created in step 3.
· Under unix, don't forget to export! Add
at the end of your go.user file before you save it.
5. For each list that you want accessible through the web interface, you must create a subdirectory in the directory you created in step 3, named like the list. For instance, if you create 'archives/xyz-l', the list XYZ-L will be accessible through the interface. Note that only lists with public archives are ever made accessible, for security reasons.
Next, restart LISTSERV. It should create a file accessible with the URL http://localhost/archives/index.html, and from there you should be able to access all the postings.
Complete information on installing the Web Archive Interface is contained in chapter 5 of the Site Manager's Operations Manual.
Please note that this feature is not available under LISTSERV Lite.
Please note that the anti-virus scanning software is available only for Windows NT/2000/XP and Linux-x86, and that this feature is only available for LISTSERV Classic or LISTSERV Classic HPO sites running those operating systems. An L-Soft maintenance contract is also required.
LISTSERV Version 14.4 supports on-the-fly anti-virus scanning of all messages sent to mailing lists that run under LISTSERV Classic or LISTSERV Classic HPO on Windows 2000/2003/XP and Linux-x86 servers, including inline uuencoded binaries and MIME attachments in those messages. This is a value-added feature which, in addition to a regularly-licensed LISTSERV Classic or LISTSERV Classic-HPO installation, requires the following:
The table below indicates the web sites for F-Secure downloads.
NOTICE: Use of FSAV 4.64 requires, at minimum, LISTSERV version 14.3. Issue a SHOW LICENSE command to LISTSERV to ascertain your product level BEFORE upgrading or installing FSAV 4.64. The current LISTSERV for Linux-Intel kit can be downloaded at http://www.lsoft.com/download/listserv.asp#unix .
In the United States:
FSAV 4.64 for Linux Servers
FSAV 4.64 for Linux Servers
F-Secure Anti-Virus 4 documentation:
In order to use LISTSERV’s Anti-Virus features, F-Secure® Anti-Virus must be installed on the same server as LISTSERV®. If you already have F-Secure Anti-Virus installed on the server, you should make sure that you are running the version supported by LISTSERV, or higher:
· For Linux-x86: version 4.64
If you are running an older version, you must upgrade to the supported version. (See below for upgrade instructions!)
The FSAV key provided by L-Soft is for a single stand-alone server only. If you wish to run the Enterprise edition of F-Secure Anti-Virus, this can be purchased separately, and it will still work with LISTSERV.
The FSAV key provided by L-Soft is valid only as long as you keep up paid maintenance for LISTSERV. If you discontinue LISTSERV maintenance, you must uninstall F-Secure Anti‑Virus or purchase a separate key from F-Secure.
Due to significant non-backwardly-compatible changes made by F-Secure in FSAV 4.5x and later, you MUST upgrade your LISTSERV 1.8e for Linux installation to at least version 14.3 before upgrading to FSAV 4.64. If you do not know if you have version 14.3 or later installed, please issue a SHOW VERSION command to LISTSERV.
F-Secure Anti-Virus for Linux 4.15 and earlier cannot be upgraded. You will need to manually remove the previous version and configuration data before installing this version.
You can uninstall the previous version as follows:
1. Remove the fsavd daemon's service definition by issuing the shell command `chkconfig -del fsavd'. Optionally, delete the fsavd script from /etc/init.d.
2. Remove the installation directory /usr/local/fsav, the configuration file /etc/fsav.conf , the symbolic link to the binary /usr/local/bin/fsav and the symbolic link to the manual page /usr/local/man/man1/fsav.1 .
3. Remove the crontab entry that runs the hourly AV signature update.
If you happen to be running FSAV 4.50 or later (which is unlikely unless you were a beta site, as no later version than 4.15 was ever certified to work with LISTSERV), these versions may be upgraded with the FSAV 4.64 kit. Simply run it as noted below.
F-Secure Anti-Virus Installation Instructions
Before starting to install FSAV, make sure that you have your FSAV installation key from your sales representative. The FSAV key is sent with your LISTSERV LAK(s).
zcat fsav-srv-4.64.4330-lsoft.tar.gz | tar xvf -
This leaves the following files:
readme.html (this file)
tar xvf fsav-srv-4.64.4330.tar
This creates a subdirectory called fsav-srv-4.64. Change into that directory, where you will find (among other things) a file called 'fsav-srv.4.64.4330' which should have execute permission. (If it does not, chmod it appropriately.)
[root@rerun fsav-srv-4.64]# ./fsav-srv-4.64.4330
F-Secure Anti-Virus for Linux Servers installation
Copyright (c) 1999-2004 F-Secure Corporation. All Rights Reserved.
We will now ask you some questions regarding the installation of this product.
A default value will be shown in square brackets after the question. To accept
the default, just press enter.
To install F-Secure Anti-Virus, enter the keycode you have received with your purchase or press enter to install evaluation version.
[Beginning of FSAV installation script]
Key accepted. Decrypting...done.
Now unpacking files to /opt/f-secure/fsav...
Full F-Secure Anti-Virus for Linux Servers version installed.
Created configuration file /etc/opt/f-secure/fsav//fsav.conf.
Program executables are usually located in designated directories,
which are listed in PATH environment variable. You can create symbolic link
form /opt/f-secure/fsav/bin/fsav to /usr/bin/ to achieve that.
Would you like to create the symbolic link [yes]?
Ok, link created.
Manual pages are located in certain directories. You can have
F-Secure Anti-Virus for Linux Servers manual pages in appropriate
place by creating symbolic links.
Would you like to create the symbolic links to /usr/share/man [yes]?
Ok, link created.
Ok, link created.
Ok, link created.
Ok, link created.
Ok, link created.
Ok, link created.
F-Secure Anti-Virus automatic scan and update scheduler
Copyright (c) 1999-2004 F-Secure Corporation. All Rights Reserved.
This program will schedule automatic virus scans and updates of the
F-Secure Anti-Virus virus database using the cron facility. We will now ask
you some questions about running these processes. A default value will be
shown in square brackets after the question. To accept the default,
just press enter.
Would you like to schedule an automatic database update [yes]?
How often would you like updates to be performed (hourly/daily) [hourly]?
Would you like to schedule an automatic virus scan [no]?
Not scheduling an automatic virus scan.
Succesfully scheduled a database update.
If for some reason you wish to disable automatic runs, run the command
crontab -e. This will bring up your current crontab in an editor.
Then remove the following line from the file and save it:
41 * * * * /opt/f-secure/fsav/bin/dbupdate
Would you like to check for updates for this product now [yes]?
F-Secure Anti-Virus for Linux
F-Secure Virus Description Database Update
Copyright (c) 2002-2004 F-Secure Corporation. All Rights Reserved.
Fetching update from F-Secure's web site to /var/opt/f-secure/fsav/update
Updated database files in /var/opt/f-secure/fsav/update from F-Secure's web site.
Databases in /var/opt/f-secure/fsav/update are valid.
Databases updated successfully.
Would you like to run a virus scan now [no]?
Installation completed successfully.
Please run "fsav --help" for usage instructions.
The manual pages for fsav, fsavd, fsav.conf, fsavschedule and
dbupdate are available using "man" command.
[End of FSAV installation script]
Upgrading LISTSERV is almost as simple as installing it.
If you already have a LISTSERV 14.5 LAK installed (issue a SHOW LICENSE command if you are not sure), skip directly to step 1, below.
You must obtain and install a LISTSERV version 14.5 product LAK prior to upgrading your server, or LISTSERV will not start after the upgrade.
If you have received a new LAK but not yet installed it, first, install the new LAK onto your old installation, following the instructions that come with the LAK. Send LISTSERV a "SHOW LICENSE" command after restarting LISTSERV to ensure that the new LAK has been installed properly.
Now you are ready to upgrade the server itself.
Get the current unix
evaluation kit (or Lite kit, depending on your installation) for your brand of
LISTSERV Classic: Point your browser to http://www.lsoft.com/download/listserv.asp#unix .
LISTSERV Lite: Point your browser to http://www.lsoft.com/download/listservlite.asp#unix
In both cases, follow the registration instructions and download the file into a scratch directory. Note that the LISTSERV Classic evaluation kits are production code limited only by an evaluation LAK, which your production LAK will override.
2. Back up the entire LISTSERV directory hierarchy (just in case).
3. Stop LISTSERV. If you have LISTSERV set up to respawn itself, be sure to bring LISTSERV to a complete stop.
4. Per the installation instructions above, login as (or su) 'root', uncompress and untar the file(s) into a scratch directory, and then edit the Makefile so that it contains the correct values for your installation. Then, run the update stage of the Makefile by issuing the command 'make update' . This will update all files (including the executables) that have changed from the previous version. Please note that your local settings, lists, archives, and so forth will be preserved. If you have a compiler, note that you should delete or rename the precompiled 'lsv' executable before running 'make update' so that it can be relinked locally.
5. If you have the web archive interface installed, copy 'wa' from the scratch directory to your cgi-bin directory to update it. Currently the Makefile will not do this for you. Be sure that 'wa' has permissions 4755 and is owned by 'listserv'.
6. Restart LISTSERV and send a command to make sure the installation was successful.
Note: The standard LISTSERV Classic and Lite kits for unix are binary installers that are designed to simplify the installation process. If upgrading a LISTSERV Classic installation, or going from LISTSERV Lite to LISTSERV Classic, you may choose to download the old 'tar.Z' installation kits instead. If so, be sure to download common.tar.Z as well as the `uname`.tar.Z. This is very important as the common files also change from version to version.
LISTSERV Lite installations should always be updated from the standard ".bin" kits.
At http://www.lsoft.com/lsv-faq.html we've attempted to document a few of the most frequently-asked questions pertaining to installing and running a LISTSERV server. Before writing to our support department for problem resolution, please take a moment to read through the online FAQ and see if your problem is answered there.
L-Soft recognizes that the FAQ pages are not going to solve every problem you may face. We are always willing to help diagnose and correct problems you may be having with your registered LISTSERV® server. To that end, please note the following when you write to L-Soft with a problem report:
1. Please make the subject line of your report indicative of the problem, and in particular the product with which you are having a problem. A subject like "Problem posting to moderated LISTSERV list" is much more useful to us than "Help me please!"
2. Include any appropriate log entries. LISTSERV keeps logs of everything it does when you are running it in the background (i.e., with './go bg', and without a log excerpt it is often impossible to determine what caused a given error.
3. If LISTSERV dumps core, please run the debugger on the core file (see FAQ 1.3. in the LISTSERV maintainer's support FAQ) and include the results.
4. Always send a copy of your site configuration file (with the passwords XXX'ed out).
5. Send along anything else that you think might be helpful in diagnosing the problem.
If you are running an evaluation version of our software, please join the evaluation users' list,
LSTSRV-E@PEACH.EASE.LSOFT.COM, and send your trouble reports there.
If you are running LISTSERV Lite, please join the LISTSERV-LITE mailing list,
LISTSERV-LITE@PEACH.EASE.LSOFT.COM, and send your trouble reports there.
If your LISTSERV Classic server is registered and has paid-up maintenance, you may send problems to SUPPORT@LSOFT.COM for a quick reply.
You should be aware that there are several documentation files included with LISTSERV. They are located in the ~listserv/home directory by default and include the following:
listserv.memo A General Introduction to LISTSERV
listpres.memo A presentation of LISTSERV for the general user
listownr.memo A List Owner's Manual for LISTSERV
listkeyw.memo A manual of the various list header keywords and what they do
listall.refcard A quick reference card for LISTSERV commands
All of L-Soft's formal documentation for LISTSERV is available at http://www.lsoft.com/manuals .
There are several mailing lists dedicated to the support of LISTSERV.
for LISTSERV maintainers and interested list owners
for LISTSERV list owners
for LISTSERV evaluation kit users
for LSMTP users
for LISTSERV Lite users
for third-party developers using features documented in the Developer's Guide to LISTSERV
To subscribe to any of these lists, send mail to LISTSERV@PEACH.EASE.LSOFT.COM with the following command in the body of the message:
SUBSCRIBE listname Your Name
LISTSERV is a registered trademark licensed to L-Soft
LSMTP is a registered trademark of L-Soft international, Inc.
ListPlex is a registered service mark of L-Soft international, Inc.
EASE and CATALIST are service marks of L-Soft international, Inc.
L-SOFT is a trademark of L-Soft international.
All other trademarks, both marked and not marked, are the property of their respective owners.