- This will check the configuration of your OS, and create
- the include file config.h, as well as the various Makefiles.
-
- The configure script accepts various options. The options of
- most interest are listed below. To see the list of all available
- options, you can run
-
- sh configure --help
-
-2) Look through the user configuration section at the beginning
- of the generated include file `config.h'. All system-specific
- definitions should be sensed automatically now, but you may
- want to customize some #defines for your environment.
-
-3) make
-
-4) make install
-
-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 you have enabled POP support and you want this to be the
- default method of accessing new mail, you will need to change
- the values of the variables "servers", "pophost", "localname",
- and possibly "mmailid".
-
- a) "servers" defines the server to which you send outgoing SMTP
- traffic.
-
- b) "pophost" defines the server that runs the POP daemon, and to
- which `inc' and `msgchk' will query for new mail.
-
- c) "localname" defines the hostname that nmh considers local.
- If not set, then nmh queries your OS for this value. You may
- want to change this if you wish your e-mail to appear as if it
- originated on the POP server.
-
- d) "mmailid" allows two different types of email address masquerading
- when it's set to be non-zero. The first type is GECOS-based
- masquerading. nmh will check if the user's pw_gecos field in the passwd
- is of the form:
-
- Full Name <fakeusername>
-
- If it is, the internal nmh routines that find the username and full
- name of that user will return "fakeusername" and "Full Name"
- respectively. This is useful if you want the messages you send to
- always appear to come from the name of an MTA alias rather than your
- actual account name. For instance, many organizations set up
- "First.Last" sendmail aliases for all users. If this is the case,
- the GECOS field for each user should look like:
-
- First [Middle] Last <First.Last>
-
- The other type of masquerading that mmailid turns on is envelope
- "From:" masquerading based on draft contents. When a user explicitly
- specifies a "From:" header in a message, nmh uses it rather than
- constructing its own. However, the SMTP envelope "From:" and the
- "Sender:" header are set to the user's real address. Turning on
- mmailid prevents this latter behavior. This is useful when the user
- wants to pretend to be sending mail "directly" from a remote POP3
- account, or when remote mail robots incorrectly use the envelope
- "From:" in preference to the body "From:" (or refuse to take action
- when the two don't match).
-
- 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 values in `mts.conf'.
-
- Check the `mh-tailor' man page for a list of all the available options
- for this file.
-
-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
+3) make install
+
+ Note that if you have mmh files in the target directories with
+ the same names as the files being installed, the old ones will get
+ 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.