+++ /dev/null
-.\"
-.\" %nmhwarning%
-.\"
-.TH MH-TAILOR %manext5% "%nmhdate%" MH.6.8 [%nmhversion%]
-.SH NAME
-mh\-tailor \- obsolete man page
-.SH DESCRIPTION
-.B "This man page is in transition state.
-.B "It's original use is gone.
-.B "Eventually it will be removed.
-.B "Until then, it contains information that have no better place yet.
-.SS "Spost's handling of From: headers
-.B spost
-will send messages by forking a
-local copy of
-.BR sendmail .
-.PP
-When a user explicitly specifies a `From:' header in a draft,
-.B nmh
-uses it
-rather than constructing its own. However, to discourage email forgery, the
-SMTP envelope `From:' and a `Sender:' header are set to the user's real address.
-.RE
-.SS "File Locking"
-A few words on locking:
-.B nmh
-has several methods for creating locks
-on files. When configuring
-.BR nmh ,
-you will need to decide on the
-locking style and locking directory (if any). The first controls the
-method of locking, the second says where lock files should be created.
-.PP
-To configure
-.B nmh
-for kernel locking, use the `--with-locking=flock' configure option if
-you want to use the
-.B flock
-system call; use `--with-locking=lockf' if
-you want to use the
-.B lockf
-system call; or use `--with-locking=fcntl'
-if you want to use the
-.B fcntl
-system call for kernel-level locking.
-.PP
-Instead of kernel locking, you can configure
-.B nmh
-to use dot locking by using `--with-locking=dot'. Dot locking
-specifies that
-a file should be created whose existence means `locked' and
-whose non-existence means `unlocked'. The name of this file is
-constructed by appending `.lock' to the name of the file being
-locked. If
-.B LOCKDIR
-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
-.BR LOCKDIR .
-.PP
-Prior to installing
-.BR nmh ,
-you should see how locking is done at
-your site, and set the appropriate values.