is a program that parses addresses according to the ARPA
Internet standard. It also understands many non\-standard formats.
It is useful for seeing how
-.B nmh
+.B mmh
will interpret an address.
.PP
The
such as those produced by TOPS\-20 sites and some UNIX sites using
.BR ctime (3).
It is useful for seeing how
-.B nmh
+.B mmh
will interpret a date.
.PP
The
.\"
.TH FMTDUMP %manext8% "%nmhdate%" MH.6.8 [%nmhversion%]
.SH NAME
-fmtdump \- decode nmh format files
+fmtdump \- decode mh format files
.SH SYNOPSIS
.HP 5
.na
.SH DESCRIPTION
.B Fmtdump
is a program that parses an
-.B nmh
+.B mh
format file and produces a pseudo-language listing of the how
-.B nmh
+.B mmh
interprets the file. This is useful when debugging a complicated format file.
.PP
The
.ad
.SH DESCRIPTION
Since the
-.B nmh
+.B mmh
environment is the shell, it is easy to lose track
of the current folder from day to day. When
.B folder
.I ucom
has files which
aren't messages. These files may either be sub\-folders, or files that
-don't belong under the nmh file naming scheme.
+don't belong under the mh file naming scheme.
.PP
The folder and message totals are output if either a
.B \-all
.B \-volume
.I number
switches implement a digest facility for
-.BR nmh .
+.BR mmh .
Specifying these switches enables and/or overloads the following escapes:
.PP
.RS 5
.B Inc
incorporates mail from the user's incoming mail drop into
an
-.B nmh
+.B mh
folder.
.PP
You may specify which folder to use with
entry, it
will be used as the protection on the newly created messages, otherwise
the
-.B nmh
+.B mmh
default of 0644 will be used. For all subsequent operations
on these messages, this initially assigned protection will be preserved.
.PP
.PP
.B Inc
will incorporate even improperly formatted messages into the
-user's nmh folder, inserting a blank line prior to the offending component
+user's mh folder, inserting a blank line prior to the offending component
and printing a comment identifying the bad message.
.PP
In all cases, the user's mail drop will be zeroed, unless the
.RI ` MailDrop '
for this information. If the value found is
not absolute, then it is interpreted relative to the user's
-.B nmh
+.B mh
directory. If the value is not found, then
.B inc
will look in the standard system location for the user's maildrop.
indicates
that the sequences should be made `public'. These sequences
will then be readable by all
-.B nmh
+.B mmh
users with permission to read the relevant folders. In contrast, the
.B \-nopublic
switch indicates that the
.\"
.TH MH-ALIAS %manext5% "%nmhdate%" MH.6.8 [%nmhversion%]
.SH NAME
-mh-alias \- alias file for nmh message system
+mh-alias \- alias file for mh message system
.SH DESCRIPTION
This describes
-.B nmh
+.B mh
personal alias files.
It does
.B not
output instead. If `alias' is terminated with a `;' instead of
a `:', then both the `alias' and the address are output in the
correct format. (This makes replies possible since personal
-.B nmh
+.B mh
aliases are unknown to the mail transport system.)
.RE
.PP
`news.<anything>' are defined to be `news'.
.PP
The key thing to understand about aliasing in
-.B nmh
+.B mh
is that aliases in
-.B nmh
+.B mh
alias files are expanded into the headers of messages posted.
This aliasing occurs first, at posting time, without the knowledge of the
message transport system. In contrast, once the message transport system
.SH "HELPFUL HINTS"
To use aliasing in
-.B nmh
+.B mmh
quickly, do the following:
.PP
.RS 2
.\"
.TH MH-DRAFT %manext7% "%nmhdate%" MH.6.8 [%nmhversion%]
.SH NAME
-mh-draft \- draft folder facility for nmh message system
+mh-draft \- draft folder facility for mh message system
.SH DESCRIPTION
There are a number of interesting advanced facilities for the composition of
outgoing mail.
.PP
The user can send off whatever drafts desired from the shell using the
standard
-.B nmh
+.B mmh
`msgs' convention to the
.B send
command..
doesn't mind sending more than one draft at a time.
.PP
It is important to realize that
-.B nmh
+.B mmh
treats the draft folder like a standard
-.B nmh
+.B mh
folder in nearly all respects. There is one exception:
Although conceptually
.B send
.\"
.TH MH-FORMAT %manext5% "%nmhdate%" MH.6.8 [%nmhversion%]
.SH NAME
-mh-format \- format file for nmh message system
+mh-format \- format file for mh message system
.SH DESCRIPTION
Several
-.B nmh
+.B mmh
commands utilize either a
.I format
string or a
.PP
There are a few alternate scan listing formats available
in
-.IR nmh/etc/scan.time ,
-.IR nmh/etc/scan.size ,
+.IR mmh/etc/scan.time ,
+.IR mmh/etc/scan.size ,
and
-.IR nmh/etc/scan.timely .
+.IR mmh/etc/scan.timely .
Look in
-.I nmh/etc
+.I mmh/etc
for other
.B scan
and
format files which may have been written at your site.
.PP
It suffices to have your local
-.B nmh
+.B mh
expert actually write new format
commands or modify existing ones. This manual section explains how to
do that. Note: familiarity with the C
.\" support this syntax?'' MH has been hacked on for a long time...)
.\".PP
One more example: Currently,
-.B nmh
+.B mmh
supports very
large message numbers, and it is not uncommon for a folder
to have far more than 10000 messages.
from older MH versions, and are generally hard-coded to 4
digits of message number before formatting problems
start to occur.
-The nmh format strings can be modified to behave more sensibly with larger
+The mh format strings can be modified to behave more sensibly with larger
message numbers:
.PP
.RS
.\"
.TH MH-MAIL %manext5% "%nmhdate%" MH.6.8 [%nmhversion%]
.SH NAME
-mh-mail \- message format for nmh message system
+mh-mail \- message format for mh message system
.SH DESCRIPTION
-.B nmh
+.B mmh
processes messages in a particular format. It should be noted
that although neither Bell nor Berkeley mailers produce message files
in the format that
-.B nmh
+.B mmh
prefers,
-.B nmh
+.B mmh
can read message files in that antiquated format.
.PP
Each user possesses a system maildrop box which initially receives all
called the body. The header must always exist, but the body is optional.
These parts are separated by an empty line, i.e., two consecutive newline
characters. Within
-.B nmh ,
+.B mmh ,
the header and body may be separated by a line consisting of dashes:
.PP
.RS 5
.SS "Process Profile Entries"
The following profile elements are used whenever an
-.B nmh
+.B mmh
program invokes some other program such as
.BR more .
The profile can be used to select alternate programs if the
.\"
.TH MH-SEQUENCE %manext7% "%nmhdate%" MH.6.8 [%nmhversion%]
.SH NAME
-mh-sequence \- sequence specification for nmh message system
+mh-sequence \- sequence specification for mh message system
.SH DESCRIPTION
A sequence (or sequence set) is a symbolic name representing a
message or collection of messages.
-.B nmh
+.B mmh
has several internally
defined sequences, as well as allowing users to define their own
sequences.
.SS "Message Specification and Pre\-Defined Message Sequences"
Most
-.B nmh
+.B mmh
commands accept a `msg' or `msgs' specification, where
`msg' indicates one message and `msgs' indicates one or more messages.
To designate a message, you may use either its number (e.g., 1, 10, 234)
.SS "User\-Defined Message Sequences"
In addition to the `reserved' (pre-defined) message names given
above,
-.B nmh
+.B mmh
supports user-defined sequence names. User-defined
sequences allow the
-.B nmh
+.B mmh
user a tremendous amount of power in dealing
with groups of messages in the same folder by allowing the user to bind
a group of messages to a meaningful symbolic name.
character followed by zero or more alphanumeric characters, and can not
be one of the `reserved' message names above. After defining a
sequence, it can be used wherever an
-.B nmh
+.B mmh
command expects a `msg' or
`msgs' argument.
.PP
.SS "Public and Private User-Defined Sequences"
There are two varieties of user-defined sequences:
public and private. Public sequences of a folder are accessible to any
-.B nmh
+.B mmh
user that can read that folder. They are kept in each folder
in the file determined by the `Mh\-Sequences' profile entry
(default is
.IR \&.mh_sequences ).
Private sequences are accessible
only to the
-.B nmh
+.B mmh
user that defined those sequences and are kept in
the user's
-.B nmh
+.B mh
context file.
.PP
In general, the commands that create sequences (such as
.BR mark )
will create public sequences if the folder for which
the sequences are being defined is writable by the
-.B nmh
+.B mmh
user.
For most commands, this can be overridden by using the switches
.B \-public
\fIprivate\fR sequences will be created instead.
.SS "Sequence Negation"
-.B Nmh
+.B Mmh
provides the ability to select all messages
.B not
elements of a user-defined sequence.
The default negation prefix is the exlamation mark `!',
but it may be change to any string, by defining the entry
`Sequence\-Negation' in the
-.B nmh
+.B mmh
profile file.
For example, if the profile entry is:
.PP
.RE
.PP
then anytime an
-.B nmh
+.B mmh
command is given `notfoo' as a `msg' or
`msgs' argument, it would substitute all messages that are not elements
of the sequence `foo'.
profile to an empty value.
.SS "The Previous Sequence"
-.B Nmh
+.B Mmh
provides the ability to remember the `msgs' or `msg' argument
last given to an
-.B nmh
+.B mmh
command. The entry `Previous\-Sequence'
should be defined in the
-.B nmh
+.B mmh
profile; its value should be a sequence
name or multiple sequence names separated by spaces. If this entry
is defined, when an
-.B nmh
+.B mmh
command finishes, it will define the
sequence(s) named in the value of this entry to be those messages that
were specified to the command. Hence, a profile entry of
.RE
.PP
directs any
-.B nmh
+.B mmh
command that accepts a `msg' or `msgs' argument to
define the sequence `pseq' as those messages when it finishes.
.PP
there can be a performance penalty in using the
`Previous\-Sequence' facility. If it is used,
.B all
-.B nmh
+.B mmh
programs have to write the sequence information to the
.I \&.mh_sequences
file for the folder each time they run. If the
.\"
.TH MHL %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
.SH NAME
-mhl \- produce formatted listings of nmh messages
+mhl \- produce formatted listings of mh messages
.SH SYNOPSIS
.HP 5
.na
.SH DESCRIPTION
.B Mhl
is an
-.B nmh
+.B mmh
command for filtering and/or displaying text
messages. It is the default method of displaying text messages for
-.B nmh
+.B mmh
(it is the default
.IR showproc ).
.PP
accept the source message on the standard input. Note that the
file, or input from standard input should be a validly formatted
message, just like any other
-.B nmh
+.B mh
message. It should
.B NOT
be in mail drop format (to convert a file in mail drop format to
a folder of
-.B nmh
+.B mh
messages, see
.BR inc (1)).
.PP
or
.BR mailx ),
which is compatible with
-.BR nmh .
+.BR mmh .
This program was intended for the use of programs such as
.BR cron ,
which expect to send mail automatically to various
addresses. It was also used by various
-.B nmh
+.B mmh
commands to mail various error notifications.
.PP
When invoked without arguments, it had once simply invoked
.\"
.TH MHPARAM %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
.SH NAME
-mhparam \- print nmh profile and context components
+mhparam \- print mmh profile and context components
.SH SYNOPSIS
.HP 5
.na
.\"
.TH MHPATH %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
.SH NAME
-mhpath \- print full pathnames of nmh messages and folders
+mhpath \- print full pathnames of mh messages and folders
.SH SYNOPSIS
.HP 5
.na
(`Path') is output; this can be useful in shell scripts.
.PP
Contrasted with other
-.B nmh
+.B mmh
commands, a message argument to
.B mhpath
may often be intended for writing. Because of this:
.SH BUGS
Like all
-.B nmh
+.B mmh
commands,
.B mhpath
expands and sorts
accept the source message on the standard input. Note that the
file, or input from standard input should be a validly formatted
message, just like any other
-.B nmh
+.B mh
message. It should
.B NOT
be in mail drop format (to convert a file in mail drop format to
a folder of
-.B nmh
+.B mh
messages, see
.BR inc (1)).
.PP
.RE
.PP
which is created automatically during
-.B nmh
+.B mmh
installation.
.SH FILES
.\"
.TH PACKF %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
.SH NAME
-packf \- pack messages in nmh folder into a single mbox file
+packf \- pack messages in mh folder into a single mbox file
.SH SYNOPSIS
.HP 5
.na
.B extremely
useful for
quickly generating arguments for other
-.B nmh
+.B mmh
programs by using the
`backquoting' syntax of the shell. For example, the command
.PP
backquoting
.B pick
is empty. In the case of
-.B nmh
+.B mmh
programs,
the outer command now acts as if the default `msg' or `msgs' should be
used (e.g., `all' in the case of
.SH DESCRIPTION
.B Rcvstore
incorporates a message from the standard input into an
-.B nmh
+.B mh
folder. This command is typically used in conjunction with
mail filtering programs such as
.B slocal
.B Rcvstore
will incorporate anything except zero length messages
into the user's
-.B nmh
+.B mh
folder. It will not change the message in any
way.
.PP
If the user's profile contains a `Msg\-Protect: nnn' entry, it
will be used as the protection on the newly created message, otherwise
the
-.B nmh
+.B mmh
default of 0644 will be used. For all subsequent operations
on this message, this initially assigned protection will be preserved.
.PP
If you use the `Unseen\-Sequence' profile entry,
.B rcvstore
could try to update the context while another
-.B nmh
+.B mmh
process
is also trying to do so. This can cause the context to become
corrupted. To avoid this, do not use
as the source message to be filed, rather than a message from a folder.
Note that the file should be a validly formatted message, just like
any other
-.B nmh
+.B mh
message. It should
.B NOT
be in mail drop format
(to convert a file in mail drop format to a folder of
-.B nmh
+.B mh
messages,
see
.BR inc (1)).
.I msgfile
switch specifies the message to be replied to as an
exact filename rather than as an
-.B nmh
+.B mh
folder and message number. It is
intended to be used by the
.B msh
.\"
.TH RMF %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
.SH NAME
-rmf \- remove an nmh folder
+rmf \- remove an mh folder
.SH SYNOPSIS
.HP 5
.na
(or default) folder, and then removes the folder (directory) itself.
.PP
If there are any files within the folder which are not a part of
-.BR nmh ,
+.BR mmh ,
they will
.B not
be removed, and an error will be produced.
15+ 10/\|05 crocker nned
16\- 10/\|05 crocker message id format
18 10/\|06 brien Re: Exit status from mkdir
-19 10/\|07*brien `scan' listing format in nmh
+19 10/\|07*brien `scan' listing format in mmh
.fi
.RE
.PP
will accept the source message
on the standard input. Note that the file, or input from standard input
should be a validly formatted message, just like any other
-.B nmh
+.B mh
message. It should
.B NOT
be in mail drop format (to convert a file in
mail drop format to a folder of
-.B nmh
+.B mh
messages, see
.BR inc (1)).
.PP
.RE
.PP
which is created automatically during
-.B nmh
+.B mmh
installation.
.SH FILES
.B show
instead. To circumvent this, add a
profile\-entry for the link to your
-.B nmh
+.B mmh
profile and add the argument
.I n
or
Append the message to the mbox file named by
.IR string .
This is handled by piping the message to the
-.B nmh
+.B mmh
program
.BR rcvpack .
If
.TP 4
.IR folder " or " +
Store the message in the
-.B nmh
+.B mh
folder named by
.IR string .
This is handled by piping the message to the
-.B nmh
+.B mmh
program
.BR rcvstore .
If
.nf
.ta \w'default 'u +\w'mh-workersxx 'uC +\w'destroy 'uC +\w'result 'u
#
-# .maildelivery file for nmh's slocal
+# .maildelivery file for mmh's slocal
#
# Blank lines and lines beginning with a '#' are ignored
#
is the default program that queries the user about
the disposition of a composed draft. It is normally automatically
invoked by one of the
-.B nmh
+.B mmh
commands
.BR comp ,
.BR dist ,
.BR mh\-profile (5)
for further information about how editors
are used by
-.BR nmh .
+.BR mmh .
It also discusses how environment variables can be
used to direct
.BR whatnow 's
projects / mmh / commitdiff