- overwritten without any warning. The only directory that isn't
- true for is the `etc' directory -- in that directory, the previous
- copy of each <file> will be backed up as <file>.prev if it differs
- from the newly-installed copy. Watch for any diff output while
- make is processing that directory to see if you need to merge
- changes from *.prev files into the new versions.
-
-5) Edit the file `mts.conf' (installed in the nmh `etc' directory)
- and make any necessary changes for the mail transport interface
- you are using.
-
- The default `mts.conf' file assumes you retrieve new mail from
- a local (or NFS mounted) maildrop, and send outgoing mail by
- injecting the message to a mail transfer agent (such as sendmail)
- on the local machine via SMTP.
-
- If, instead, all your mail sending and receiving occurs on a
- remote POP/SMTP server, you will need to look at the values of the
- variables "localname", "pophost", and "servers":
-
- a) "localname" defines the hostname that nmh considers local.
- If not set, then nmh queries your OS for this value. You will
- want to change this if you wish your e-mail to appear as if it
- originated on the POP server.
-
- b) "pophost" defines the server that runs the POP daemon, and to
- which `inc' and `msgchk' will always query for new mail.
-
- c) "servers" defines the server to which you send outgoing SMTP
- traffic.
-
- If you compile with POP support, but don't want to use it exclusively,
- you can use the `-host' and `-user' options to `inc' and `msgchk'
- rather than hardcoding pophost in `mts.conf'.
-
- Check the `mh-tailor' man page for a list of all the available options
- for this file ("masquerade" may be of particular interest).
-
-6) If you have enabled POP support, make sure that `pop3' (or more
- precisely the value of the define POPSERVICE in config.h) is defined
- in the /etc/services file (or its NIS/NIS+ equivalent) on the client
- machine. It should be something equivalent to "110/tcp". This might
- have already been done when the POP daemon was installed.
-
-7) Edit the file `mhn.defaults' (installed in the nmh `etc' directory).
- This file contains the default profile entries for the nmh command
- `mhn' and is created by the script `mhn.defaults.sh'. This script
- will search a generic path (essentially your $PATH) for programs to
- handle various content types (for example, xv to display images).
- You can re-run this script and give it a more tailored path. You may
- want to re-run this script later if you install new programs to
- display content. An example of this is:
-
- % cd support/general
- % ./mhn.defaults.sh /usr/local/bin:/usr/X11/bin:/usr/ucb > mhn.defaults
-
- and then move `mhn.defaults' into the nmh `etc' directory.
-
- The `mhn.defaults.sh' script only searches for a simple set of programs.
- If you have specialized programs to handle various types, you will need
- to edit the `mhn.defaults' file manually. The syntax of this file is
- described in the man page for `mhn', and in section 9.4 of the book
- "MH & xmh: Email for Users and Programmers", 3rd edition, by Jerry Peek,
- on the Internet at <http://www.ics.uci.edu/~mh/book/mh/confmhn.htm>.
-
-9) Add an optional global mh.profile, if desired. This profile should be
- placed in the nmh `etc' directory with the name `mh.profile'. This
- file will be used to construct the initial .mh_profile of a new nmh
- user, but will not be consulted after that.
+ overwritten without any warning. The only directory this isn't
+ true for, is the `etc' directory -- in that directory, the distributed
+ files are installed with a `.dist' suffix if they differ from the
+ existing file. Watch for information messages while make is processing
+ that directory to see if you need to merge changes.
+
+4) You may edit the file `mhn.defaults' in the mmh `etc' directory.
+
+ This file contains the default profile entries for the mmh commands
+ mhlist/mhstore/show. The syntax of this file is described in section
+ 9.4 of the book "MH & xmh: Email for Users and Programmers", 3rd edition,
+ by Jerry Peek, on the Internet at
+ <http://rand-mh.sourceforge.net/book/mh/confmhn.html>.
+ In most cases you can skip this step.
+
+5) Add the bindir to your PATH variable.
+
+ If you haven't change any paths, then the bindir is `/usr/local/mmh/bin'.
+ Likely, your PATH is set in ~/.profile, ~/.kshrc, ~/.bashrc, or a similar
+ file. Have a look at mmhwrap(1), which allows you to access mmh tools
+ conveniently without changing the PATH variable.
+