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
.SS "File Locking"
A few words on locking:
.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