mh-gen.8

<B>Digital的Unix操作系统VAX 4.2源码</B>

.\" @(#)$Id: mh-gen.8,v 2.50 90/11/21 09:27:52 mh Exp Locker: mh $
.\" uneven inter-word spacing (nroff line adjusting) hampers readability
.if n .na
.TH MH-GEN 8 MH [mh.6]
.SH NAME
mh-gen \- generating the MH system
.SH "READ THIS"
This documentation describes how to configure, generate, and install
the UCI version of the RAND \fIMH\fR system.  \fBBe certain\fP to 
read this document completely before you begin.  You probably will
also want to familiarize yourself with the \fIMH\fP Administrator's
Guide before you install \fIMH\fP.
.SH DISCLAIMER
Although the \fIMH\fR system was originally developed by the RAND Corporation,
and is now in the public domain,
the RAND Corporation assumes no responsibility for \fIMH\fR
or this particular modification of \fIMH\fR.
.PP
In addition,
the Regents of the University of California issue the following
\fBdisclaimer\fR in regard to the UCI version of \fIMH\fR:
.in +.5i
\*(lqAlthough each program has been tested by its contributor,
no warranty, express or implied,
is made by the contributor or the University of California,
as to the accuracy and functioning of the program
and related program material,
nor shall the fact of distribution constitute any such warranty,
and no responsibility is assumed by the contributor
or the University of California in connection herewith.\*(rq
.in -.5i
.PP
This version of \fIMH\fR is in the public domain,
and as such,
there are no real restrictions on its use.
The \fIMH\fR source code and documentation have no licensing restrictions
whatsoever.
As a courtesy,
the authors ask only that you provide appropriate credit to the RAND
Corporation and
the University of California for having developed the software.
.SH "GETTING HELP"
\fIMH\fR is a software package that is neither supported by the RAND
Corporation nor the University of California.
However,
since we do use the software ourselves and plan to continue using (and
improving) \fIMH\fR,
bug reports and their associated fixes should be reported back to us so that
we may include them in future releases.
The current computer mailbox for \fIMH\fR is \fBBug\[e-mail]\fR
(in the ARPA Internet),
and \fB...!ucbvax!ucivax!bug\-mh\fR (UUCP).
.PP
Presently,
there are two Internet discussion groups, \fBMH\[e-mail]\fR
and \fBMH\[e-mail]\fR.  \fBMH\-Workers\fP is for people
discussing code changes to \fIMH\fP.  \fBMH-Users\fP is for general
discussion about how to use \fIMH\fP.
\fBMH\-Users\fR is bi-directionally 
gatewayed into USENET as \fBcomp.mail.mh\fR.
.SH "HOW TO GET MH"
Since you probably already have \fIMH\fP,
you may not need to read this unless you suspect you have an old version.
There are two ways to get the latest release:
.PP
1.  If you can FTP to the ARPA Internet, use anonymous FTP to
ics.uci.edu [128.195.1.1] and retrieve the file pub/mh/mh-6.7.tar.Z.
This is a tar image after being run through the compress program
(approximately 1.5MB).  There should also be a \fBREADME\fR file in
that directory which tells what the current release of \fIMH\fP
is, and how to get updates.
.PP
This tar file is also available on louie.udel.edu 
[128.175.1.3] in portal/mh-6.7.tar.Z.  You may also find MH on
various other hosts; to make sure you get the latest version and
don't waste your time re-fixing bugs, it's best to get it from
either ics.uci.edu or louie.udel.edu.
.PP
2.  You can send $75 US to the address below.
This covers the cost of a 6250 BPI 9-track magtape,
handling, and shipping.  In addition, you'll get a
laser-printed hard-copy of the entire MH documentation set.  Be
sure to include your USPS address with your check.  Checks 
must be drawn on U.S\&. funds and should be made payable to:

.ti +1i
Regents of the University of California

The distribution address is:  

.nf
.RS 1i
Computing Support Group 
Attn: MH distribution
Department of Information and Computer Science
University of California, Irvine
Irvine, CA  92717

714/856-7554
.fi
.RE
.PP
Sadly, if you just want the hard-copies of the documentation, you
still have to pay the $75.  The tar image has the documentation
source (the manual is in roff format, but the rest are in TeX
format).  Postscript formatted versions of the TeX papers are 
available, as are crude tty-conversions of those papers.
.SH SYNOPSIS
MAKE
.SH DESCRIPTION
This is a description of how one can bring up an \fIMH\fR system.
It is assumed that you have super-user privileges in order to
(re\-)install \fIMH\fR.
Super-user privileges are not required to configure or generate \fIMH\fR.
.PP
Become the super-user and create a new directory under /usr/src/local/
(or whatever) for the \fIMH\fR area.
Traditionally, the directory's name should be mh/.
The distribution tape contains the hierarchy for the mh.6/ directory.
Bring the sources on-line:
.sp 1
.nf
# mkdir /usr/src/local/mh
% cd /usr/src/local/mh
% tar xv
.fi
.SH CONFIGURATION
First, go to the conf/ directory.
.sp 1
.nf
% cd conf/
.fi
.sp 1
This directory contains files that will produce source files tailored
for your choice of \fIMH\fR configuration.
You should edit only the file \fBMH\fR.
This file contains configuration directives.
These configuration directives are read by the \fImhconfig\fR program to
produce customized files.
For examples of various configurations,
look in the directory \fBconf/examples/\fR.
The file \fBMH\fR provided in \fBconf/\fR is a reasonable default.
.PP
Here are the \fIMH\fP configuration options available:
.in +.5i
.ti -.5i
bin: /usr/local
.br
The directory where user\-invoked programs go (see manual section 1).

.ti -.5i
debug: off
.br
Support for debug mode of \fIMH\fR.
Don't use this unless you know what you're doing,
which isn't likely if you're reading this document!

.ti -.5i
etc: /usr/local/lib/mh
.br
The directory where pgm\-invoked programs go (see manual section 8).

.ti -.5i
mail: /usr/spool/mail
.br
The directory where the maildrops are stored.
If this pathname is absolute (i.e., begins with a \fB/\fR\0),
then the user's maildrop is a file called \fB$USER\fR in this directory.
If the pathname is not absolute,
then the user's maildrop is in the user's home directory under the given name.

.ti -.5i
mailgroup: off
.br
If set, \fIinc\fR is made set-group-id to this group name.
Some SYS5 systems want this to be set to \*(lqmail\*(rq.

.ti -.5i
mandir: /usr/man
.br
The parent directory of the manual entries.

.ti -.5i
manuals: standard
.br
Where manual entries should be installed,
relative to the directory given with \*(lqmandir\*(rq.
Either \*(lqlocal\*(rq to install manual entries under \fBmanl/\fR,
or \*(lqnew\*(rq to install manual entries under \fBmann/\fR,
or \*(lqold\*(rq to install manual entries under \fBmano/\fR,
or \*(lqstandard\*(rq to install manual entries under \fBman?/\fR,
or \*(lqgen\*(rq to generate but not install them,
or \*(lqnone\*(rq to neither generate nor install them.
For example,
to install manual entries under \fB/usr/man/u_man/man?\fR,
use \*(lqstandard\*(rq and \fB/usr/man/u_man\fR for \*(lqmandir\*(rq.

.ti -.5i
chown: /etc/chown
.br
The location of the \fIchown\fR\0(8) on your system.
If \fIchown\fR is in your search path,
just use the value of \*(lqchown\*(rq.
On SYS5 systems,
this should probably be \*(lq/bin/chown\*(rq.

.ti -.5i
editor: prompter
.br
The default editor for \fIMH\fR.

.ti -.5i
remove: mv \-f
.br
How \fIMH\fR should backup existing files when installing a new file.

.ti -.5i
mts: sendmail
.br
Which message transport system to use.
Either \*(lqmmdf\*(rq to use \fIMMDF\fR as the transport system,
\*(lqmmdf2\*(rq to use \fIMMDF\-II\fR as the transport system,
\*(lqsendmail\*(rq to have \fISendMail\fR as the transport system,
or, \*(lqmh\*(rq to have \fIMH\fR as the transport system.

On UNIX systems supporting TCP/IP networking via sockets
you can add the suffix \*(lq/smtp\*(rq to the mts setting.
This often yields a superior interface as \fIMH\fR will post mail with the
local \fISMTP\fR server instead of interacting directly with \fIMMDF\fR or
\fISendMail\fR.
Hence, for TCP/IP UNIX systems,
the \*(lq/smtp\*(rq suffix to either \*(lqsendmail\*(rq or \*(lqmmdf2\*(rq is
the preferred MTS configuration.
The \*(lq/smtp\*(rq suffix is described in detail in the \fIAdministrator's
Guide\fR; be sure to set \*(lqservers:\*(rq as described in
\fImh\-tailor\fR\0(8) if you use this option.

.ti -.5i
bboards: off
.br
If \*(lqon\*(rq, include support for the UCI BBoards facility.
BBoards may be enabled with any mts setting.
If \*(lqoff\*(rq, the BBoard reading program \fIbbc\fR will not be installed.
If \*(lqnntp\*(rq,
include support for the UCI BBoards facility to read the Network News
via the NNTP.
If \*(lqpop\*(rq (formerly \*(lqpopbboards:\ on\*(rq),
include support for the UCI BBoards facility via the POP3 service;
this setting requires \*(lqpop:\ on\*(rq.

.ti -.5i
bbdelivery: off
.br
If \*(lqoff\*(rq,
the BBoards delivery agent and library files will not be installed.
If 
\*(lqon\*(rq,
and you set \*(lqbboards:\*(rq to something besides \*(lqoff\*(rq,
then 
the BBoards delivery agent and library files will be installed
in the \fIbbhome\fR directory (see below).
To read remote BBoards,
the usual configuration would have \fIbbc\fR talk to a \fIPOP3\fR or
\fINNTP\fR server.
However, it may be useful to set this to \*(lqoff\*(rq if 
you NFS mount the \fIbbhome\fR directory from another host
and want to use \fIbbc\fR to read those files directly.

.ti -.5i
bbhome: /usr/spool/bboards
.br
The home directory for the BBoards user.

.ti -.5i
mf: off
.br
Support for mail filtering on those systems in which the message transport
system isn't integrated with \fIUUCP\fR 
This option is strictly for an \fIMH\fR system using either \fIMMDF\-I\fR
as its transport system or one using \*(lqstand\-alone delivery\*(rq.

.ti -.5i
pop: off
.br
Support for POP service.
This allows local delivery for non\-local users
(a major win).
See \fBsupport/pop/pop.rfc\fR for more information on the POP.
This option currently works only on UNIX systems with TCP/IP sockets.
(It doesn't hurt to enable this option regardless of whether or not
you intend to use POP.)
If POP is enabled, there are three additional options which are of interest:
\*(lqRPOP\*(rq, \*(lqDPOP\*(rq and \*(lqPOP2\*(rq.
The first indicates that support for the UNIX variant of POP,
RPOP, which uses privileged sockets for authentication be enabled.
This peacefully co\-exists with the standard POP.
The \*(lqDPOP\*(rq option indicates that POP subscribers do not have
entries in the \fIpasswd\fR\0(5) file,
and instead have their own separate database (another major win).
The \*(lqPOP2\*(rq option indicates that the \fIMH\fP POP daemon should
speak the older POP2 protocol in addition to the \fIMH\fP POP3 protocol \-
a major win.
All of these options can be enabled via an \*(lqoptions\*(rq directive in the
\fIMH\fR configuration file.

.ti -.5i
options:
.br
\&`\-D' options to \fIcc\fR\0(1).  If you don't know what an
option does, it probably doesn't apply to you.

.in +.5i
.ti -.5i
ALTOS
.br
Use on XENIX/v7 systems.
Also, be sure to use \*(lqoptions V7\*(rq.

.ti -.5i
ATHENA
.br
Makes \fIrepl\fR `\-nocc\ all' the default instead of `\-cc\ all'.
You may want to enable this if you're using \fIxmh\fR.

.ti -.5i
ATZ
.br
Directs \fIMH\fR to use alpha\-timezones whenever possible.

.ti -.5i
BANG
.br
Directs \fIMH\fR to favor `!' over `@' in addressing.

.ti -.5i
BERK
.br
Optional for for 4.{2,3}BSD sites running SendMail.
Disables nearly all of the RFC822 address and header-parsing routines
in favor of recognizing such formats as ASCnet, and so on.
If you don't need to disable the parser for this reason,
you probably want to use \*(lqoptions DUMB\*(rq instead.

.ti -.5i
BIND
.br
If you are running with the BIND code on UNIX systems
with TCP/IP sockets (e.g. 4.{2,3}BSD),
be sure to define this.

.ti -.5i
BSD41A
.br
Use on 4.1a Berkeley UNIX systems.

.ti -.5i