X-Git-Url: http://git.marmaro.de/?a=blobdiff_plain;f=man%2Fmh-tailor.man5;h=097242b2018dff0d3089bb8f9fd99e1fb87c6741;hb=9fca5fd33b87291cdcb326c7aab6ab9574244289;hp=e3a949a2454e837c63df9fd4ca6941d3cc25f848;hpb=2abae0bfd0ad5bf898461e50aa4b466d641f23d9;p=mmh

diff --git a/man/mh-tailor.man5 b/man/mh-tailor.man5
index e3a949a..097242b 100644
--- a/man/mh-tailor.man5
+++ b/man/mh-tailor.man5
@@ -3,50 +3,24 @@
 .\"
 .TH MH-TAILOR %manext5% "%nmhdate%" MH.6.8 [%nmhversion%]
 .SH NAME
-mh-tailor, mts.conf \- mail transport customization for nmh message handler
-.SH SYNOPSIS
-.I %etcdir%/mts.conf
+mh\-tailor \- obsolete man page
 .SH DESCRIPTION
-The file
-.I %etcdir%/mts.conf
-defines run-time options for those
-.B nmh
-programs which interact (in some form) with the message transport system.
-At present, these (user) programs are:
-.BR ap ,
-.BR conflict ,
-.BR inc ,
-.BR msgchk ,
-.BR post ,
-.BR rcvdist ,
-and
-.BR rcvpack .
-.PP
-Each option should be given on a single line.  Blank lines and lines
-which begin with `#' are ignored.  The options available along with
-default values and a description of their meanings are listed below:
-.PP
+.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 \*(lqFrom:\*(rq header in a draft,
+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 \*(lqFrom:\*(rq and a \*(lqSender:\*(rq header are set to the user's real address.
+SMTP envelope `From:' and a `Sender:' header are set to the user's real address.
 .RE
-.PP
-.BR maildelivery :
-%libdir%/maildelivery
-.RS 5
-The name of the system-wide default
-.I maildelivery
-file.
-See
-.BR slocal (1)
-for the details.
 .SS "File Locking"
 A few words on locking:
 .B nmh
@@ -59,24 +33,24 @@ method of locking, the second says where lock files should be created.
 .PP
 To configure
 .B nmh
-for kernel locking, use the \*(lq--with-locking=flock\*(rq configure option if
+for kernel locking, use the `--with-locking=flock' configure option if
 you want to use the
 .B flock
-system call; use \*(lq--with-locking=lockf\*(rq if
+system call; use `--with-locking=lockf' if
 you want to use the
 .B lockf
-system call; or use \*(lq--with-locking=fcntl\*(rq
+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 \*(lq--with-locking=dot\*(rq.  Dot locking
+to use dot locking by using `--with-locking=dot'.  Dot locking
 specifies that
-a file should be created whose existence means \*(lqlocked\*(rq and
-whose non-existence means \*(lqunlocked\*(rq.  The name of this file is
-constructed by appending \*(lq.lock\*(rq to the name of the file being
+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
@@ -88,19 +62,3 @@ Prior to installing
 .BR nmh ,
 you should see how locking is done at
 your site, and set the appropriate values.
-
-.SH FILES
-.fc ^ ~
-.nf
-.ta \w'%etcdir%/ExtraBigFileName  'u
-^%etcdir%/mts.conf~^nmh mts configuration file
-.fi
-
-.SH "PROFILE COMPONENTS"
-None
-
-.SH "SEE ALSO"
-mh\-mts(8), post(8)
-
-.SH DEFAULTS
-As listed above