[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Nmh-workers] Changes to mh-tailor.man
[Nmh-workers] Changes to mh-tailor.man
Thu, 23 Mar 2017 01:49:06 +0000
- Straighten up some formatting
- Don't escape hyphens unecessarily
- Pluralise message (so that outgoing messages...)
diff --git a/man/mh-tailor.man b/man/mh-tailor.man
index 0a3f5240..6c1c6a2b 100644
@@ -1,4 +1,4 @@
-.TH MH-TAILOR %manext5% "April 18, 2014" "%nmhversion%"
+.TH MH-TAILOR %manext5% "March 23, 2017" "%nmhversion%"
@@ -34,14 +34,13 @@ and
If you use
.BR smtp ,
-this will enable a direct SMTP
+this will enable a direct SMTP interface in
.BR nmh .
-When sending mail, instead of passing the
-message to the mail transport agent,
+When sending mail, instead of passing the message to the mail
-will open a socket connection
-to the mail port on the machine specified in the
+will open a socket connection to the mail port on the machine
+specified in the
@@ -49,8 +48,7 @@ If you use
.BR sendmail/smtp ,
-will send messages by forking a
-local copy of
+will send messages by forking a local copy of
.BR sendmail .
It will still speak SMTP with this local copy of
.BR sendmail .
@@ -71,24 +69,21 @@ This replaces the old, undocumented
mechanism and retains some of its limitations, such as lack of
support for the
-\*(lqDcc:\*(rq header field.
+switch and \*(lqDcc:\*(rq header field.
.BR localname :
-considers local. It should typically be a fully
-qualified hostname. If this is not set, depending on the version of
-UNIX you're running,
+considers local. It should typically be a fully qualified hostname.
+If this is not set, depending on the version of UNIX you're running,
-will query the system for this value
-(e.g.\& uname, gethostname, etc.), and attempt to fully qualify this
+will query the system for this value (e.g.\& uname, gethostname, etc.),
+and attempt to fully qualify this value.
If you are using POP to retrieve new messages, you may want to set this
-value to the name of the POP server, so that outgoing message appear to
+value to the name of the POP server, so that outgoing messages appear to
have originated on the POP server.
@@ -99,25 +94,22 @@ hostname.
This should only be needed, if for some reason
-is not able to
-fully qualify the hostname returned by the system (e.g.\& uname,
+is not able to fully qualify the hostname returned by the system
+(e.g.\& uname, gethostname, etc.).
.BR clientname :
This option specifies the host name that
-will give in the
+will give in the SMTP
.BR EHLO )
-command, when posting mail. If not
-set, the default is to use the host name that
+command, when posting mail. If not set, the default is to use the
+host name that
+considers local (see
above). If this option is set, but empty, no
@@ -125,11 +117,10 @@ command will be given.
-command is required by RFC 821, many SMTP servers
-do not require it. Early versions of
+command is required by RFC 821, many SMTP servers do not require it.
+Early versions of
-will fail if the hostname
-given in the
+will fail if the hostname given in the
command is the local host. Later versions of
@@ -156,14 +147,14 @@ file.
.BR mmdfldir :
-The directory where maildrops are kept. If this option is set, but empty,
+The directory where mail drops are kept. If this option is set, but empty,
the user's home directory is used. This overrides the default value
chosen at the time of compilation.
.BR mmdflfil :
-The name of the maildrop file in the directory where maildrops are kept.
+The name of the mail drop file in the directory where mail drops are kept.
If this is empty, the user's login name is used. This overrides the default
value (which is empty).
@@ -171,19 +162,19 @@ value (which is empty).
.BR mmdelim1 :
-The beginning-of-message delimiter for maildrops.
+The beginning-of-message delimiter for mail drops.
.BR mmdelim2 :
-The end-of-message delimiter for maildrops.
+The end-of-message delimiter for mail drops.
.BR spoollocking :
-The locking algorithm to use when opening the maildrop. Can be any one of
+The locking algorithm to use when opening the mail drop. Can be any one of
@@ -212,8 +203,8 @@ to
.BR servers :
-A SINGLE hostname to be used when performing mail submission via SMTP.
+A single hostname to be used when performing mail submission via SMTP.
+Previous versions of
supported multiple hostnames for
.BR servers ,
@@ -222,13 +213,13 @@ but the current version of
only supports a single entry (the name is kept for backwards compatibility
reasons). This can be overridden via the
.IR send (1).
It is not possible to change the mail submission port number in the
entry; see the
.BR send (1)
for this functionality.
@@ -249,7 +240,7 @@ program.
The name of the default POP service host. If this is not set, then
-looks in the standard maildrop areas for waiting mail, otherwise
+looks in the standard mail drop areas for waiting mail, otherwise
the named POP service host is consulted.
.\" .SS "BBoards Delivery"
@@ -312,19 +303,17 @@ If no entry is given, the
lock method will be chosen.
-If you do not wish to use kernel\-based locking,
+If you do not wish to use kernel-based locking,
-locking is an option available.
-is not specified at build time, lock files will be created
-in the directory where the file being locked resides. Otherwise, lock
+locking is an option available. If \*(lq--enable-lockdir=directory\*(rq
+is not specified at build time, 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
Prior to installing
.BR nmh ,
-you should see how locking is done at
-your site, and set the appropriate values.
+you should see how locking is done at your site, and set the appropriate
@@ -335,19 +324,13 @@ None
.IR mh\-mts (8),
.IR post (8)
-As listed above. The path of the mail transport configuration
-file can be changed with the
-environment variable and augmented with the
-environment variable, see
+As listed above. The path of the mail transport configuration file can
+be changed with the MHMTSCONF environment variable and augmented with the
+MHMTSUSERCONF environment variable, see
.IR mh\-profile (5).
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
+a file with the intent of use via the MHMTSCONF or MHMTSUSERCONF
environment variables. If such use is necessary, the ability
to successfully open the file should first be verified.