mtstailor(5mh)							mtstailor(5mh)

Name
       mtstailor - system customization for MH message system

Description
       The  file defines run-time options for those MH programs which interact
       (in some form) with the message transport system.   At  present,	 these
       (user) programs are: and

       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, depending on the version of ULTRIX you  are  run‐
		 ning,	MH  will query the system for this value (for example:
		 <whoami.h>, gethostname).  This has no equivalent in  the  MH
		 configuration file.

       The name of the local host in the UUCP “domain”.
		 If  not  set, depending on the version of ULTRIX you are run‐
		 ning, MH will query the system for this value.	 This  has  no
		 equivalent in the MH configuration file.

       A host or list of hosts running
		 can  be  specified.   When an MH program is run, it uses this
		 entry to search for a central to connect to.  This is partic‐
		 ularly	 useful for workstation users who may not have 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 configuration 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	 over‐
		 rides 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, then support for MMailids in
		 is  enabled.  Basically, the 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.

       The locking discipline to perform.
		 A value of 0 means to use if available, standard locking oth‐
		 erwise.  A value of 1 means to use locking always  (the  name
		 of  the  lock is based on the file name).  A value of 2 means
		 to use locking always (the name  of  the  lock	 is  based  on
		 device/inode pairs).

       The name of the directory for making locks.
		 If your system does not have the syscall, then this directory
		 is used when creating locks.  If the value is empty, then the
		 directory of the file to be locked is used.

       The pathname to the
		 program.

       The name of the system-wide default
		 file.	See for the details.

       The highest user-id which should NOT receive mail addressed to
		 everyone.

       If set, then each user-id greater than everyone
		 that  has  a  login  shell equivalent to the given value (for
		 example, indicates that mail for everyone should not be  sent
		 to them.  This is useful for handling admin, dummy, and guest
		 logins.

       A few words on locking: MH has a flexible  locking  system  for	making
       locks  on files.	 There are two variables you should be aware of: lock‐
       style and lockldir.  The first controls the method of locking: the sec‐
       ond says where lock files should be created.

       The lockstyle variable can take on three values: 0, 1, 2.  A value of 0
       means use the syscall if you are running on  4.2BSD,  otherwise	use  a
       locking	style of 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 specified that the lockname is constructed by
       appending 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.

Files
       System customization file.

       System password file.

See Also
       flock(2), mh_profile(5mh)

								mtstailor(5mh)

Vote for polarhome