- nmh's man pages are installed here.
-
---with-mts=MTS (DEFAULT is smtp)
- specify the mail transport system you want to use. The two
- acceptable options are "smtp" (which is the default), and
- "sendmail".
-
- If you use "smtp", this will enable a direct SMTP (simple
- mail transport protocol) interface in nmh. When sending
- mail, instead of passing the message to the mail transport
- agent, `post' will open a socket connection to the mail
- port on the machine specified in the `mts.conf' file
- (default is localhost), and speak SMTP directly.
-
- If you use "sendmail", then `post' will send messages by
- passing forking a local copy of sendmail. Currently it
- will still speak SMTP with this local copy of sendmail.
-
- If you wish to use a transport agent other than sendmail, you will
- need to use a `sendmail wrapper'.
-
---with-editor=EDITOR (DEFAULT is vi)
- specify the full path of the default editor to use. If this
- option is not given, then the configuration process will search
- for the `vi' command and use it as the default. If you wish to
- specify an interface which is compatible with MH, then use the
- nmh command `prompter'. If you specify `prompter', then you don't
- need to give the full pathname.
-
---with-pager=PAGER (DEFAULT is more)
- specify the default pager (file lister) to use. If this option
- is not given, then the configuration process will search for the
- command `more' and use it as the default.
-
---enable-nmh-mhe (DEFAULT)
- Add support for the Emacs front-end `mhe'.
-
---enable-nmh-pop
- Enable client-side support for pop.
-
---with-krb4=PREFIX
- Specify the location of Kerberos V4 for KPOP support. You will
- also need to specify the option `--enable-nmh-pop'. After running
- configure, you will probably need to change the POPSERVICE define
- in config.h. See the comments inside config.h for details.
-
---with-hesiod=PREFIX
- Specify the location of Hesiod.
-
---enable-nmh-debug
- Enable debugging support.
-
---
-The nmh team
-nmh-workers@mhost.com
+ mmh's man pages are installed here.
+
+--enable-debug
+ Add debugging symbols to the binaries.
+
+--with-locking=LOCKTYPE (DEFAULT is dot)
+ Specify the locking mechanism when attempting to "inc"
+ a local mail spool. Valid options are "dot", "fcntl", "flock",
+ and "lockf".
+
+ Of the four, dot-locking requires no special kernel
+ or filesystem support, and simply creates a file called
+ "FILE.lock" to indicate that "FILE" is locked.
+ If LOCKDIR is specified, lock files will be created in that
+ directory. Otherwise, lock files will be created in the
+ directory where the file being locked resides.
+
+ To configure nmh for kernel locking, use one of the `flock',
+ `lockf' or `fcntl' values, each using the equally named
+ system call to perform the kernel-level locking.
+
+ In order to be effective, you should contact the site
+ administrator to find out what locking mechanisms other
+ mail delivery and user programs respect. The most common
+ reason not to use dot-locking is if the mail spool directory
+ is not world- or user-writeable, and thus a lock file cannot
+ be created.
+
+--with-lockdir=DIR
+ If you have defined "dot" locking, then the default is to
+ place the lock files in the same directory as the file that
+ is to be locked. Alternately, if you use this option, you can
+ specify that all lock files go in the specified directory.
+ Don't define this unless you know you need it.
+
+ This option is only relevant if "dot" locking is used.
+ In the other cases, it is ignored.