![[LISTSERV logo]](../images/LISTSERV-generic.gif)
![[Online documentation]](../images/HDR-doc.gif)
|
|
|
L-Soft international, Inc.
Site Manager's Operations Manual
for
LISTSERV®, version 1.8c
April 8, 1997
Revision 1
r970408-001
The reference number of this document is 9704-UD-03.
Defining site configuration keyword values
==========================================
The syntax used to define these values differs from platform to platform.
All examples in this reference guide are for VM unless the keyword is
specifically not available under VM. A syntax guide follows:
VM
========================
KEYWORD='somevalue'
For substitutions, follow the REXX language syntax. For instance,
MAILER='mailer@'NODE
MYDOMAIN=NODE 'some.host.com'
VMS
========================
VMS users should use the LISTSERV_CONFIGURE.COM application, provided
with the software, to modify the site configuration file, rather than
editing it by hand.
Unix (all)
========================
KEYWORD="somevalue"
For substitutions, follow this example:
MYDOMAIN="$NODE some.host.com"
Note that under unix, you must also export all site configuration
variables before they will work.
Windows (all)
========================
Windows users should use the SITE.EXE application, provided with the
software, to modify the site configuration file, rather than editing it
by hand. However, it is possible to edit the file by hand if necessary.
KEYWORD=somevalue
For substitutions, follow this example:
MYDOMAIN=%NODE% some.host.com
Note for all platforms
======================
Whenever you change the contents of the site configuration file, you must
stop and restart the LISTSERV server before the changes will take effect.
Windows sites using the SMTPL.EXE "listener" should also stop and restart
the listener as some changes will affect it as well.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
BITNET_ROUTE
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
Defines the Internet hostname of a machine that will be used to route
mail to BITNET addresses. If your organization is connected to BITNET,
you may want to use the hostname of your main BITNET system for best
turnaround time. Otherwise the default value is suitable.
Example
=======
BITNET_ROUTE= 'BITMAIL.LSOFT.COM'
Default Value
=============
If not explicitly defined, this keyword defaults to BITMAIL.LSOFT.COM.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
CHECKMDISK
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
VM
Abstract
========
Defines the list of library minidisks to be checked at startup.
Example
=======
CHECKMDISK= '191 192'
Details
=======
This parameter defines the LISTSERV "library" minidisks, i.e., minidisks
on which LISTSERV might have to read or write list archives or library
files (as opposed to "system" files like PROFILE EXEC or DATABASE FILE
which are manipulated by LISTSERV but are not apparent to the users).
Default Value
=============
None. This parameter must be set explicitly.
Wildcards
=========
Not allowed.
See also
========
MDISK.cuu
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
CMSNAME
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
VM
Abstract
========
The name of the CMS system to be used on IPL commands.
Example
=======
CMSNAME= 'CMS'
Details
=======
This parameter defines the LISTSERV "library" minidisks, i.e., minidisks
on which LISTSERV might have to read or write list archives or library
files (as opposed to "system" files like PROFILE EXEC or DATABASE FILE
which are manipulated by LISTSERV but are not apparent to the users).
Default Value
=============
The standard value for your system.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
CREATEPW
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
Defines the password used to validate the creation of new lists.
Example
=======
CREATEPW= 'SECRET'
Default Value
=============
None. This parameter must be set explicitly.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
DATABASE
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
VM
Abstract
========
Boolean value that determines whether or not the database functions are
enabled. 0= no, 1= yes.
Example
=======
DATABASE= 0
Default Value
=============
DATABASE= 1
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
DBRINDEX
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
Non-VM
Abstract
========
Determines whether or not LISTSERV's database functions use reverse
indexing. Please see the 1.8c release notes for a full discussion of
whether or not you should use reverse indexing.
Example
=======
DBRINDEX= 0
Default Value
=============
For VM and VMS: DBRINDEX= 0
For unix and Windows: DBRINDEX= 1
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
DEFAULT_SPLIT
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
Provides a default value for the "SPLIT=" command line keyword, causing
files ordered through the GET command to be automatically split into
smaller "chunks". This option can be useful if LISTSERV is behind a
firewall or other central mail gateway with an unusually low maximum
message size limit. Unit: kilobytes.
Example
=======
DEFAULT_SPLIT= 250
Default Value
=============
Not set - messages are not split unless specifically requested by the
user.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
DELAY
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
VM
Abstract
========
The delay between two reader-scan operations. Increasing it will reduce
CPU time consumption but will increase response time.
Example
=======
DELAY= 250
Default Value
=============
Standard value.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
DIAGD4
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
VM
Abstract
========
Indicates whether LISTSERV should use diagnose X'D4' to mimic the RSCS
origin on files it DISTRIBUTEs. Boolean value. Requires VM/SP release 5
and privilege class B.
Example
=======
DIAGD4= 1
Default Value
=============
DIAGD4= 0
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
FILEDISK
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
VM
Abstract
========
The filemode of the DEFAULT disk to be used for storing files with a PUT
command.
Example
=======
FILEDISK= 'L5'
Default Value
=============
FILEDISK= 'A5'
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
FILEMAXL
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
VM
Abstract
========
The maximum number of lines for any incoming non-mail file to be
accepted.
Example
=======
FILEMAXL= 10000
Default Value
=============
Standard value.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
FILTER_ALSO
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
Blank-delimited list of problem users who should not be allowed to post
or subscribe to any list. This is similar to the "Filter=" list header
keyword, but applies to all the lists. The FILTER_ALSO option is usually
used to filter out problematic mail gateways, anonymous remailers (if
anonymous postings are not desired), troublesome users, etc. Please refer
to the list owner's guide for more information.
Example
=======
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
FILTER_ALSO= '*@BADNODE.COM OBNOXUSR@SOMEHOST.NET'
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Details
=======
Sometimes it may be necessary to deny a specific user (or a class of
users) access to all the lists hosted by your server. This may be due to
policies internal to your organization, technical problems, or simply to
lock out an obnoxious user. FILTER_ALSO adds to the standard LISTSERV
filter and denies access to all lists on the server.
Default Value
=============
Not set; adds to LISTSERV's built-in filter.
Wildcards
=========
Allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
FIOC_TARGET
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
Defines the "target size" for LISTSERV's file cache (in kilobytes). You
normally set this option through the various "Optimize for..." buttons in
the LISTSERV configuration program. See the LISTSERV Tuning Guide
(available from L-Soft at no extra charge) for more information.
Example
=======
FIOC_TARGET=15000
Details
=======
One of three variables that control how LISTSERV handles its built-in
data cache. FIOC_TARGET is the "target size" for the cache. LISTSERV will
strive to keep the cache to about that size, but will allow it to grow
past this value for short periods of time. LISTSERV expects that it will
have fast access (low paging rate) to these FIOC_TARGET kilobytes of
cache memory; it does not help to increase this value if your system is
memory-constrained.
Default Value
=============
System dependent.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
FIOC_TRIM
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
Defines the threshold (in kilobytes) where LISTSERV should start
aggressively trimming the cache. You normally set this option through the
various "Optimize for..." buttons in the LISTSERV configuration program.
See the LISTSERV Tuning Guide (available from L-Soft at no extra charge)
for more information.
Example
=======
FIOC_TRIM=17000
Details
=======
One of three variables that control how LISTSERV handles its cache.
FIOC_TRIM is the point at which LISTSERV should start aggressively
trimming the cache in order to free up virtual storage. Typically this
value should be set to FIOC_TARGET plus 20% or 512KB (whichever is
larger).
Default Value
=============
System dependent.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
FIOC_WARNING
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
Defines the cache size (in kilobytes) at which LISTSERV should write a
warning to the console log. You normally set this option through the
various "Optimize for..." buttons in the LISTSERV configuration program.
See the LISTSERV Tuning Guide (available from L-Soft at no extra charge)
for more information.
Example
=======
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
FIOC_WARNING=20000
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Details
=======
One of three variables that control how LISTSERV handles its cache. Under
certain circumstances, LISTSERV may not be able to trim the cache right
away, either because a cache entry is locked by a routine that maintains
pointers to it or because the file is currently open and thus it would be
counter-productive to flush the cache entry right away. In such cases,
the cache size can continue to grow past FIOC_TRIM. When it reaches
FIOC_WARNING, a warning is displayed on the LISTSERV log. This probably
indicates a programming error, or a value of FIOC_TARGET which is
significantly below the "correct" value for your workload. Typically this
value should be set to FIOC_TARGET plus 75% or 1MB (whichever is larger).
Default Value
=============
System dependent.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
GETQWAIVE
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
VM
Abstract
========
Internet addresses (space-delimited) of persons to be granted an
"infinite" GET quota.
Example
=======
GETQWAIVE= 'nathan@lsoft.com holly@iupui.edu lowell@ubvm.bitnet'
Default Value
=============
Empty string.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IGNORE
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
VM
Abstract
========
A list of Internet addresses (space-delimited) whose messages and files
are to be ignored. Usually these are addresses that generate
auto-responses that should simply be discarded.
Example
=======
IGNORE= 'response@* dirmaint@'node 'reslim@'node
Default Value
=============
Empty string.
Wildcards
=========
Allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
INDEX_VIA_GETPOST
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
VM only
Abstract
========
Starting with 1.8c, the INDEX subscription option now uses the GETPOST
command rather than a database job by default. INDEX_VIA_GETPOST can be
used to control this default.
Example
=======
INDEX_VIA_GETPOST= 0
Details
=======
This change was made because the GETPOST command requires fewer resources
and is easier to use for non-technical users. Users may of course
continue to use their old database jobs to access the list archives. The
old behavior can be restored by adding 'INDEX_VIA_GETPOST= 0' to LOCAL
SYSVARS.
Default Value
=============
INDEX_VIA_GETPOST= 1
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
INSTPW
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
VM-NJE only
Abstract
========
The optional local "installation password" associated with the INSTALL
command.
Example
=======
INSTPW= 'fixmelater'
Details
=======
When INSTPW is set to '', it indicates that there is no local password
and that only the global password is required to install automatic
shipments. The server can then be updated by the LISTSERV Master
Coordinator without requiring any intervention by the local operation
staff (provided that this has not been disabled from the LSV$INST EXEC
user exit). A non-null value indicates that the installation of each
shipment must be confirmed by means of an "INSTALL PASSWORD instpw"
command from either the LMC or the local operation staff.
Default Value
=============
Empty string.
Wildcards
=========
Allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
LICENSE_WARNING
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
LISTSERV issues a warning to the console and to all non-quiet POSTMASTERs
when you reach a usage level corresponding to about 80% of your license
points. This warning is automatically disabled for small licenses (10
points or less). The warning can be turned off for higher license point
values by using this Boolean variable. WARNING: SEE DETAILS BELOW.
Example
=======
LICENSE_WARNING= 0
Details
=======
Note that this keyword turns off all license warnings, including
expiration warnings. L-Soft does not recommend turning this feature off
as it is possible for your license to expire or to be at capacity without
any warning. L-Soft is not responsible for delays or other problems
arising from the deactivation of license warnings.
Default Value
=============
LICENSE_WARNING= 1
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
LIST_ADDRESS
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
Default value for the "List-Address=" list header keyword. This keyword
does not normally need to be changed on non-VM systems.
Example
=======
LIST_ADDRESS= 'LIST-ID@NJE'
Details
=======
LIST_ADDRESS defines how mailing lists will identify themselves by
default. The main purpose of this keyword is to allow BITNET sites to
select their NJE address as the primary address, for compatibility. There
is no practical application for this keyword under non-VM systems, other
than as a migration aid for mainframe BITNET sites moving off of VM.
Default Value
=============
LIST_ADDRESS= 'LIST-ID@FQDN'
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
LIST_EXITS
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
A list of filenames of files that can be activated as list exits through
the "Exit=" list header keyword. Any suffixes (CMD for Windows NT and BAT
for Windows 95, for example) should not be included.
Example
=======
LIST_EXITS= 'EXIT1 EXIT2'
Details
=======
An "exit" is a program supplied by the customer to modify the behavior of
a product (such as LISTSERV) in ways that the supplier of the product
could not anticipate, or could not afford to support via standard
commands or options. The product checks for the presence of the "exit"
program and calls it on a number of occasions, called "exit points". In
some cases, the "exit" program supplies an answer ("return code") to the
main program, which adjusts its behavior accordingly. For instance,
LISTSERV may ask an exit program "Is it OK to add JOE@XYZ.EDU to the
ABC-L list?", and the program will answer yes or no, and possibly send a
message to the user explaining why his subscription was accepted or
rejected. In other cases, the "exit point" call is purely informative:
the exit program gets a chance to do something, such as sending an
informational message to a user, but does not return any answer. Because
this "exit" is a computer program, it must be prepared by a technical
person and installed by the LISTSERV maintainer.
List "exits" are available to control the major events associated with
list maintenance. This makes it easier to tailor the behavior of LISTSERV
to local requirements that are too specific to be addressed through
standard facilities.
An exit is enabled by adding "Exit= filename" to the list header. For
security reasons, all exits must be explicitly declared in the LIST_EXITS
configuration variable (in the LISTSERV configuration). This prevents
list owners from causing the invocation of arbitrary executable files
through the use of the "Exit=" keyword.
See the Site Manager's Operations Manual for LISTSERV 1.8c for more
information on list exits.
Default Value
=============
Empty string (no exits enabled).
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
LMCPUT
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
VM
Abstract
========
A boolean variable indicating how PUT commands for datafiles associated
with the LMC FAC are handled.
Example
=======
LMCPUT= 0
Details
=======
This variable indicates whether PUT commands for datafiles associated
with the LMC FAC must be honored immediately (1) or transferred to the
postmaster (0). Note that in the latter case, the postmaster is
responsible for updating the file.
Default Value
=============
LMCPUT= 1
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
LOCAL
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
A list of hosts and nodes to be associated with the hard-coded LCL FAC.
Also used as the default for the "Local=" list header keyword. You
usually want to set this variable to a wildcard pattern matching all the
hosts in your organization (or department for large organizations).
Example
=======
LOCAL= '*.XYZ.EDU'
Default Value
=============
None. This parameter must be set explicitly.
Wildcards
=========
Allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
MAILER
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
VM
Abstract
========
RFC822 address of the local mailer.
Example
=======
MAILER= 'MAILERT@'node
Default Value
=============
MAILER= 'MAILER@'node
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
MAILMAXL
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
The maximum size, in lines, of an incoming mail message. Messages larger
than this are not accepted for processing. This option is mostly intended
for small machines where there are not enough resources to process very
large messages. Rather than attempting to process them and then running
out of resources anyway, you can use the MAILMAXL option to reject the
message right away. You should not set this option unless you are
experiencing this kind of problem.
Example
=======
MAILMAXL= 15000
Default Value
=============
System dependent.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
MAXBSMTP
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
The maximum number of recipients in each message forwarded to the mail
delivery system (see SMTP_FORWARD). This is an optimization parameter
that you would normally set through the various "Optimize for..." buttons
in the configuration program. If your mail delivery system is a unix
machine, you should use values in the 50-100 range; smaller values will
result in faster delivery, but will use up more system resources. If your
mail delivery system runs L-Soft's LSMTP(TM)product, you should use a
much larger value, such as 1000. With LSMTP(TM), larger values improve
turnaround time and decrease system resource usage. Very large values,
however, may exhaust available system storage.
Example
=======
MAXBSMTP= 50
Default Value
=============
MAXBSMTP= 100
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
MAXDISTN
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
The maximum number of recipients in forwarded DISTRIBUTE jobs. You should
not modify this value unless instructed to do so by L-Soft.
Example
=======
MAXDISTN= 100
Default Value
=============
MAXDISTN= 1000
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
MYDOMAIN
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
The list of all the possible Internet host names and aliases for the
machine on which LISTSERV is running. Usually this is the same as NODE,
however you can supply additional names if your machine operates several
services under different host names. For instance, if your machine
operates WWW and FTP servers in addition to LISTSERV, under the hostnames
WWW.XYZ.COM and FTP.XYZ.COM, you may want to list these names in
MYDOMAIN. Similarly, if you operate the LISTSERV service under a hostname
such as LISTSERV.XYZ.COM, while the machine's real name is
NT2.IGATE.XYZ.COM, you will want to list the real name in MYDOMAIN
because some unix machines will automatically substitute it for the
published name.
Example
=======
MYDOMAIN= 'LISTSERV.XYZ.COM WWW.XYZ.COM NT2.IGATE.XYZ.COM'
or
MYDOMAIN= NODE 'WWW.XYZ.COM NT2.IGATE.XYZ.COM'
Default Value
=============
None. This parameter must be set explicitly.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
MYORG
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
Short organization name that appears in the mail header of messages from
LISTSERV itself (i.e. not in the header of messages from a mailing list).
Example
=======
MYORG= 'XYZ, Inc.'
Default Value
=============
Not set. Generates the standard "L-Soft list server at host" organization
name. Please note that the "L-Soft list server at" part of the string is
not configurable, for trademark and copyright reasons.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
NODE
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
Defines the Internet hostname of this LISTSERV host.
Example
=======
NODE= 'LISTSERV.MYHOST.NET'
Details
=======
This must be a fully-qualified address, as noted in the example. It must
not be an IP address or a non-qualified address such as 'LISTSERV'.
Default Value
=============
None. This parameter must be set explicitly.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
POSTMASTER
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
The Internet addresses of the "LISTSERV maintainers", i.e. the people in
charge of operating the LISTSERV service who are to be granted maintainer
privileges and notified of problems with the operation of the server. The
SHOW VERSION, RELEASE and HELP commands report the names and addresses of
all the LISTSERV maintainers, allowing users to determine where to report
problems. However, you can insert a "Hide:" keyword in the list, causing
all the addresses that follow to be hidden from SHOW VERSION, RELEASE or
HELP. Similarly, a "Quiet:" keyword indicates that all the addresses that
follow should be granted privileges, but should not be notified of
problems with the service.
Example
=======
POSTMASTER= 'NATHAN@LSOFT.COM Hide: DANA@LSOFT.COM Quiet: ERIC@LSOFT.COM'
Details
=======
Please note that userids such as 'postmaster@somehost.com' or
'listserv-maintainer@somehost.com' cannot be defined as LISTSERV
maintainers because they will be trapped by LISTSERV's built-in
loop-checking heuristics. If it is desired to have an "generic" address
listed as the POSTMASTER address (for instance, in the output of the
RELEASE or HELP commands), L-Soft suggests using a userid such as
'lstmaint'.
Default Value
=============
None. This parameter must be set explicitly.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PRIMETIME
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
Defines the "prime time" for your node, during which mail to lists
configured as "Prime= No" should not be processed. This option is mostly
for small machines that are very busy during business hours. Refer to the
list owner's guide for more information. Note that the value for
PRIMETIME must always be enclosed in quotes, including on Windows
machines where quotes are not normally required.
Do not confuse "prime time" for time that LISTSERV is allowed to process
mail. "Prime time" is the time during which LISTSERV is not allowed to
process mail, e.g., it is the "prime time" of day on your machine during
which other operations must take precedence.
Example
=======
PRIMETIME= 'MON-FRI: 0800-1700; SAT-SUN: -'
Default Value
=============
PRIMETIME= 'MON-SUN: -'
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
QUALIFY_DOMAIN
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
Defines the Internet domain to be appended to all non-qualified Internet
addresses. This is mostly useful when dealing with unix systems, which
often do use unqualified addresses (in violation of the Internet mail
standards). In a typical non-unix-based network, this option does not
need to be set.
Example
=======
QUALIFY_DOMAIN= '.DC.LSOFT.COM'
Default Value
=============
Determined from the Internet hostname; for instance, if your hostname is
LISTSERV.XYZ.COM, the value of QUALIFY_DOMAIN will be .XYZ.COM.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
RUNMODE
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
Windows NT, Windows 95
Abstract
========
Determines the server's mode of operation with respect to peer LISTSERV
servers running on other Internet hosts. This parameter can only be set
in the Windows versions.
Details
=======
LISTSERV can operate in one of three modes:
- Networked: in this mode, your server will connect to the worldwide
LISTSERV backbone operated over the Internet, exchanging information
with these other servers on a regular basis. This allows you, for
instance, to keep a local database of all the available LISTSERV lists,
to act as a redistribution point for all LISTSERV mail directed to
users on your campus, to advertise your lists in the worldwide list of
lists, etc. Networked mode requires a number of special tables, which
must be updated on a regular basis, and 24h uptime. Thus, this mode is
not suitable for servers with dial-up connectivity.
- Tableless: in this mode, your server accesses the worldwide LISTSERV
backbone through another LISTSERV site (which must be running in
Networked mode with full backbone status). Your server still has access
to the data available to backbone servers, but doesn't need to maintain
any LISTSERV table (hence the name). This is the preferred mode for
dial-up servers and for small servers where the overhead of maintaining
the server should be kept to a minimum.
- Standalone: this mode is for servers that are not connected to the
Internet, or that operate in a "closed" environment where outside
communication is not desired. The server will not communicate with any
of the other LISTSERV servers on the Internet. As such, it will not
have access to the list of lists or to other Internet LISTSERV
resources.
The traditional academic servers operate in Networked mode. This is the
default mode for the non-shareware versions.
Example
=======
RUNMODE=TABLELESS SWGATE.LSOFT.COM
Default Value
=============
Tableless for the Windows 95 version, networked for Windows NT.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Setting non-default directory paths with .SD
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
It is possible (but not recommended) to set non-default directory paths
for LISTSERV files by using the .SD parameter.
Example
=======
.SD 'L E:\FTP\LOGS'
Details
=======
L-Soft recommends that the default directory configuration not be changed
without good reason. Such reasons might include putting LISTSERV logs on
a shared network drive for testing or debugging purposes.
Default Value
=============
Not set.
Wildcards
=========
Not allowed. Note that this parameter must point to a valid, existing
directory name. For security reasons, LISTSERV will not create
directories that do not already exist.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SMTP_FORWARD
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
The Internet hostname (not the IP address; this variable must contain a
fully-qualfied domain name [FQDN]) of the server to which all outgoing
SMTP mail should be forwarded for delivery. This can be any machine with
SMTP software that will accept mail from your machine. If you are running
the MS Mail SMTP gateway product as your SMTP forwarding host, you should
point SMTP_FORWARD to the "smart host" defined in the MS Mail
configuration, rather than to the MS Mail gateway itself.
Example
=======
SMTP_FORWARD= 'UNIX.XYZ.COM'
Default Value
=============
None. This parameter must be set explicitly.
Wildcards
=========
Not allowed.
See also
========
SMTP_FORWARD_n
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SMTP_FORWARD_n
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
VMS, Windows
Abstract
========
Defines a number of "SMTP workers" used to spread the mail delivery load
across multiple machines (or multiple connections to the same machine).
This option is normally used for large workloads (30,000 daily deliveries
or more), or when the mail delivery server is very slow. In that case,
opening multiple connections to the machine may improve throughput.
Generally speaking, this option should not be used unless xxx.MAIL files
are consistently accumulating in the LISTSERV spool directory. The value
of each SMTP_FORWARD_n host must be a fully-qualified domain name (FQDN),
not an IP address.
Example
=======
SMTP_FORWARD_1= 'UNIXSERVER.BAR.COM'
SMTP_FORWARD_2= 'SMTP.BAZ.NET'
SMTP_FORWARD_3= 'UNIXSERVER.BAR.COM'
Default Value
=============
Not set.
Comments
The more SMTP_FORWARDn hosts you define, the more SMTP workers will be
started. Since each SMTP worker takes up some resources on your machine,
you should not define more workers than your workload requires.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SMTP_RESET_EVERY
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
Directs LISTSERV to reset the SMTP connections to the SMTP delivery
machines (see SMTP_FORWARD) at regular intervals (units: minutes). This
parameter improves turnaround time on busy servers if the mail delivery
server is a unix machine. It should not be used with other types of
delivery servers. This parameter is normally set through one of the
"Optimize for..." buttons in the configuration program.
Example
=======
SMTP_RESET_EVERY= 60
Default Value
=============
Not set; connections are not reset unless inactive.
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SORT_RECIPIENTS
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
A boolean value (0 or 1) that determines whether or not LISTSERV sorts
the recipient list in outgoing SMTP jobs. This option is normally set
through the "Optimize for..." buttons in the configuration program. It
should be set to 1 for best performance if your mail delivery host is a
unix machine. Other systems do not normally need a pre-sorted recipient
list for optimal performance.
Example
=======
SORT_RECIPIENTS= 1
Default Value
=============
SORT_RECIPIENTS= 0
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SPAM_DELAY
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
This variable sets the server-wide delay period (in minutes) during which
LISTSERV holds certain "suspicious" messages before processing them. This
gives LISTSERV's anti-spamming algorithms time in which to gather the
necessary evidence to determine whether or not the message may be a spam.
The value can be overridden on a list-by-list basis with the list header
keyword setting "Loopcheck= Spam-Delay(xxx)" (the value is in minutes). A
value of zero disables this "spam quarantine" feature.
Example
=======
SPAM_DELAY= 15
Default Value
=============
SPAM_DELAY= 10
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TRAPIN
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
A list of Internet addresses from which LISTSERV should never accept
mail. Mail and files from users matching these templates will not be
processed. This parameter is provided primarily for VM sites, but is
available for the convenience of VM customers migrating to other
platforms and should not need to be set by typical non-VM installations.
Note: L-Soft does not recommend using this keyword to filter out problem
users. Rather, you should use the FILTER_ALSO keyword for that purpose.
Example
=======
TRAPIN= 'OBNOX@SOMENODE.NET *@BADNODE.COM'
Default Value
=============
Built in.
Wildcards
=========
Allowed.
See also
========
TRAPOUT
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TRAPOUT
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
A list of Internet addresses to which LISTSERV should never send mail.
Mail and files to users matching these templates will be sent to the
postmaster instead. This parameter is provided primarily for VM sites,
but is available for the convenience of VM customers migrating to other
platforms and should not need to be set by typical non-VM installations.
Example
=======
TRAPOUT= 'OBNOX@SOMENODE.NET *@BADNODE.COM'
Default Value
=============
Built in.
Wildcards
=========
Allowed.
See also
========
TRAPIN
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
WEB_BROWSER_CONFIRM
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
All
Abstract
========
LISTSERV now requires confirmation (through the "OK" mechanism) when
commands are sent through a WWW browser, even if they apply to a list
whose security level or "Subscription=" keyword does not require
confirmation. To disable this feature, set WEB_BROWSER_CONFIRM= 0 in the
site configuration file.
Details
=======
This change was made for 1.8c both to avoid abuse and because many
occasional WWW users do not know their e-mail address or enter it
incorrectly, whereas people who use e-mail regularly do of course have a
working e-mail address in their configuration.
Example
=======
WEB_BROWSER_CONFIRM= 0
Default Value
=============
WEB_BROWSER_CONFIRM= 1
Wildcards
=========
Not allowed.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
WWW_ARCHIVE_CGI
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
VMS, unix, Windows
Abstract
========
The relative URL that leads to the WWW archive CGI script. (This is a
URL, not an OS path name.)
Example
=======
WWW_ARCHIVE_CGI= "/cgi-bin/wa"
Default Value
=============
Null.
Wildcards
=========
Not allowed.
See also
========
WWW_ARCHIVE_DIR
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
WWW_ARCHIVE_DIR
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
VMS, unix, Windows
Abstract
========
The full OS path name to the WWW archive directory
Examples
WWW_ARCHIVE_DIR= "/usr/local/etc/httpd/htdocs/archives"
WWW_ARCHIVE_DIR= e:\inetsrv\wwwroot\archives
Default Value
=============
Null.
Wildcards
=========
Not allowed.
See also
========
WWW_ARCHIVE_CGI
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
XFERTO
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Platforms
=========
VM
Abstract
========
Userid of the virtual machine to which files found in the lists readers
should be transferred. This is part of the VM/ISF support and should NOT
be changed on a regular SP or HPO system.
Example
=======
XFERTO= 'LSTMAINT'
Default Value
=============
Standard value.
Wildcards
=========
Not allowed.