NAME

/usr/new/lib/mh/mtstailor − system customization for MH message system

SYNOPSIS

any MH command that interacts with the MTS

DESCRIPTION

The file /usr/new/lib/mh/mtstailor defines run−time options for those MH programs which interact (in some form) with the message transport system.  At present, these (user) programs are: ap, conflict, inc, msgchk, msh, post, rcvdist, and rcvpack. 
 
The options available along with default values and a description of their meanings are listed below:
 

localname:
The host name MH considers local.  If not set, depending on the version of UNIX you’re running, MH will query the system for this value (e.g., <whoami.h>, gethostname, etc.).  This has no equivalent in the MH configuration file.  POP client hosts have this value set to the name of the POP service host. 
 

systemname:
The name of the local host in the UUCP “domain”.  If not set, depending on the version of UNIX you’re running, MH will query the system for this value.  This has no equivalent in the MH configuration file. 
 

mmdfldir: /usr/spool/mail
The directory where maildrops are kept. If this is empty, the user’s home directory is used. This overrides the “mail” field in the MH configuration file. 
 

mmdflfil:
The name of the maildrop file in the directory where maildrops are kept. If this is empty, the user’s login name is used. This overrides the “mail” field in the MH configuration file. 
 

mmdelim1: \001\001\001\001\n
The beginning−of−message delimiter for maildrops.
 

mmdelim2: \001\001\001\001\n
The end−of−message delimiter for maildrops.
 

mmailid: 0
If non-zero, then support for MMailids in /etc/passwd is enabled.  Basically, the pw_gecos field in the password file is of the form
 

My Full Name <mailid>
 
The MH internal routines that deal with user and full names will return “mailid” and “My Full Name” respectively. 
 

lockstyle: 0
The locking−discipline to perform. A value of “0” means to use flock if available, or lockf if LOCKF was defined when building MH.  On non-BSD42 systems, standard BellMail locking is used.  A value of “1” means to use BellMail locking always (the name of the lock is based on the file name).  A value of “2” means to use MMDF locking always (the name of the lock is based on device/inode pairs).  On NEWS-OS, A value of “3” means to use standard BellMail locking first, and to use flock if available, or lockf if LOCKF was defined when building MH. 
 

lockldir:
The name of the directory for making locks. If your system doesn’t have the flock or lockf syscalls, then this directory is used when creating locks.  If the value is empty, then the directory of the file to be locked is used. 
 

maildelivery: /usr/new/lib/mh/maildelivery
The name of the system−wide default .maildelivery file.  See mhook (1) for the details. 
 

everyone: 200
The highest user−id which should NOT receive mail addressed to “everyone”.
 

noshell:
If set, then each user-id greater than “everyone” that has a login shell equivalent to the given value (e.g., “/bin/csh”) indicates that mail for “everyone” should not be sent to them. This is useful for handling admin, dummy, and guest logins.

These options are only available if you compiled MH with “options MF”. 
 

uucpchan: name of UUCP channel
Usually “UUCP”. This has no equivalent in the MH configuration file. 
 

uucpldir: /usr/spool/mail
The name of the directory where UUCP maildrops are kept.  This has no equivalent in the MH configuration file. 
 

uucplfil:
The name of the maildrop file in the directory where UUCP maildrops are kept.  If this is empty, the user’s login name is used.  This has no equivalent in the MH configuration file. 
 

umincproc: /usr/new/lib/mh/uminc
The path to the program that filters UUCP−style maildrops to MMDF−style maildrops. 

These options are only available if you compiled MH to use stand-alone delivery (i.e., “mts: mh”). 
 

mailqdir: /usr/spool/netmail
The directory where network mail is queued.
 

tmailqdir: /usr/tmp
The directory where network mail queue files are built.
 

syscpy: 1
If ON, unauthorized mail is copied to the overseer.
 

overseer: root
The user that receives reports of unauthorized mail.
 

mailer: root
The user acting for the mail system.
 

fromtmp: /tmp/rml.f.XXXXXX
The mktemp template for storing from lines. 
 

