home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ARM Club 3
/
TheARMClub_PDCD3.iso
/
hensa
/
comms
/
maillist_1
/
!MailList
/
Docs
/
FineTuning
< prev
next >
Wrap
Text File
|
1995-04-23
|
4KB
|
72 lines
MailList will automatically install itself on your system. Chances are you
won't have to change anything. But to tailor your installation of MailList
to your specific needs and system configuration there are a number of
parameters that can be changed.
These parameters are kept in one file:
<NewsDir$Dir>.MailList.Config
This file discusses each changeable parameter.
There are currently 9 parameters in this file.
#1: The first parameter is the current version-number of MailList. It is
automatically updated when you upgrade to a new version of MailList.
#2: The second parameter can be either BATCH or NOBATCH. It flags
whether MailList is to quit after it has completed its job. This is
useful on machines with a shortage of memory. To change this: From
your root account you should send a request to your MailList Robot
with the Subject: SET BATCH or the Subject: SET NOBATCH. Whichever
is appropriate.
#3: This number is the maximum number of kB one person may retrieve via
the MailServer on a single day. You can change this by using the
SET QUOTA request. This is useful if you have lots of big files on
your MailServer and people tend to retrieve as much as possible in
one go. 900 to 1000kB is a recommendable amount.
#4: This is an alias-user for your root account. MailList sends all
reports and errors to 'root@<host>'. If you don't have/use a
root-account you can have MailList send it's messages to an
alternative address by changing the default value of 'root' to a
username of your choice. To do this send the request SET ROOT
<user>. The <user> must exist on your host. Once defined, MailList
will nolonger accept HostOwner requests from the root-account. These
requests must also be sent from the alias account.
#5: These characters are not accepted as part of a filename when a file
is requested from the MailServer with the SEND <file> request. To
change this string send the request: SET FSEXCLUDE <string>. The
<string> should contain all characters that are not to be accepted.
#6: This is the maximum size (in kB) to which a digest may grow. When
the digest has become this size it is sent to the mailing-list's
subscribers. The size is excluding headers and information added at
the time of "shipment". A 90kB limit will probably be a good
setting. Bigger values may result in problems, as some
gateways/routers in the world still don't allow it. Use the request:
SET DigestSize <kB> where <kB> is the maximum size in (you guessed
it) kB.
#7: The maximum age (in days) of a digest. When the digest is older than
this number the digest will be sent. 7 days is usually a good
number. Bigger values will result in people reading "old news".
Use the request: SET DigestAge <days>
#8: Whether to fold the addresses in the Bcc: header according to
RFC-822 or make one long chain. Folding should be swithed on, as
most transports don't support strings longer than 240 chars. Use the
request: SET FOLD to use folding or SET NOFOLD for no folding.
#9: The maximum number of addresses in the Bcc: header. Some transports
have problems sending messages with a huge list of addresses in the
Bcc: header. In that case you may need to experiment what is a good
value for you. UUCP is known to have a maximum of 3 to 5. KA9Q has
no known maximum. Use the request: SET MaxBcc <number>
*** To change any of these values you need to send the appropriate request
to the robot. You will have to send the request fom your root (or
root-alias) account.