mtstailor(4)						     Kernel Interfaces Manual						      mtstailor(4)

NAME

       mtstailor - System customization for MH message system

DESCRIPTION

       The file /usr/lib/mh/mtstailor defines run-time options for those MH programs that 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:  The  host  name  that  MH  considers
       local.	If not set, MH queries the system for this value (for example: gethostname).  This has no equivalent in the MH configuration file.
       The name of the local host in the UUCP "domain".  If not set, MH queries the system for this value.  This has no equivalent in the MH  con-
       figuration file.  A host or list of hosts running sendmail can be specified.  When an MH program is run, it uses this entry to search for a
       central sendmail to connect to.	This is particularly useful for workstation users who may not have sendmail running on their  workstation.
       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 con-
       figuration file.  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.  The beginning-of-message delimiter for maildrops.	The end-of-message
       delimiter for maildrops.  If non-zero, support for MMailids in /etc/passwd is enabled.  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 return mailid and My Full Name respectively.  The locking discipline to
	      perform.	A value of 0 or 4 means to use lockf.  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); supported only
	      within MH. A value of 5 means to use both lockf and BellMail style locking (the default).

	      Note that this locking is superseded by the locking set, if any, in the rc.config.common file. For more information,  see  mail_man-
	      ual_setup(7)  and  Network Administration .  The name of the directory for making locks when using MMDF style locking.  If the value
	      is empty, the directory of the file to be locked is used.  The pathname to the  sendmail	program.   The	name  of  the  system-wide
	      default .maildelivery file.  See slocal(1) for the details.  The highest user-id that should NOT receive mail addressed to everyone.
	      All login names with a user ID greater than the specified value are included in the address list for the alias.  If set, each  user-
	      id  greater  than  everyone  that  has  a  login shell equivalent to the given value (for example, /bin/csh) should not receive mail
	      addressed to everyone.  This is useful for handling admin, dummy, and guest logins.

   Locking
       MH has a flexible locking system for making locks on files.  Two mtstailor variables pertain to locking: lockstyle and lockldir.  The first
       controls the method of locking; the second specifies where lock files should be created.

       The  lockstyle  variable can have one of the following values: Specifies the lockf system call style locking.  Specifies that a file should
       be created whose existence means locked and whose non-existence means unlocked.	The lockname is constructed by appending .lock to the name
       of  the	file  being  locked.  Specifies that a file should be created whose existence means locked and whose non-existence means unlocked.
       The lockname is constructed by looking at the device and inode numbers of the file being locked.  If the lockldir variable  is  not  speci-
       fied,  lock  files  are	created  in the directory where the file being locked resides.	Otherwise, lock files are created in the directory
       specified by lockldir.  Specifies the lockf system call style locking.  Specifies both lockf and BellMail style locking (the default).

       Prior to installing MH, you should see how locking is done at your site, and set the appropriate values.

FILES

       System customization file.  System password file.

RELATED INFORMATION

       lockf(3), mh_profile(4), mail_manual_setup(7)

       Network Administration delim off

																      mtstailor(4)