msgtmp: /tmp/rml.m.XXXXXX
The mktemp template for storing the rest of the message. 
 

errtmp: /tmp/rml.e.XXXXXX
The mktemp template for storing error messages from other mailers. 
 

tmpmode: 0600
The octal mode which temporary files are set to.
 

okhosts: /usr/new/lib/mh/Rmail.OKHosts
A file containing a list of hosts that can sent ARPAnet mail.
 

okdests: /usr/new/lib/mh/RMail.OKDests
A file containing a list of hosts that can always receive mail.

These options are only available if you compiled MH with the “/smtp” suffix to your “mts:” configuration. 
 

hostable: /usr/new/lib/mh/hosts
The exceptions file for /etc/hosts used by post to try to find official names.  The format of this file is quite simple:
 

1. Comments are surrounded by sharp (‘#’) and newline. 
2. Words are surrounded by whitespace.
3. The first word on the line is the official name of a host.
4. All words following the official names are aliases for that host.

servers: localhost \01localnet
A lists of hosts and networks which to look for SMTP servers when posting local mail. It turns out this is a major win for hosts which don’t run an message transport system. The value of “servers” should be one or more items. Each item is the name of either a host or a net (in the latter case, precede the name of the net by a \01). This list is searched when looking for a smtp server to post mail. If a host is present, the SMTP port on that host is tried. If a net is present, the SMTP port on each host in that net is tried. Note that if you are running with the BIND code, then any networks specified are ignored (sorry, the interface went away under BIND).

This option is only available if you compiled MH to use SendMail as your delivery agent (i.e., “mts: sendmail”). 
 

sendmail: /usr/lib/sendmail
The pathname to the sendmail program. 

This option is only available if you compiled MH with POP support enabled (i.e., “pop: on”). 
 

pophost:
The name of the default POP service host. If this is not set, then MH looks in the standard maildrop areas for waiting mail, otherwise the named POP service host is consulted. 

This option is only available if you compiled MH with “bbdelivery: on”. 
 

bbdomain:
The local BBoards domain (a UCI hack).

These options are only available if you compiled MH with “bboards: pop” and “pop: on”. 
 

popbbhost:
The POP service host which also acts as a BBoard server. This variable should be set on the POP BBoards client host.
 

popbbuser:
The guest account on the POP/BB service host. This should be a different login ID than either the POP user or the BBoards user. (The user−id “ftp” is highly recommended.) This variable should be set on both the POP BBoards client and service hosts.
 

popbblist: /usr/new/lib/mh/hosts.popbb
A file containing of lists of hosts that are allowed to use the POP facility to access BBoards using the guest account. If this file is not present, then no check is made. This variable should be set on the POP BBoards service host.

This option is only available if you compiled MH with “bboards: nntp” and “pop: on”. 
 

nntphost:
The host which provides the NNTP service. This variable should be set on the NNTP BBoards client host.

A few words on locking: MH has a flexible locking system for making locks on files.  There are two mtstailor variables you should be aware of “lockstyle” and “lockldir”.  The first controls the method of locking, the second says where lock files should be created.  The “lockstyle” variable can take on three values: 0, 1, 2.  A value of 0 is useful on BSD42 systems.  If you included the LOCKF option when building MH, the lockf syscall is used, otherwise the flock syscall is used.  If you’re not on a 4.2BSD system, a locking style of 0 is considered the same as locking style 1. 
 
A value of 1 or 2 specifies that a file should be created whose existence means “locked” and whose non−existence means “unlocked”. A value of 1 says to construct the lockname by appending “.lock” to the name of the file being locked. A value of 2 says to construct the lockname by looking at the device and inode numbers of the file being locked. If the “lockldir” variable is not specified, lock files will be created in the directory where the file being locked resides. Otherwise, lock files will be created in the directory specified by “lockldir”. Prior to installing MH, you should see how locking is done at your site, and set the appropriate values.  ^/usr/new/lib/mh/mtstailor~^tailor file None mh−gen(8), mh−mts(8) As listed above None

NEWS-OSRelease 4.2.1R