- 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:
+6) Edit the file `mhn.defaults' (installed in the mmh `etc' directory).
+ This file contains the default profile entries for the mmh commands
+ mhlist/mhstore/mhshow 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: