home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Best of Windows 95.com 1996 September
/
WIN95_09961.iso
/
mailsrv
/
LSV95.ZIP
/
win95.z
/
SITE_DEFAULT.CFG
< prev
next >
Wrap
Text File
|
1995-04-03
|
5KB
|
93 lines
**********************************************************************
* *
* This is the SITE configuration file for LISTSERV. It serves two *
* purposes: *
* *
* 1. Define a number of required configuration variables for which *
* there is no sensible default. For instance, the password for *
* list creation, or the preferred full name for the local host. *
* *
* 2. Allow you to override definitions made in the SYSTEM.CFG file. *
* Variables which simply define textual information, such as host *
* names, passwords, names of contact persons, can be defined with *
* a statement of the form "name=value". Directories, however, *
* must be defined with ".SD name path". When you use the .SD *
* configuration statement, LISTSERV verifies the validity and *
* existence of the directory, and converts any relative path to *
* an absolute path to ensure proper operation. *
* *
**********************************************************************
*
* NODE is the full preferred Internet hostname for the machine on
* which LISTSERV is running. For instance, NT.XYZ.EDU. There is no
* default for this variable because WinSock only returns the first
* token of the host name configured in the Networks applet of Control
* Panel ("NT" in the previous example). LISTSERV needs the full
* hostname.
*
* MYDOMAIN is a list of all the Internet hostnames which correspond to
* the machine on which LISTSERV is running. In most cases, this will
* be just %NODE%, but if you have CNAMEs or other aliases, you can
* enter them here after %NODE%. Use a space and not a comma between
* the various hostnames.
*
* LOCAL is a series of hostnames or wildcard patterns identifying
* machines which are to be considered "local". Usually, this will be
* a single wildcard like *.XYZ.EDU.
*
NODE=XXX.YYY.ZZZ
MYDOMAIN=%NODE%
LOCAL=*.YYY.ZZZ
*
* SMTP_FORWARD is the Internet hostname of the server to which all
* outgoing SMTP mail should be forwarded for delivery. This can be
* any machine (and in particular any operating system) which supports
* SMTP and whose SMTP implementation can handle your workload gracefully.
*
* You can choose to run the outgoing mail interface in either synchronous
* or asynchronous mode. Synchronous mode uses the main (LSV.EXE) process
* for the delivery. This may be preferable for small workloads, especially
* if you don't have much memory on the machine. Synchronous mode is the
* default, so you don't need to do anything to activate it. In asynchronous
* mode, LISTSERV will create one or more subprocesses, called "SMTP workers",
* to deliver the mail in parallel. This allows LISTSERV to work on new incoming
* requests while the mail is being sent to the SMTP forward host. This also
* allows you to spread the load among several delivery machines (for large
* workloads), by configuring multiple SMTP workers and making them point to
* different machines. To activate asynchronous mode, you must add a number of
* SMTP_FORWARD_n variables, starting with SMTP_FORWARD_1. These variables have
* the same meaning of SMTP_FORWARD and define the SMTP forwarded for worker
* number 'n'. To create multiple workers pointing to the same machine, simply
* add multiple SMTP_FORWARD_n variables with the same value. Note that you
* must keep the plain SMTP_FORWARD variable at any rate. It is used as a fallback
* if for any reason LISTSERV fails to activate the asynchronous interface.
*
SMTP_FORWARD=XXX.YYY.ZZZ
*SMTP_FORWARD_1=%SMTP_FORWARD%
*
* BITNET_ROUTE defines the hostname of a machine that knows how to route mail
* to BITNET addresses. If your organization is connected to BITNET, you should
* substitute the Internet address of the local BITNET hosts for optimal efficiency.
* Otherwise, the default value is adequate for US sites.
*
BITNET_ROUTE=BITMAIL.LSOFT.COM
*
* POSTMASTER is a blank separated list of RFC822 e-mail addresses
* identifying the users who are to receive LISTSERV privileges.
*
POSTMASTER=Administrator@%NODE%
*
* CREATEPW is the list creation password, which POSTMASTER users need
* to specify in order to create lists using the mail interface. This
* password can also be used to validate a number of "weak" privileged
* commands. STOREPW is a secondary password that, in the Windows
* implementation, is functionally identical to CREATEPW. You should
* probably use the same value for both passwords.
*
CREATEPW=XXXXXXXX
STOREPW=%CREATEPW%