.B \-use
or
.B \-file
-switches will NOT be processed with
+switches will
+.I not
+be processed with
.IR mh\-format (5).
.PP
In addition to the standard
switch, one can direct
.B inc
to incorporate messages from a file other than the user's mail drop.
-Note that the named file will NOT be zeroed, unless the
+Note that the named file will
+.I not
+be zeroed, unless the
.B \-truncate
switch is given.
.PP
.B send
directly, they supply
.B send
-with the Unix pathname of the message draft; NOT a
+with the Unix pathname of the message draft;
+.I not
+a
.B \-draftmessage
.I msg
argument. As far as
The file name is a positive integer. Other files containing metadata or
arbitrary names can exist in a folder; while the preference is that non-message
files begin with \*(lq.\*(rq, all files that are not positive integers
-.B must
+.I must
be ignored by an
.BR MH \-compatible
implementation. However, implementations are free to indicate to the user
.B mhpath
.IR new ).
New messages are
-.B only
+.I only
permitted to be added to a folder at the end of the message number range.
.PP
To add a new message to a folder, the recommended sequence is:
If you need to create an address list that includes previously-seen
addresses you may use the (\fIconcataddr\fR\^) function, which is identical
to (\fIformataddr\fR\^) in all other respects. Note that (\fIconcataddr\fR\^)
-does NOT add addresses to the duplicate-suppression cache.
+does
+.I not
+add addresses to the duplicate-suppression cache.
.SS Other Hints and Tips
Sometimes, the writer of a format function is confused because output is
duplicated. The general rule to remember is simple: If a function or
.fi
.RE
.PP
-Unfortunately, if the Reply-to: header is NOT present, the output line
+Unfortunately, if the Reply-to: header is
+.I not
+present, the output line
will be something like:
.PP
.RS 5
statement (so the rule about not starting with % applies). But the component
escape in our
.B else
-statement (everything after the `%|') is NOT an argument to anything;
+statement (everything after the `%|') is
+.I not
+an argument to anything;
it begins with a %, and thus the value of that component is output.
This also has the side effect of setting the
.I str
.PP
Each header item is called a component and is composed of a keyword or
name, along with associated text. The keyword begins at the left margin,
-may NOT contain spaces or tabs, may not exceed 63 characters (as specified
+may
+.I not
+contain spaces or tabs, may not exceed 63 characters (as specified
by RFC 822), and is terminated by a colon (`:'). Certain components
(as identified by their keywords) must follow rigidly defined formats
in their text portions.
be copied exactly to your \*(lqFrom:\*(rq header, so it should already be RFC
822 compliant. If this is set, the
.B Signature
-profile entry is NOT used, so it should include a signature as well. (profile,
+profile entry is
+.I not
+used, so it should include a signature as well. (profile,
default: userid@local.hostname)
.RE
.PP
.I \&.mh\-profile
contains only static information, which
.B nmh
-programs will NOT update. Changes in context are made to the
+programs will
+.I not
+update. Changes in context are made to the
.I context
file kept in the users
.B nmh
to add new messages to the sequence \*(lqunseen\*(rq.
Unlike the behavior of the \*(lqPrevious\-Sequence\*(rq entry in the
profile, however, the sequence(s) will
-.B not
+.I not
be zeroed by
.BR inc .
.PP
the sequence file after their processing is complete to reduce lock
contention time.
.PP
-.B Note:
+Note:
Currently transactional locks are only supported for public sequences;
private sequences will not get corrupted, but the possibility exists that two
.B nmh
the ignore list. If this component is not specified, an ignore list is
not needed since all non-specified components will be ignored.
.PP
-If \*(lqnocomponent\*(rq is NOT specified, then the component name will
+If \*(lqnocomponent\*(rq is
+.I not
+specified, then the component name will
be output as it appears in the format file.
.PP
The default format file is:
file, or input from standard input should be a validly formatted
message, just like any other
.B nmh
-message. It should NOT be in mail drop format (to convert a file in
+message. It should
+.I not
+be in mail drop format (to convert a file in
mail drop format to a folder of
.B nmh
messages, see
file, or input from standard input, should be a validly formatted message,
just like any other
.B nmh
-message. It should NOT be in mail drop format (to convert a file in
+message. It should
+.I not
+be in mail drop format (to convert a file in
mail drop format to a folder of
.B nmh
messages, see
file, or input from standard input, should be a validly formatted
message, just like any other
.B nmh
-message. It should NOT be in mail drop format (to convert a file in
+message. It should
+.I not
+be in mail drop format (to convert a file in
mail drop format to a folder of
.B nmh
messages, see
mail drops. This is useful if the user wishes to check
.BR msgchk 's
exit status. A non-zero exit status indicates that mail was
-.B not
+.I not
waiting for at least one of the indicated users.
.PP
If
.B \-list
switch is given, the message numbers of the selected messages are
written to the standard output separated by newlines. This is
-.B extremely
+.I extremely
useful for quickly generating arguments for other
.B nmh
programs by using the \*(lqbackquoting\*(rq syntax of the shell.
.SH "PROFILE COMPONENTS"
.B post
does
-.B NOT
+.I not
consult the user's
.I \&.mh_profile
.SH "SEE ALSO"
Otherwise, a `\\' preceding a <RETURN> will continue the
response on the next line, allowing for multiline components.
Continuation lines
-.B must
+.I must
begin with a space or tab.
.PP
Each non-empty component is copied to the draft and displayed on the
Note that the file should be a validly formatted message, just like
any other
.B nmh
-message. It should NOT be in mail drop format (to convert a file in
+message. It should
+.I not
+be in mail drop format (to convert a file in
mail drop format to a folder of
.B nmh
messages,
If the standard input for
.B refile
is
-.B not
+.I not
a tty, then
.B refile
will not ask any questions and will proceed as if the user answered
.I rmmproc
to delete the message, the
.I rmmproc
-must NOT call
+must
+.I not
+call
.B refile
or
.B rmm
If there are any files within the folder which are not a part of
.BR nmh ,
they will
-.B not
+.I not
be removed, and an error will be produced.
If the folder is given explicitly, or the
.B \-nointeractive
.I rmmproc
to delete the message, the
.I rmmproc
-must NOT call
+must
+.I not
+call
.B rmm
or
.B refile
.PP
If a message with multiple \*(lqFrom:\*(rq
addresses does
-.B NOT
+.I not
include a \*(lqSender:\*(rq field but does include an \*(lqEnvelope\-From:\*(rq
field, the \*(lqEnvelope\-From:\*(rq field will be used to construct
a \*(lqSender:\*(rq field.
.TP \w'defaultrrr'u
.I default
this matches
-.B only
+.I only
if the message hasn't been delivered yet
.TP \w'defaultrrr'u
.I *
.B sortm
complains about a message which it can't temporally
order, it complains about the message number
-.B prior
+.I prior
to sorting.
It should indicate what the message number will be
.B after
projects / nmh / commitdiff