X-Git-Url: https://diplodocus.org/git/nmh/blobdiff_plain/46f35e659f3bc3e808a70263bea0ec72624c8a08..84ee1e3a7320a9b4b5f40f65f9e969563dfa1443:/man/mh-tailor.man

diff --git a/man/mh-tailor.man b/man/mh-tailor.man
index 4b2362ff..0a3f5240 100644
--- a/man/mh-tailor.man
+++ b/man/mh-tailor.man
@@ -34,8 +34,8 @@ and
 .PP
 If you use
 .BR smtp ,
-this will enable a direct SMTP (simple mail transport
-protocol) interface in
+this will enable a direct SMTP
+interface in
 .BR nmh .
 When sending mail, instead of passing the
 message to the mail transport agent,
@@ -84,7 +84,7 @@ qualified hostname.  If this is not set, depending on the version of
 UNIX you're running,
 .B nmh
 will query the system for this value
-(e.g. uname, gethostname, etc.), and attempt to fully qualify this
+(e.g.\& uname, gethostname, etc.), and attempt to fully qualify this
 value.
 .PP
 If you are using POP to retrieve new messages, you may want to set this
@@ -100,7 +100,7 @@ hostname.
 This should only be needed, if for some reason
 .B nmh
 is not able to
-fully qualify the hostname returned by the system (e.g. uname,
+fully qualify the hostname returned by the system (e.g.\& uname,
 gethostname, etc.).
 .RE
 .PP
@@ -212,12 +212,25 @@ to
 .BR servers :
 localhost
 .RS 5
-A lists of hosts and networks which to look for SMTP servers when
-posting non\-local mail.  It turns out this is a major win for hosts
-which don't run an message transport system.  The value of
+A SINGLE hostname to be used when performing mail submission via SMTP.  Previous
+versions of
+.B nmh
+supported multiple hostnames for
+.BR servers ,
+but the current version of
+.B nmh
+only supports a single entry (the name is kept for backwards compatibility
+reasons).  This can be overridden via the
+.B \-server
+option to
+.IR send (1).
+It is not possible to change the mail submission port number in the
 .B servers
-should be one or more items.  Each item is the name of a host which
-is (hopefully) running a SMTP server.
+entry; see the
+.B \-port
+option to
+.BR send (1)
+for this functionality.
 .SS "SendMail"
 This option is only available if you set
 .B mts
@@ -282,7 +295,7 @@ during updates.  These locking methods can be configured separately
 from each other.
 .PP
 For locking the mail spool, the
-.I spoollocking
+.B spoollocking
 entry in
 .IR mh\-tailor (5)
 will control the locking algorithm to use when
@@ -291,12 +304,12 @@ incorporates mail from the spool file.  If no entry is given, a default
 based on the operating system type will be chosen.
 .PP
 For locking all other files, the
-.I datalocking
+.B datalocking
 entry in
 .IR mh-profile (5)
 controls the locking algorithm used for all other file access.
 If no entry is given, the
-.I fcntl
+.B fcntl
 lock method will be chosen.
 .PP
 If you do not wish to use kernel\-based locking,
@@ -313,11 +326,9 @@ Prior to installing
 you should see how locking is done at
 your site, and set the appropriate values.
 .SH FILES
-.fc ^ ~
-.nf
-.ta \w'%nmhetcdir%/ExtraBigFileName  'u
-^%nmhetcdir%/mts.conf~^nmh mts configuration file
-.fi
+.TP 20
+%nmhetcdir%/mts.conf
+nmh mts configuration file
 .SH "PROFILE COMPONENTS"
 None
 .SH "SEE ALSO"
@@ -326,16 +337,17 @@ None
 .SH DEFAULTS
 As listed above.  The path of the mail transport configuration
 file can be changed with the
-.B MHMTSCONF
+MHMTSCONF
 environment variable and augmented with the
-.B MHMTSUSERCONF
-environment variable, see mh\-profile(5).
+MHMTSUSERCONF
+environment variable, see
+.IR mh\-profile (5).
 .SH BUGS
 Failure to open any mail transport configuration file is silently
 ignored.  Therefore, it's best to avoid dynamic creation of such
 a file with the intent of use via the
-.B MHMTSCONF
+MHMTSCONF
 or
-.B MHMTSUSERCONF
+MHMTSUSERCONF
 environment variables.  If such use is necessary, the ability
 to successfully open the file should first be verified.