Automated generation of mh-chart.man.

[mmh] / docs / historical / MH-19910201.txt

                                  _\bd_\bi_\bs_\bc_\ba_\br_\bd _\bt_\bh_\bi_\bs _\bp_\ba_\bg_\be




                                     The RAND _\bM_\bH
                               Message Handling System:
                                    User's Manual

                                     UCI Version


                                   February 1, 1991
                                    6.7.1a #6[UCI]





































\e9\e9












                                   _\b1. _\bI_\bN_\bT_\bR_\bO_\bD_\bU_\bC_\bT_\bI_\bO_\bN



\e9
            Although people can travel cross-country in  hours  and  can  reach
       others by telephone in seconds, communications still depend heavily upon
       paper, most of which is distributed through the mails.

            There are several major reasons for this  continued  dependence  on
       written  documents.   First,  a  written  document  may be proofread and
       corrected prior to its distribution, giving the author complete  control
       over  his  words.   Thus,  a written document is better than a telephone
       conversation in this respect.  Second, a carefully written  document  is
       far  less  likely to be misinterpreted or poorly translated than a phone
       conversation.  Third, a  signature  offers  reasonable  verification  of
       authorship, which cannot be provided with media such as telegrams.

            However, the need for fast\b\b\b\b____,  accurate,  and  reproducible  document
       distribution is obvious.  One solution in widespread use is the telefax.
       Another that is rapidly gaining popularity is  electronic  mail.   Elec-
       tronic  mail is similar to telefax in that the data to be sent are digi-
       tized, transmitted via phone lines, and turned back into a  document  at
       the  receiver.   The  advantage of electronic mail is in its compression
       factor.  Whereas a telefax must scan a page in very fine lines and  send
       all  of the black and white information, electronic mail assigns charac-
       ters fixed codes which can be transmitted as a few bits of  information.
       Telefax  presently  has the advantage of being able to transmit an arbi-
       trary page, including pictures, but electronic mail is beginning to deal
       with  this  problem.   Electronic mail also integrates well with current
       directions  in  office  automation,  allowing  documents  prepared  with
       sophisticated  equipment  at  one  site  to  be  quickly transferred and
       printed at another site.

            Currently, most electronic mail is intraorganizational,  with  mail
       transfer  remaining within one computer.  As computer networking becomes
       more common, however, it is becoming more feasible to  communicate  with
       anyone whose computer can be linked to your own via a network.

            The pioneering efforts on general-purpose electronic mail  were  by
       organizations using the DoD ARPAnet[1].  The capability to send messages
       between computers existed before the ARPAnet was developed, but  it  was
       used  only in limited ways.  With the advent of the ARPAnet, tools began
       to be developed which made it convenient for  individuals  or  organiza-
       tions  to distribute messages over broad geographic areas, using diverse
       computer facilities.  The interest and activity in message  systems  has
       now  reached  such proportions that steps have been taken within the DoD
       to coordinate and unify the development  of  military  message  systems.
       The  use  of electronic mail is expected to increase dramatically in the
       next few years.  The utility of such systems in the command and  control
       and  intelligence environments is clear, and applications in these areas

\e9









                                         -2-


       will probably lead the way.  As the costs for sending and handling elec-
       tronic messages continue their rapid decrease, such uses can be expected
       to spread rapidly into other areas and, of course, will not  be  limited
       to the DoD.

            A message system provides tools that  help  users  (individuals  or
       organizations)  deal  with  messages  in various ways.  Messages must be
       composed, sent, received, stored, retrieved, forwarded, and replied  to.
       Today's  best  interactive  computer  systems provide a variety of word-
       processing and information handling capabilities.  The message  handling
       facilities  should be well integrated with the rest of the system, so as
       to be a graceful extension of overall system capability.

            The message system described in this report, _\bM_\bH, provides  most  of
       the  features that can be found in other message systems and also incor-
       porates some new ones.  It has been built on the UNIX time-sharing  sys-
       tem[2],  a  popular  operating  system  for the DEC PDP-11[1] and VAX-11
       classes of computers.  A "secure" operating system similar  to  UNIX  is
       currently being developed[3], and that system will also run _\bM_\bH.

            This report provides a complete description  of  _\bM_\bH  and  thus  may
       serve  as  a  user's  manual,  although  parts  of the report will be of
       interest to non-users as well.  Sections  2  and  3,  the  Overview  and
       Tutorial,  present  the key ideas of _\bM_\bH and will give those not familiar
       with message systems an idea of what such systems are like.

            _\bM_\bH consists of a set of commands which use some special  files  and
       conventions.   The final section is divided into three parts.  The first
       part covers the information a user needs to know in addition to the com-
       mands.   Then, each of the _\bM_\bH commands is described in detail.  Finally,
       other obscure details are revealed.  A summary of the commands is  given
       in  Appendix A, and the syntax of message sequences is given in Appendix
       B.

            A novel approach has been taken in the design of  _\bM_\bH.   Instead  of
       creating  a large subsystem that appears as a single command to the user
       (such as MS[4]), _\bM_\bH is a collection of separate commands which  are  run
       as  separate  programs.   The file and directory system of UNIX are used
       directly.  Messages are stored as individual files (datasets), and  col-
       lections  of them are grouped into directories.  In contrast, most other
       message systems store messages in a complicated data structure within  a
       monolithic file.  With the _\bM_\bH approach, UNIX commands can be interleaved
       with commands invoking the  functions  of  the  message  handler.   Con-
       versely, existing UNIX commands can be used in connection with messages.
       For example, all the usual UNIX editing, text-formatting,  and  printing
       facilities  can  be applied directly to individual messages.  MH, there-
       fore, consists of a relatively  small  amount  of  new  code;  it  makes


\e9          [1] PDP and VAX are trademarks of Digital Equipment Corporation.


\e9









                                         -3-


       extensive use of other UNIX software to provide the  capabilities  found
       in other message systems.

















































\e9
\e9












                                     _\b2. _\bO_\bV_\bE_\bR_\bV_\bI_\bE_\bW



\e9
            There are three main aspects  of  _\bM_\bH :   the   way   messages   are
       stored  (the  message  database),  the user's profile (which directs how
       certain actions of the message handler take place), and the commands for
       dealing with messages.

            Under _\bM_\bH, each message is stored as a separate file.   A  user  can
       take  any  action  with a message that he could with an ordinary file in
       UNIX.  A UNIX directory in which messages are stored is called a folder.
       Each  folder  contains  some  standard  entries  to support the message-
       handling functions.  The messages in  a  folder  have  numerical  names.
       These  folders (directories) are entries in a particular directory path,
       described in the user profile, through which _\bM_\bH can find  message  fold-
       ers.   Using  the UNIX "link" facility, it is possible for one copy of a
       message to be "filed" in more than one folder, providing a message index
       facility.   Also, using the UNIX tree-structured file system, it is pos-
       sible to have a folder within a folder,  nested  arbitrarily  deep,  and
       have the full power of the _\bM_\bH commands available.

            Each user of _\bM_\bH has a user profile, a file in  his  $HOME  (initial
       login)  directory  called  ._\bm_\bh__\bp_\br_\bo_\bf_\bi_\bl_\be.   This  profile contains several
       pieces of information used by the _\bM_\bH commands: a path name to the direc-
       tory  that  contains  the  message folders and parameters that tailor _\bM_\bH
       commands to the individual user's requirements.  There is  also  another
       file,  called  the  user  context, which contains information concerning
       which folder the user last referenced (the "current" folder).   It  also
       contains most of the necessary state information concerning how the user
       is dealing with his messages, enabling _\bM_\bH to be implemented as a set  of
       individual  UNIX commands, in contrast to the usual approach of a monol-
       ithic subsystem.

            In _\bM_\bH, incoming mail is appended to the end of a file in  a  system
       spooling  area  for  the user.  This area is called the mail drop direc-
       tory, and the file is called the user's mail drop.   Normally  when  the
       user  logins  in, s/he is informed of new mail (or the _\bM_\bH program _\bm_\bs_\bg_\bc_\bh_\bk
       may be run).  The user adds the new messages to his/her collection of _\bM_\bH
       messages  by  invoking  the  command _\bi_\bn_\bc.  The _\bi_\bn_\bc (incorporate) command
       adds the new messages to a folder called "inbox", assigning  them  names
       which  are  consecutive  integers starting with the next highest integer
       available in inbox.  _\bi_\bn_\bc also produces a _\bs_\bc_\ba_\bn summary  of  the  messages
       thus  incorporated.   A  folder can be compacted into a single file, for
       easy storage, by using the  _\bp_\ba_\bc_\bk_\bf  command.   Also,  messages  within  a
       folder can be sorted by date and time with the _\bs_\bo_\br_\bt_\bm command.


            There are four commands for examining the  messages  in  a  folder:
       _\bs_\bh_\bo_\bw,  _\bp_\br_\be_\bv,  _\bn_\be_\bx_\bt,  and _\bs_\bc_\ba_\bn.  The _\bs_\bh_\bo_\bw command displays a message in a

\e9                                         -4-









                                         -5-


       folder, _\bp_\br_\be_\bv displays the message preceding  the  current  message,  and
       _\bn_\be_\bx_\bt  displays  the  message following the current message.  _\bM_\bH lets the
       user choose the program that displays individual  messages.   A  special
       program,  _\bm_\bh_\bl,  can  be used to display messages according to the user's
       preferences.  The _\bs_\bc_\ba_\bn command summarizes the messages in a folder, nor-
       mally  producing  one line per message, showing who the message is from,
       the date, the subject, etc.

            The user may move a message from one folder  to  another  with  the
       command  _\br_\be_\bf_\bi_\bl_\be.   Messages may be removed from a folder by means of the
       command _\br_\bm_\bm.  In addition, a user may query what the current  folder  is
       and may specify that a new folder become the current folder, through the
       command _\bf_\bo_\bl_\bd_\be_\br.  All folders may be summarized with the _\bf_\bo_\bl_\bd_\be_\br_\bs command.
       A  message  folder (or subfolder) may be removed by means of the command
       _\br_\bm_\bf.

            A set of messages based on content may be selected by  use  of  the
       command  _\bp_\bi_\bc_\bk.   This  command searches through messages in a folder and
       selects those that match a given set of criteria.   These  messages  are
       then  bound  to  a  "sequence" name for use with other _\bM_\bH commands.  The
       _\bm_\ba_\br_\bk command manipulates these sequences.

            There are five commands enabling the user to  create  new  messages
       and  send them: _\bc_\bo_\bm_\bp, _\bd_\bi_\bs_\bt, _\bf_\bo_\br_\bw, _\br_\be_\bp_\bl, and _\bs_\be_\bn_\bd.  The _\bc_\bo_\bm_\bp command pro-
       vides the facility for the user to compose a new message; _\bd_\bi_\bs_\bt redistri-
       butes  mail  to  additional addressees; _\bf_\bo_\br_\bw enables the user to forward
       messages; and _\br_\be_\bp_\bl facilitates the generation of a reply to an  incoming
       message.   The  last three commands may optionally annotate the original
       message.  Messages may be arbitrarily annotated with the  _\ba_\bn_\bn_\bo  command.
       Once  a  draft has been constructed by one of the four above composition
       programs, a user-specifiable program is run to query the user as to  the
       disposition of the draft prior to sending.  _\bM_\bH provides the simple _\bw_\bh_\ba_\bt_\b-
       _\bn_\bo_\bw program to start users off.  If a message is not  sent  directly  by
       one  of these commands, it may be sent at a later time using the command
       _\bs_\be_\bn_\bd.  _\bM_\bH allows the use of any UNIX editor when  composing  a  message.
       For rapid entry, a special editor, _\bp_\br_\bo_\bm_\bp_\bt_\be_\br, is provided.  For programs,
       a special mail-sending program, _\bm_\bh_\bm_\ba_\bi_\bl, is provided.

            _\bM_\bH supports a personal aliasing  facility  which  gives  users  the
       capability  to  considerably  shorten  address typein and use meaningful
       names for addresses.  The _\ba_\bl_\bi program can be used to query _\bM_\bH as to  the
       expansion of a list of aliases.  After composing a message, but prior to
       sending, the _\bw_\bh_\bo_\bm command can be used to determine exactly who a message
       would go to.

            _\bM_\bH provides a natural interface for telling the  user's  shell  the
       names  of  _\bM_\bH  messages  and  folders.  The _\bm_\bh_\bp_\ba_\bt_\bh program achieves this
       capability.

            Finally, _\bM_\bH supports the UCI BBoards facility.  _\bb_\bb_\bc can be used  to
       query  the  status  of a group of BBoards, while _\bm_\bs_\bh can be used to read
       them.  The _\bb_\bu_\br_\bs_\bt command can be used to "shred" digests of messages into











                                         -6-


       individual messages.

            All of the elements summarized above are described in  more  detail
       in  the  following sections.  Many of the normal facilities of UNIX pro-
       vide additional capabilities for dealing with messages in various  ways.
       For  example,  it  is  possible  to  print  messages on the line-printer
       without requiring any additional code within _\bM_\bH .  Using  standard  UNIX
       facilities, any terminal output can be redirected to a file for repeated
       or future viewing.  In general, the flexibility and capabilities of  the
       UNIX  interface  with the user are preserved as a result of the integra-
       tion of _\bM_\bH into the UNIX structure.








































\e9
\e9












                                     _\b3. _\bT_\bU_\bT_\bO_\bR_\bI_\bA_\bL



\e9
            This tutorial provides a brief introduction to the _\bM_\bH commands.  It
       should  be sufficient to allow the user to read his mail, do some simple
       manipulations of it, and create and send messages.

            A message has two major pieces:  the header and the body.  The body
       consists  of the text of the message (whatever you care to type in).  It
       follows the header and is separated from it by an empty line.  (When you
       compose  a  message, the form that appears on your terminal shows a line
       of dashes after the header.  This is for convenience and is replaced  by
       an  empty  line  when  the  message is sent.)  The header is composed of
       several components, including the subject of the message and the  person
       to whom it is addressed.  Each component starts with a name and a colon;
       components must not start with a blank.  The text of the  component  may
       take  more  than  one line, but each continuation line must start with a
       blank.  Messages typically have "To:", "cc:", and "Subject:" components.
       When  composing  a  message, you should include the "To:" and "Subject:"
       components; the "cc:" (for people you want to send  copies  to)  is  not
       necessary.

            The basic _\bM_\bH commands are _\bi_\bn_\bc, _\bs_\bc_\ba_\bn, _\bs_\bh_\bo_\bw, _\bn_\be_\bx_\bt, _\bp_\br_\be_\bv,  _\br_\bm_\bm,  _\bc_\bo_\bm_\bp,
       and _\br_\be_\bp_\bl.  These are described below.

       _\bi_\bn_\bc

            When you get the message "You have mail",  type  the  command  _\bi_\bn_\bc.
       You will get a "scan listing" such as:

            7+   7/13  Cas      revival of measurement work
            8   10/ 9  Norm     NBS people and publications
            9   11/26  To:norm  question <<Are there any functions

            This shows the messages you received since the last time  you  exe-
       cuted  this  command (_\bi_\bn_\bc adds these new messages to your inbox folder).
       You can see this list again, plus a list of any other messages you have,
       by using the _\bs_\bc_\ba_\bn command.

       _\bs_\bc_\ba_\bn

            The scan listing shows the message number, followed by the date and
       the  sender.   (If  you  are the sender, the addressee in the "To:" com-
       ponent is displayed.  You may send yourself a message by including  your
       name  among  the "To:" or "cc:" addressees.) It also shows the message's
       subject; if the subject is short, the first part of the body of the mes-
       sage is included after the characters <<.



\e9                                         -7-









                                         -8-


       _\bs_\bh_\bo_\bw

            This command shows the current message, that is, the first  one  of
       the  new messages after an _\bi_\bn_\bc.  If the message is not specified by name
       (number), it is generally the last message referred to by an _\bM_\bH command.
       For example,


            _\bs_\bh_\bo_\bw 5      will show message 5.


            You can use the show command to copy a message or print a message.


            _\bs_\bh_\bo_\bw > _\bx    will copy the message to file x.
            _\bs_\bh_\bo_\bw | _\bl_\bp_\br  will print the message, using the _\bl_\bp_\br command.
            _\bn_\be_\bx_\bt        will show the message that follows the current message.
            _\bp_\br_\be_\bv        will show the message previous to the current message.
            _\br_\bm_\bm         will remove the current message.
            _\br_\bm_\bm _\b3       will remove message 3.


       _\bc_\bo_\bm_\bp

            The _\bc_\bo_\bm_\bp command puts you in the editor to write or edit a message.
       Fill  in or delete the "To:", "cc:", and "Subject:" fields, as appropri-
       ate, and type the body of the message.  Then exit normally from the edi-
       tor.   You will be asked "What now?".  Type a carriage return to see the
       options.  Typing send will cause the message to  be  sent;  typing  quit
       will cause an exit from _\bc_\bo_\bm_\bp, with the message draft saved.

            If you quit without sending the message, it will be saved in a file
       called  <name>/Mail/draft  (where  <name> is your $HOME directory).  You
       can resume editing the message later with "comp -use"; or you  can  send
       the message later, using the _\bs_\be_\bn_\bd command.

       _\bc_\bo_\bm_\bp -_\be_\bd_\bi_\bt_\bo_\br _\bp_\br_\bo_\bm_\bp_\bt_\be_\br

            This command uses a different editor and is  useful  for  preparing
       "quick  and  dirty"  messages.  It prompts you for each component of the
       header.  Type the information for that component,  or  type  a  carriage
       return to omit the component.  After that, type the body of the message.
       Backspacing is the only form of editing allowed with this editor.   When
       the  body is complete, type a carriage return followed by <EOT> (usually
       <CTRL-D>).  This completes the initial preparation of the message;  from
       then on, use the same procedures as with _\bc_\bo_\bm_\bp (above).





\e9
\e9









                                         -9-


       _\br_\be_\bp_\bl
       _\br_\be_\bp_\bl n

            This command makes up an initial message form with a header that is
       appropriate  for  replying  to  an  existing message.  The message being
       answered is the current message if no message number is mentioned, or  n
       if a number is specified.  After the header is completed, you can finish
       the message as in _\bc_\bo_\bm_\bp (above).

            This is enough information to get you going using  _\bM_\bH.   There  are
       more commands, and the commands described here have more features.  Sub-
       sequent sections explain _\bM_\bH in complete detail.   The  system  is  quite
       powerful  if you want to use its sophisticated features, but the forego-
       ing commands suffice for sending and receiving messages.

            There are numerous additional capabilities you may wish to explore.
       For  example, the _\bp_\bi_\bc_\bk command will select a subset of messages based on
       specified criteria such as sender and/or subject.   Groups  of  messages
       may  be  designated, as described in Sec. IV, under Message Naming.  The
       file ._\bm_\bh__\bp_\br_\bo_\bf_\bi_\bl_\be can be used to tailor your use of the message system to
       your needs and preferences, as described in Sec. IV, under The User Pro-
       file.  In general, you may  learn  additional  features  of  the  system
       selectively,  according  to  your requirements, by studying the relevant
       sections of this manual.  There is no need to learn all the  details  of
       the system at once.


























\e9
\e9












                               _\b4. _\bD_\bE_\bT_\bA_\bI_\bL_\bE_\bD _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN



\e9
            This section describes the _\bM_\bH system in detail, including the  com-
       ponents  of  the  user  profile, the conventions for message naming, and
       some of the other _\bM_\bH conventions.  Readers who  are  generally  familiar
       with  computer  systems  will  be  able  to  follow the principal ideas,
       although some details may be meaningful  only  to  those  familiar  with
       UNIX.


\e9       _\bT_\bH_\bE _\bU_\bS_\bE_\bR _\bP_\bR_\bO_\bF_\bI_\bL_\bE

            The first time an _\bM_\bH command is issued by a new  user,  the  system
       prompts for a "Path" and creates an _\bM_\bH "profile".

            Each _\bM_\bH user has a profile which contains tailoring information for
       each  individual  program.   Other  profile  entries control the _\bM_\bH path
       (where folders and special files are kept), folder and  message  protec-
       tions,  editor  selection,  and  default  arguments for each _\bM_\bH program.
       Each user of _\bM_\bH also has a context file  which  contains  current  state
       information for the _\bM_\bH package (the location of the context file is kept
       in the user's _\bM_\bH directory, or may be named in the user profile).   When
       a  folder  becomes the current folder, it is recorded in the user's con-
       text.  (Other state information is kept in the  context  file,  see  the
       manual  entry for _\bm_\bh-_\bp_\br_\bo_\bf_\bi_\bl_\be (5) for more details.) In general, the term
       "profile entry" refer to entries in either the profile or context  file.
       Users of _\bM_\bH needn't worry about the distinction, _\bM_\bH handles these things
       automatically.

            The _\bM_\bH profile is stored in the  file  ._\bm_\bh__\bp_\br_\bo_\bf_\bi_\bl_\be  in  the  user's
       $HOME directory[1].  It has the format of a message  without  any  body.
       That is, each profile entry is on one line, with a keyword followed by a
       colon (:) followed by text particular to the keyword.
       =>   _\bT_\bh_\bi_\bs _\bf_\bi_\bl_\be _\bm_\bu_\bs_\bt _\bn_\bo_\bt _\bh_\ba_\bv_\be _\bb_\bl_\ba_\bn_\bk _\bl_\bi_\bn_\be_\bs.
       The keywords may have any combination of upper and lower case.  (See the
       information of _\bm_\bh-_\bm_\ba_\bi_\bl later on in this manual for a description of mes-
       sage formats.)

            For the average _\bM_\bH user, the only profile entry  of  importance  is
       "Path".   Path  specifies  a  directory  in which _\bM_\bH folders and certain
       files such as "draft" are found.  The argument to this keyword must be a
       legal  UNIX  path that names an existing directory.  If this path is not


\e9          [1] By defining the envariable $MH, you can specify an alternate pro-
       file to be used by _\bM_\bH commands.


\e9                                         -10-









                                         -11-


       absolute (i.e., does not begin with a / ), it will be presumed to  start
       from  the  user's  $HOME  directory.   All folder and message references
       within _\bM_\bH will relate to this path unless full path names are used.

            Message protection defaults to 644, and folder protection  to  711.
       These  may  be  changed  by  profile  entries "Msg-Protect" and "Folder-
       Protect", respectively.  The argument to  these  keywords  is  an  octal
       number which is used as the UNIX file mode[2].

            When an _\bM_\bH program starts running, it looks through the user's pro-
       file for an entry with a keyword matching the program's name.  For exam-
       ple, when _\bc_\bo_\bm_\bp is run, it looks for a "comp" profile entry.  If  one  is
       found,  the text of the profile entry is used as the default switch set-
       ting until all defaults are overridden by explicit  switches  passed  to
       the     program     as    arguments.     Thus    the    profile    entry
       "comp: -form standard.list"  would  direct  _\bc_\bo_\bm_\bp   to   use   the   file
       "standard.list"  as the message skeleton.  If an explicit form switch is
       given to the _\bc_\bo_\bm_\bp command, it will override the switch obtained from the
       profile.

            In UNIX, a program may exist under several names, either by linking
       or  aliasing.   The actual invocation name is used by an _\bM_\bH program when
       scanning for its profile defaults[3].  Thus, each _\bM_\bH  program  may  have
       several  names by which it can be invoked, and each name may have a dif-
       ferent set of default switches.  For example, if _\bc_\bo_\bm_\bp is invoked by  the
       name  _\bi_\bc_\bo_\bm_\bp, the profile entry "icomp" will control the default switches
       for this invocation of the  _\bc_\bo_\bm_\bp  program.   This  provides  a  powerful
       definitional facility for commonly used switch settings.

            The default editor for editing within _\bc_\bo_\bm_\bp, _\br_\be_\bp_\bl, _\bf_\bo_\br_\bw,  and  _\bd_\bi_\bs_\bt,
       is  usually  _\bp_\br_\bo_\bm_\bp_\bt_\be_\br, but might be something else at your site, such as
       /_\bu_\bs_\br/_\bu_\bc_\bb/_\be_\bx or /_\bb_\bi_\bn/_\be.  A different editor may be used by specifying the
       profile  entry  "Editor:  ".  The argument to "Editor" is the name of an
       executable program or shell command file which  can  be  found  via  the
       user's  $PATH defined search path, excluding the current directory.  The
       "Editor:"  profile  specification  may  in  turn  be  overridden  by   a
       `-editor <editor>'  profile  switch associated with _\bc_\bo_\bm_\bp, _\br_\be_\bp_\bl, _\bf_\bo_\br_\bw, or
       _\bd_\bi_\bs_\bt.  Finally, an explicit editor switch specified with  any  of  these
       four commands will have ultimate precedence.



\e9          [2] See _\bc_\bh_\bm_\bo_\bd (1) in the _\bU_\bN_\bI_\bX _\bP_\br_\bo_\bg_\br_\ba_\bm_\bm_\be_\br'_\bs _\bM_\ba_\bn_\bu_\ba_\bl [5].
          [3] Unfortunately, the shell does not preserve  aliasing  information
       when  calling  a program, hence if a program is invoked by an alias dif-
       ferent than its name, the program will examine  the  profile  entry  for
       it's name, not the alias that the user invoked it as.  The correct solu-
       tion is to create a (soft) link in your $_\bH_\bO_\bM_\bE/_\bb_\bi_\bn directory  to  the  _\bM_\bH
       program  of  your choice.  By giving this link a different name, you can
       use an alternate set of defaults for the command.


\e9









                                         -12-


            During message composition, more than one editor may be used.   For
       example,  one  editor  (such  as _\bp_\br_\bo_\bm_\bp_\bt_\be_\br ) may be used initially, and a
       second editor may be invoked later to revise the message being  composed
       (see  the discussion of _\bc_\bo_\bm_\bp in Section 5 for details).  A profile entry
       "<lasteditor>-next: <editor>" specifies the name of  the  editor  to  be
       used  after  a  particular  editor.  Thus "comp: -e prompter" causes the
       initial text  to  be  collected  by  _\bp_\br_\bo_\bm_\bp_\bt_\be_\br,  and  the  profile  entry
       "prompter-next: ed"  names  ed  as the editor to be invoked for the next
       round of editing.

            Some of the _\bM_\bH commands, such as _\bs_\bh_\bo_\bw, can be used on message fold-
       ers owned by others, if those folders are readable.  However, you cannot
       write in someone else's folder.  All the _\bM_\bH command actions not  requir-
       ing write permission may be used with a "read-only" folder.

            Table 1 lists examples of some of  the  currently  defined  profile
       entries, typical arguments, and the programs that reference the entries.


































\e9
\e9









                                         -13-


                                       Table 1
\e9                                  PROFILE COMPONENTS
                ______________________________________________________

                                             _\bM_\bH Programs that
                Keyword and Argument          use Component\e9\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b______________________________________________________
\e9                Path: Mail                   All
                Current-Folder: inbox        Most
                Editor: /usr/ucb/ex          _\bc_\bo_\bm_\bp, _\bd_\bi_\bs_\bt, _\bf_\bo_\br_\bw, _\br_\be_\bp_\bl
                Msg-Protect: 644             _\bi_\bn_\bc
                Folder-Protect: 711          _\bi_\bn_\bc, _\bp_\bi_\bc_\bk, _\br_\be_\bf_\bi_\bl_\be
                <program>: default switches  All
                prompter-next: ed            _\bc_\bo_\bm_\bp, _\bd_\bi_\bs_\bt, _\bf_\bo_\br_\bw, _\br_\be_\bp_\bl
                ______________________________________________________


            Path should\b\b\b\b\b\b______ be present.  Current-Folder is maintained automatically
       by many _\bM_\bH commands (see the Context sections of the individual commands
       in Sec. IV).  All other entries are optional, defaulting to  the  values
       described above.


\e9       _\bM_\bE_\bS_\bS_\bA_\bG_\bE _\bN_\bA_\bM_\bI_\bN_\bG

            Messages may be referred to explicitly or implicitly when using  _\bM_\bH
       commands.   A formal syntax of message names is given in Appendix B, but
       the following description should be sufficient for most _\bM_\bH users.   Some
       details  of  message  naming  that  apply  only  to certain commands are
       included in the description of those commands.

            Most of the _\bM_\bH commands accept arguments  specifying  one  or  more
       folders,  and  one  or more messages to operate on.  The use of the word
       "msg" as an argument to a command means that exactly  one  message  name
       may  be  specified.   A  message name may be a number, such as 1, 33, or
       234, or it may be one of the  "reserved"  message  names:  first,  last,
       prev,  next,  and  cur.   (As a shorthand, a period (.) is equivalent to
       cur.) The meanings of these names are straightforward:  "first"  is  the
       first  message  in the folder; "last" is the last message in the folder;
       "prev" is the message  numerically  previous  to  the  current  message;
       "next"  is  the message numerically following the current message; "cur"
       (or ".") is the current message in the folder.  In addition, _\bM_\bH supports
       user-defined-sequences; see the description of the _\bm_\ba_\br_\bk command for more
       information.

            The default in commands that take a "msg" argument is always "cur".

            The word "msgs" indicates that several messages may  be  specified.
       Such  a specification consists of several message designations separated
       by spaces.  A message designation is either a message name or a  message
       range.   A  message  range is a specification of the form name1-name2 or











                                         -14-


       name1:n, where name1 and name2 are message names and n  is  an  integer.
       The  first  form  designates  all  the  messages  from  name1  to  name2
       inclusive; this must be a non-empty range.  The second form specifies up
       to  n messages, starting with name1 if name1 is a number, or first, cur,
       or next, and ending with name1 if name1 is last or prev.  This interpre-
       tation  of  n  is  overridden if n is preceded by a plus sign or a minus
       sign; +n always means up to n  messages  starting  with  name1,  and  -n
       always  means  up  to n messages ending with name1.  Repeated specifica-
       tions of the same message have the same effect as a single specification
       of the message.  Examples of specifications are:


           1 5 7-11 22
           first 6 8 next
           first-10
           last:5


            The message name "all" is a shorthand for "first-last",  indicating
       all of the messages in the folder.

            In commands that accept "msgs" arguments, the default is either cur
       or all, depending on which makes more sense.

            In all of the _\bM_\bH commands, a plus sign preceding an argument  indi-
       cates  a folder name.  Thus, "+inbox" is the name of the user's standard
       inbox.  If an explicit folder argument is given to  an  _\bM_\bH  command,  it
       will  become the current folder (that is, the "Current-Folder:" entry in
       the user's profile will be changed to this folder).  In the case of  the
       _\br_\be_\bf_\bi_\bl_\be  command,  which  can  have multiple output folders, a new source
       folder  (other  than  the  default  current  folder)  is  specified   by
       `-src +folder'.


\e9       _\bO_\bT_\bH_\bE_\bR _\bM_\bH _\bC_\bO_\bN_\bV_\bE_\bN_\bT_\bI_\bO_\bN_\bS

            One very powerful feature of _\bM_\bH is that  the  _\bM_\bH  commands  may  be
       issued  from any current directory, and the proper path to the appropri-
       ate folder(s) will be taken from the user's profile.  If the _\bM_\bH path  is
       not  appropriate for a specific folder or file, the automatic prepending
       of the _\bM_\bH path can be avoided by beginning a folder or file name with /,
       or  with  ./  or  ../ component.  Thus any specific absolute path may be
       specified along with any path relative to the current working directory.

            Arguments to the various programs may be given in any  order,  with
       the exception of a few switches whose arguments must follow immediately,
       such as `-src +folder' for _\br_\be_\bf_\bi_\bl_\be.

            Whenever an _\bM_\bH command prompts the user, the valid options will  be
       listed  in  response to a <RETURN>.  (The first of the listed options is
       the default if end-of-file is encountered, such as from a command file.)

\e9









                                         -15-


       A  valid  response  is  any  _\bu_\bn_\bi_\bq_\bu_\be  abbreviation  of  one of the listed
       options.

            Standard UNIX documentation conventions are used in this report  to
       describe  _\bM_\bH  command  syntax.  Arguments enclosed in brackets ([ ]) are
       optional; exactly one of the arguments enclosed within braces ({ }) must
       be specified, and all other arguments are required.  The use of ellipsis
       dots (...) indicates zero or more repetitions of the previous item.  For
       example,  "+folder  ..." would indicate that one or more "+folder" argu-
       ments is required and "[+folder ...]" indicates that 0 or more "+folder"
       arguments may be given.

            _\bM_\bH departs from UNIX standards by using switches  that  consist  of
       more  than  one  character,  e.g. `-header'.  To minimize typing, only a
       unique abbreviation of a switch need  be  typed;  thus,  for  `-header',
       `-hea'  is probably sufficient, depending on the other switches the com-
       mand accepts.  Each _\bM_\bH program accepts the switch `-help' (which must be
       spelled  out  fully)  and  produces  a  syntax description and a list of
       switches.  In the list of switches, parentheses indicate required  char-
       acters.   For  example,  all  `-help' switches will appear as "-(help)",
       indicating that no abbreviation is accepted.  Furthermore,  the  `-help'
       switch tells the version of the _\bM_\bH program you invoked.

            Many _\bM_\bH switches have both on and off forms, such as `-format'  and
       `-noformat'.  In many of the descriptions which follow, only one form is
       defined; the other form, often used to nullify profile switch  settings,
       is assumed to be the opposite.
























\e9
\e9









                                         -16-


       _\bM_\bH _\bC_\bO_\bM_\bM_\bA_\bN_\bD_\bS

            The _\bM_\bH package comprises several programs:

            ali (1)        - list mail aliases
            anno (1)       - annotate messages
            bbc (1)        - check on BBoards
            bboards (1)    - the UCI BBoards facility
            burst (1)      - explode digests into messages
            comp (1)       - compose a message
            dist (1)       - redistribute a message to additional addresses
            folder (1)     - set/list current folder/message
            folders (1)    - list all folders
            forw (1)       - forward messages
            inc (1)        - incorporate new mail
            mark (1)       - mark messages
            mhl (1)        - produce formatted listings of MH messages
            mhmail (1)     - send or read mail
            mhook (1)      - MH receive-mail hooks
            mhpath (1)     - print full pathnames of MH messages and folders
            msgchk (1)     - check for messages
            msh (1)        - MH shell (and BBoard reader)
            next (1)       - show the next message
            packf (1)      - compress a folder into a single file
            pick (1)       - select messages by content
            prev (1)       - show the previous message
            prompter (1)   - prompting editor front end
            rcvstore (1)   - incorporate new mail asynchronously
            refile (1)     - file messages in other folders
            repl (1)       - reply to a message
            rmf (1)        - remove folder
            rmm (1)        - remove messages
            scan (1)       - produce a one line per message scan listing
            send (1)       - send a message
            show (1)       - show (list) messages
            sortm (1)      - sort messages
            vmh (1)        - visual front-end to MH
            whatnow (1)    - prompting front-end for send
            whom (1)       - report to whom a message would go


            These programs are described below.  The form of  the  descriptions
  conforms to the standard form for the description of UNIX commands.








\e9
\e9









  ALI(1)                            -17-                            ALI(1)


  _\bN_\bA_\bM_\bE
       ali - list mail aliases

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       ali [-alias aliasfile] [-list] [-nolist] [-normalize]
            [-nonormalize] [-user] [-nouser] aliases ...  [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bA_\bl_\bi searches the named mail alias  files  for  each  of  the  given
       _\ba_\bl_\bi_\ba_\bs_\be_\bs.   It  creates  a  list of addresses for those _\ba_\bl_\bi_\ba_\bs_\be_\bs, and
       writes that list on standard output.   If  the  `-list'  option  is
       specified,  each address appears on a separate line; otherwise, the
       addresses are separated by commas and printed on as  few  lines  as
       possible.

       The `-user' option directs _\ba_\bl_\bi to  perform  its  processing  in  an
       inverted  fashion: instead of listing the addresses that each given
       alias expands to, _\ba_\bl_\bi will list the aliases  that  expand  to  each
       given  address.   If the `-normalize' switch is given, _\ba_\bl_\bi will try
       to track down the official hostname of the address.

       The file specified by the profile entry "Aliasfile:" and any  addi-
       tional  alias  files given by the `-alias aliasfile' switch will be
       read.  Each _\ba_\bl_\bi_\ba_\bs is processed as described in _\bm_\bh-_\ba_\bl_\bi_\ba_\bs (5).

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile
       /etc/passwd                         List of users
       /etc/group                          List of groups


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Aliasfile:           For a default alias file


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       mh-alias(5)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `-alias /usr/local/lib/mh/MailAliases'
       `-nolist'
       `-nonormalize'
       `-nouser'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None

\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  ALI(1)                            -18-                            ALI(1)


  _\bB_\bu_\bg_\bs
       The `-user' option with `-nonormalize' is not entirely accurate, as
       it  does  not replace local nicknames for hosts with their official
       site names.















































\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  ANNO(1)                           -19-                           ANNO(1)


  _\bN_\bA_\bM_\bE
       anno - annotate messages

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       anno [+folder] [msgs] [-component field] [-inplace] [-noinplace]
            [-date] [-nodate] [-text body] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bA_\bn_\bn_\bo annotates the specified messages in the named folder using the
       field  and body.  Annotation is optionally performed by _\bd_\bi_\bs_\bt, _\bf_\bo_\br_\bw,
       and _\br_\be_\bp_\bl, to keep track of your distribution of, forwarding of, and
       replies  to  a  message.   By using _\ba_\bn_\bn_\bo, you can perform arbitrary
       annotations of your own.  Each message selected will  be  annotated
       with the lines

           field: date
           field: body

       The `-nodate' switch inhibits the date annotation, leaving only the
       body  annotation.   The  `-inplace'  switch causes annotation to be
       done in place in order to preserve links to the annotated message.

       The field specified should be a valid 822-style message field name,
       which  means  that  it  should consist of alphanumerics (or dashes)
       only.  The body specified is arbitrary text.

       If a `-component field' is not specified when _\ba_\bn_\bn_\bo is invoked, _\ba_\bn_\bn_\bo
       will prompt the user for the name of field for the annotation.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Current-Folder:      To find the default current folder


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       dist (1), forw (1), repl (1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to the current folder
       `msgs' defaults to cur
       `-noinplace'
       `-date'



\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  ANNO(1)                           -20-                           ANNO(1)


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       If a folder is given, it will become the current folder.  The first
       message annotated will become the current message.
















































\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  BBC(1)                            -21-                            BBC(1)


  _\bN_\bA_\bM_\bE
       bbc - check on BBoards

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       bbc [bboards ...] [-topics] [-check] [-read] [-quiet] [-verbose]
            [-archive] [-noarchive] [-protocol] [-noprotocol]
            [-mshproc program] [switches for _\bm_\bs_\bh_\bp_\br_\bo_\bc] [-rcfile rcfile]
            [-norcfile] [-file BBoardsfile] [-user BBoardsuser]
            [-host host] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bb_\bb_\bc is a BBoard reading/checking program  that  interfaces  to  the
       BBoard channel.

       The _\bb_\bb_\bc program has three action switches which direct  its  opera-
       tion:

       The `-read' switch invokes the _\bm_\bs_\bh program on  the  named  _\bB_\bB_\bo_\ba_\br_\bd_\bs.
       If  you  also  specify the `-archive' switch, then  _\bb_\bb_\bc will invoke
       the _\bm_\bs_\bh program on the  archives  of  the  named  _\bB_\bB_\bo_\ba_\br_\bd_\bs.   If  no
       _\bB_\bB_\bo_\ba_\br_\bd_\bs   are   given  on  the  command  line,  and  you  specified
       `-archive', _\bb_\bb_\bc will not read your  `bboards'  profile  entry,  but
       will read the archives of the "system" _\bB_\bB_\bo_\ba_\br_\bd instead.

       The `-check' switch types out  status  information  for  the  named
       _\bB_\bB_\bo_\ba_\br_\bd_\bs.   _\bb_\bb_\bc  can  print one of several messages depending on the
       status of both the BBoard and the user's reading  habits.  As  with
       each  of these messages, the number given is the item number of the
       last item placed in the BBoard.  This number (which  is  marked  in
       the  messages  as the "BBoard-Id") is ever increasing.  Hence, when
       _\bb_\bb_\bc says "n items", it really means that the highest  BBoard-Id  is
       "n".   There  may,  or may not actually be "n" items in the BBoard.
       Some common messages are:

            BBoard -- n items unseen
                 This message tells how many items the user  has  not  yet
                 seen.  When invoked with the `-quiet' switch, this is the
                 only informative line that _\bb_\bb_\bc will possibly print out.

            BBoard -- empty
                 The BBoard is empty.

            BBoard -- n items (none seen)
                 The BBoard has items in it, but the user hasn't seen any.

            BBoard -- n items (all seen)
                 The BBoard is non-empty, and the user has seen everything
                 in it.

            BBoard -- n items seen out of m
                 The BBoard has at most m-n items that the  user  has  not

  [mh.6]                           MH.6.7                      UCI version









  BBC(1)                            -22-                            BBC(1)


                 seen.

       The `-topics' switch directs _\bb_\bb_\bc to print  three  items  about  the
       named _\bB_\bB_\bo_\ba_\br_\bd_\bs: it's official name, the number of items present, and
       the date and time of the last update.  If  no  _\bB_\bB_\bo_\ba_\br_\bd_\bs  are  named,
       then  all  BBoards  are listed.  If the `-verbose' switch is given,
       more information is output.

       The `-quiet' switch specifies that  _\bb_\bb_\bc  should  be  silent  if  no
       _\bB_\bB_\bo_\ba_\br_\bd_\bs  are  found  with  new  information.  The `-verbose' switch
       specifies that _\bb_\bb_\bc is to consider you to be interested  in  _\bB_\bB_\bo_\ba_\br_\bd_\bs
       that you've already seen everything in.

       To override the default _\bm_\bs_\bh_\bp_\br_\bo_\bc and  the  profile  entry,  use  the
       `-mshproc program' switch.  Any arguments not understood by _\bb_\bb_\bc are
       passed to this program.  The `-protocol' switch tells _\bb_\bb_\bc that your
       _\bm_\bs_\bh_\bp_\br_\bo_\bc  knows  about  the  special _\bb_\bb_\bc protocol for reporting back
       information.  _\bm_\bs_\bh (1), the default _\bm_\bs_\bh_\bp_\br_\bo_\bc, knows all about this.

       The `-file BBoardsfile' switch tells  _\bb_\bb_\bc  to  use  a  non-standard
       _\bB_\bB_\bo_\ba_\br_\bd_\bs  file  when  performing  its  calculations.  Similarly, the
       `-user BBoardsuser' switch tells _\bb_\bb_\bc to use  a  non-standard  user-
       name.   Both  of  these  switches  are  useful  for debugging a new
       _\bB_\bB_\bo_\ba_\br_\bd_\bs or _\bP_\bO_\bP file.

       If the local host is configured as an NNTP BBoards  client,  or  if
       the `-host host' switch is given, then _\bb_\bb_\bc will query the NNTP ser-
       vice host as to the  status  of  the  BBoards.   For  NNTP  BBoards
       clients, the `-user user' and the `-rpop' switches are ignored.

       The  `-rcfile rcfile'  switch  overrides  the  use  of  ._\bb_\bb_\br_\bc   for
       user-specific  BBoards  information.   If  the  value  given to the
       switch is not absolute, (i.e., does not begin with a / ),  it  will
       be  presumed  to start from the current working directory.  If this
       switch is not given (or the `-norcfile' switch is given), then  _\bb_\bb_\bc
       consults  the envariable $MHBBRC, and honors it similarly.  If this
       envariable is not set, then the file  ._\bb_\bb_\br_\bc  in  the  user's  $HOME
       directory is used.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile
       $HOME/.bbrc                         BBoard information


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       bboards:             To specify interesting BBoards
       mshproc:             Program to read a given BBoard



\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  BBC(1)                            -23-                            BBC(1)


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       bbl(1), bboards(1), msh(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `-read'
       `-noarchive'
       `-protocol'
       `bboards' defaults to "system"
       `-file /usr/bboards/BBoards'
       `-user bboards'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None


  _\bB_\bu_\bg_\bs
       The `-user' switch takes effect only if  followed  by  the  `-file'
       switch.































\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  BBOARDS(1)                        -24-                        BBOARDS(1)


  _\bN_\bA_\bM_\bE
       bboards - the UCI BBoards facility

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       bbc [-check] [-read] bboards ...  [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       The home directory of _\bb_\bb_\bo_\ba_\br_\bd_\bs is where the BBoard system  is  kept.
       This documentation describes some of the nuances of the BBoard sys-
       tem.

       BBoards, BBoard-IDs
            A BBoard is just a file containing a group of messages  relat-
            ing  to the same topic.  These files live in the ~bboards home
            directory.  Each message in a BBoard file has  in  its  header
            the  line  "BBoard-Id:  n",  where "n" is an ascending decimal
            number.  This id-number  is  unique  for  each  message  in  a
            BBoards  file.   It  should  NOT  be confused with the message
            number of a message, which can change as messages are  removed
            from the BBoard.

       BBoard Handling
            To read BBoards, use the _\bb_\bb_\bc and _\bm_\bs_\bh programs.  The  _\bm_\bs_\bh  com-
            mand  is  a  monolithic  program  which contains all the func-
            tionality of _\bM_\bH in a single program.  The `-check'  switch  to
            _\bb_\bb_\bc  lets  you check on the status of BBoards, and the `-read'
            switch tells _\bb_\bb_\bc to invoke _\bm_\bs_\bh to read those BBoards.

       Creating a BBoard
            Both public, and private BBoards are supported.   Contact  the
            mail  address  _\bP_\bo_\bs_\bt_\bM_\ba_\bs_\bt_\be_\br  if  you'd  like  to  have  a BBoard
            created.

       BBoard addresses
            Each BBoard has associated with it 4 addresses, these are (for
            the ficticious BBoard called ``hacks''):
              hacks : The Internet wide distribution list.
              dist-hacks : The local BBoard.
              hacks-request : The people responsible for the BBoard at the
                   Internet level.
              local-hacks-request : The people responsible for the  BBoard
                   locally.

  _\bF_\bi_\bl_\be_\bs
      $HOME/.mh_profile                   The user profile
      $HOME/.bbrc                         BBoard information




\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  BBOARDS(1)                        -25-                        BBOARDS(1)


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       bboards:             To specify interesting BBoards
       mshproc:             Program to read a given BBoard


  _\bS_\be_\be _\bA_\bl_\bs_\bo
      bbc(1), bbl(1), bbleader(1), msh(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       The default bboard is "system"


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
      None



































\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  BURST(1)                          -26-                          BURST(1)


  _\bN_\bA_\bM_\bE
       burst - explode digests into messages

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       burst [+folder] [msgs] [-inplace] [-noinplace] [-quiet] [-noquiet]
            [-verbose] [-noverbose] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bB_\bu_\br_\bs_\bt considers the specified messages in the named  folder  to  be
       Internet digests, and explodes them in that folder.

       If `-inplace' is given, each digest is replaced by  the  "table  of
       contents"  for  the digest (the original digest is removed).  _\bB_\bu_\br_\bs_\bt
       then renumbers all of the messages  following  the  digest  in  the
       folder  to  make room for each of the messages contained within the
       digest.  These messages are placed immediately after the digest.

       If `-noinplace' is given, each digest is  preserved,  no  table  of
       contents  is produced, and the messages contained within the digest
       are placed at the end of the folder.  Other messages are  not  tam-
       pered with in any way.

       The `-quiet' switch directs _\bb_\bu_\br_\bs_\bt to be silent about reporting mes-
       sages that are not in digest format.

       The `-verbose' switch directs _\bb_\bu_\br_\bs_\bt to tell the  user  the  general
       actions that it is taking to explode the digest.

       It turns out that _\bb_\bu_\br_\bs_\bt works equally well  on  forwarded  messages
       and  blind-carbon-copies  as on Internet digests, provided that the
       former two were generated by _\bf_\bo_\br_\bw or _\bs_\be_\bn_\bd.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Current-Folder:      To find the default current folder
       Msg-Protect:         To set mode when creating a new message


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       _\bP_\br_\bo_\bp_\bo_\bs_\be_\bd _\bS_\bt_\ba_\bn_\bd_\ba_\br_\bd _\bf_\bo_\br _\bM_\be_\bs_\bs_\ba_\bg_\be _\bE_\bn_\bc_\ba_\bp_\bs_\bu_\bl_\ba_\bt_\bi_\bo_\bn (aka RFC-934),
       inc(1), msh(1), pack(1)





\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  BURST(1)                          -27-                          BURST(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to the current folder
       `msgs' defaults to cur
       `-noinplace'
       `-noquiet'
       `-noverbose'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       If a folder is given, it will become the current folder.  If  `-in-
       place'  is  given, then the first message burst becomes the current
       message.  This leaves the context ready for a _\bs_\bh_\bo_\bw of the table  of
       contents  of the digest, and a _\bn_\be_\bx_\bt to see the first message of the
       digest.  If `-noinplace' is given, then the first message extracted
       from  the  first  digest  burst  becomes the current message.  This
       leaves the context in a similar, but not identical,  state  to  the
       context achieved when using `-inplace'.


  _\bB_\bu_\bg_\bs
       The _\bb_\bu_\br_\bs_\bt program enforces a limit on the number of messages  which
       may be _\bb_\bu_\br_\bs_\bt from a single message.  This number is on the order of
       1000 messages.  There is usually no limit on the number of messages
       which may reside in the folder after the _\bb_\bu_\br_\bs_\bting.

       Although _\bb_\bu_\br_\bs_\bt uses a sophisticated algorithm  to  determine  where
       one  encapsulated message ends and another begins, not all digesti-
       fying programs  use  an  encapsulation  algorithm.   In  degenerate
       cases, this usually results in _\bb_\bu_\br_\bs_\bt finding an encapsulation boun-
       dary prematurely and splitting a single encapsulated  message  into
       two or more messages.  These erroneous digestifying programs should
       be fixed.

       Furthermore, any text which appears  after  the  last  encapsulated
       message  is not placed in a seperate message by _\bb_\bu_\br_\bs_\bt.  In the case
       of digestified messages, this text is usally  an  "End  of  digest"
       string.   As  a result of this possibly un-friendly behavior on the
       part of _\bb_\bu_\br_\bs_\bt, note that when the `-inplace' option is  used,  this
       trailing  information  is lost.  In practice, this is not a problem
       since correspondents usually place remarks in  text  prior  to  the
       first encapsulated message, and this information is not lost.










\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  COMP(1)                           -28-                           COMP(1)


  _\bN_\bA_\bM_\bE
       comp - compose a message

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       comp [+folder] [msg] [-draftfolder +folder] [-draftmessage msg]
            [-nodraftfolder] [-editor editor] [-noedit] [-file file]
            [-form formfile] [-use] [-nouse] [-whatnowproc program]
            [-nowhatnowproc] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bC_\bo_\bm_\bp is used to create a new message to be  mailed.   It  copies  a
       message form to the draft being composed and then invokes an editor
       on the draft (unless `-noedit' is given, in which case the  initial
       edit is suppressed).

       The default message form contains the following elements:

            To:
            cc:
            Subject:
            --------

       If the file named "components" exists in the user's  MH  directory,
       it  will  be  used  instead  of  this  form.  The file specified by
       `-form formfile' will be used if given.  You may  also  start  _\bc_\bo_\bm_\bp
       using the contents of an existing message as the form.  If you sup-
       ply either a `+folder' or `msg' argument, that message will be used
       as  the  form.   You  may  not supply both a `-form formfile' and a
       `+folder' or `msg' argument.  The line of dashes or  a  blank  line
       must be left between the header and the body of the message for the
       message to be identified properly when it is sent  (see  _\bs_\be_\bn_\bd (1)).
       The  switch  `-use'  directs  _\bc_\bo_\bm_\bp  to  continue editing an already
       started message.  That is, if a _\bc_\bo_\bm_\bp (or _\bd_\bi_\bs_\bt, _\br_\be_\bp_\bl, or  _\bf_\bo_\br_\bw )  is
       terminated without sending the draft, the draft can be edited again
       via "comp -use".

       If the draft already exists, _\bc_\bo_\bm_\bp will ask you as to  the  disposi-
       tion  of  the  draft.  A reply of quit will abort _\bc_\bo_\bm_\bp, leaving the
       draft intact; replace will replace  the  existing  draft  with  the
       appropriate  form;  list  will  display the draft; use will use the
       draft for further composition; and  refile +folder  will  file  the
       draft  in  the  given  folder,  and  give  you a new draft with the
       appropriate form.  (The `+folder' argument to refile is required.)

       The `-draftfolder +folder' and `-draftmessage msg' switches  invoke
       the _\bM_\bH draft folder facility.  This is an advanced (and highly use-
       ful) feature.  Consult the Advanced  Features  section  of  the  _\bM_\bH
       manual for more information.

       The `-file file' switch says to use the named file as  the  message
       draft.

  [mh.6]                           MH.6.7                      UCI version









  COMP(1)                           -29-                           COMP(1)


       The `-editor editor' switch indicates the editor  to  use  for  the
       initial  edit.   Upon exiting from the editor, _\bc_\bo_\bm_\bp will invoke the
       _\bw_\bh_\ba_\bt_\bn_\bo_\bw program.  See _\bw_\bh_\ba_\bt_\bn_\bo_\bw (1) for  a  discussion  of  available
       options.   The invocation of this program can be inhibited by using
       the `-nowhatnowproc' switch.  (In truth of fact, it is the  _\bw_\bh_\ba_\bt_\bn_\bo_\bw
       program  which  starts  the  initial edit.  Hence, `-nowhatnowproc'
       will prevent any edit from occurring.)

  _\bF_\bi_\bl_\be_\bs
       /usr/local/lib/mh/components        The message skeleton
       or <mh-dir>/components              Rather than the standard skeleton
       $HOME/.mh_profile                   The user profile
       <mh-dir>/draft                      The draft file


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Draft-Folder:        To find the default draft-folder
       Editor:              To override the default editor
       Msg-Protect:         To  set  mode  when  creating  a  new  message
       (draft)
       fileproc:            Program to refile the message
       whatnowproc:         Program to ask the "What now?" questions


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       dist(1), forw(1), repl(1), send(1), whatnow(1), mh-profile(5)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to the current folder
       `msg' defaults to the current message
       `-nodraftfolder'
       `-nouse'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None


  _\bB_\bu_\bg_\bs
       If _\bw_\bh_\ba_\bt_\bn_\bo_\bw_\bp_\br_\bo_\bc is _\bw_\bh_\ba_\bt_\bn_\bo_\bw, then _\bc_\bo_\bm_\bp uses a  built-in  _\bw_\bh_\ba_\bt_\bn_\bo_\bw,  it
       does  not  actually  run the _\bw_\bh_\ba_\bt_\bn_\bo_\bw program.  Hence, if you define
       your own _\bw_\bh_\ba_\bt_\bn_\bo_\bw_\bp_\br_\bo_\bc, don't call it _\bw_\bh_\ba_\bt_\bn_\bo_\bw since  _\bc_\bo_\bm_\bp  won't  run
       it.






\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  DIST(1)                           -30-                           DIST(1)


  _\bN_\bA_\bM_\bE
       dist - redistribute a message to additional addresses

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       dist [+folder] [msg] [-annotate] [-noannotate]
            [-draftfolder +folder] [-draftmessage msg] [-nodraftfolder]
            [-editor editor] [-noedit] [-form formfile] [-inplace]
            [-noinplace] [-whatnowproc program] [-nowhatnowproc] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bD_\bi_\bs_\bt is similar to _\bf_\bo_\br_\bw.  It prepares  the  specified  message  for
       redistribution to addresses that (presumably) are not on the origi-
       nal address list.

       The default message form contains the following elements:

            Resent-To:
            Resent-cc:

       If the file named "distcomps" exists in the user's MH directory, it
       will be used instead of this form.  In either case, the file speci-
       fied by `-form formfile' will be used if given.  The form used will
       be prepended to the message being resent.

       If the draft already exists, _\bd_\bi_\bs_\bt will ask you as to  the  disposi-
       tion  of  the  draft.  A reply of quit will abort _\bd_\bi_\bs_\bt, leaving the
       draft intact; replace will replace the existing draft with a  blank
       skeleton; and list will display the draft.

       Only   those   addresses   in   "Resent-To:",   "Resent-cc:",   and
       "Resent-Bcc:"  will  be sent.  Also, a "Resent-Fcc: folder" will be
       honored (see _\bs_\be_\bn_\bd (1)).  Note that with _\bd_\bi_\bs_\bt, the draft should con-
       tain  only  "Resent-xxx:"  fields and no body.  The headers and the
       body of the original message are copied to the draft when the  mes-
       sage  is sent.  Use care in constructing the headers for the redis-
       tribution.

       If the `-annotate' switch is given, the  message being  distributed
       will be annotated with the lines:

            Resent: date
            Resent: addrs

       where each address list contains as many lines as  required.   This
       annotation  will  be done only if the message is sent directly from
       _\bd_\bi_\bs_\bt.  If the message is not  sent  immediately  from  _\bd_\bi_\bs_\bt,  "comp
       -use"  may be used to re-edit and send the constructed message, but
       the annotations won't take place.   The  '-inplace'  switch  causes
       annotation  to  be  done in place in order to preserve links to the
       annotated message.
\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  DIST(1)                           -31-                           DIST(1)


       See _\bc_\bo_\bm_\bp (1) for a  description  of  the  `-editor'  and  `-noedit'
       switches.   Note that while in the editor, the message being resent
       is available through a link named "@" (assuming the  default  _\bw_\bh_\ba_\bt_\b-
       _\bn_\bo_\bw_\bp_\br_\bo_\bc ).   In  addition,  the  actual  pathname of the message is
       stored in the envariable $editalt, and the pathname of  the  folder
       containing the message is stored in the envariable $mhfolder.

       The `-draftfolder +folder' and `-draftmessage msg' switches  invoke
       the _\bM_\bH draft folder facility.  This is an advanced (and highly use-
       ful) feature.  Consult the Advanced  Features  section  of  the  _\bM_\bH
       manual for more information.

       Upon exiting from the editor, _\bd_\bi_\bs_\bt will invoke the _\bw_\bh_\ba_\bt_\bn_\bo_\bw program.
       See _\bw_\bh_\ba_\bt_\bn_\bo_\bw (1) for a discussion of available options.  The invoca-
       tion of this program can be inhibited by using the `-nowhatnowproc'
       switch.   (In truth of fact, it is the _\bw_\bh_\ba_\bt_\bn_\bo_\bw program which starts
       the initial edit.  Hence, `-nowhatnowproc' will  prevent  any  edit
       from occurring.)

  _\bF_\bi_\bl_\be_\bs
       /usr/local/lib/mh/distcomps         The message skeleton
       or <mh-dir>/distcomps               Rather than the standard skeleton
       $HOME/.mh_profile                   The user profile
       <mh-dir>/draft                      The draft file


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Current-Folder:      To find the default current folder
       Draft-Folder:        To find the default draft-folder
       Editor:              To override the default editor
       fileproc:            Program to refile the message
       whatnowproc:         Program to ask the "What now?" questions


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       comp(1), forw(1), repl(1), send(1), whatnow(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to the current folder
       `msg' defaults to cur
       `-noannotate'
       `-nodraftfolder'
       `-noinplace'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       If a folder is given, it will become the current folder.  The  mes-
       sage distributed will become the current message.

\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  DIST(1)                           -32-                           DIST(1)


  _\bH_\bi_\bs_\bt_\bo_\br_\by
       _\bD_\bi_\bs_\bt originally used headers of the form "Distribute-xxx:"  instead
       of "Resent-xxx:".  In order to conform with the ARPA Internet stan-
       dard, RFC-822, the "Resent-xxx:"  form  is  now  used.   _\bD_\bi_\bs_\bt  will
       recognize  "Distribute-xxx:" type headers and automatically convert
       them to "Resent-xxx:".


  _\bB_\bu_\bg_\bs
       _\bD_\bi_\bs_\bt does not _\br_\bi_\bg_\bo_\br_\bo_\bu_\bs_\bl_\by check the message  being  distributed  for
       adherence  to the transport standard, but _\bp_\bo_\bs_\bt called by _\bs_\be_\bn_\bd does.
       The _\bp_\bo_\bs_\bt program will balk (and rightly  so)  at  poorly  formatted
       messages, and _\bd_\bi_\bs_\bt won't correct things for you.

       If _\bw_\bh_\ba_\bt_\bn_\bo_\bw_\bp_\br_\bo_\bc is _\bw_\bh_\ba_\bt_\bn_\bo_\bw, then _\bd_\bi_\bs_\bt uses a  built-in  _\bw_\bh_\ba_\bt_\bn_\bo_\bw,  it
       does  not  actually  run the _\bw_\bh_\ba_\bt_\bn_\bo_\bw program.  Hence, if you define
       your own _\bw_\bh_\ba_\bt_\bn_\bo_\bw_\bp_\br_\bo_\bc, don't call it _\bw_\bh_\ba_\bt_\bn_\bo_\bw since  _\bd_\bi_\bs_\bt  won't  run
       it.

       If your current working directory is not writable, the  link  named
       "@" is not available.






























\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  FOLDER(1)                         -33-                         FOLDER(1)


  _\bN_\bA_\bM_\bE
       folder, folders - set/list current folder/message

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       folder [+folder] [msg] [-all] [-fast] [-nofast] [-header]
            [-noheader] [-pack] [-nopack] [-recurse] [-norecurse] [-total]
            [-nototal] [-print] [-noprint] [-list] [-nolist] [-push]
            [-pop] [-help]

       folders

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       Since the _\bM_\bH environment is the shell, it is easy to lose track  of
       the current folder from day to day.

       When _\bf_\bo_\bl_\bd_\be_\br is given the `-print' switch (the default), the current
       folder  and/or  message  may  be set, or all folders may be listed.
       When a `+folder' argument is given,  this  corresponds  to  a  "cd"
       operation  in the _\bC_\bS_\bh_\be_\bl_\bl; when no `+folder' argument is given, this
       corresponds roughly to a "pwd" operation in the _\bC_\bS_\bh_\be_\bl_\bl.

       _\bF_\bo_\bl_\bd_\be_\br will list the current folder, the number of messages in  it,
       the  range  of  the  messages  (low-high),  and the current message
       within the folder, and will flag extra files  if  they  exist.   An
       example of the output is:

       inbox+            has  16 messages (  3- 22); cur=  5.

       If a `+folder' and/or `msg' are specified,  they  will  become  the
       current  folder  and/or  message.  Specifying `-all' will produce a
       line for each folder in the user's MH directory, sorted  alphabeti-
       cally.   These folders are preceded by the read-only folders, which
       occur as "atr-cur-" entries in the user's _\bM_\bH context.  For example,

       Folder               # of messages ( range )  cur msg (other files)
       /fsd/rs/m/tacc    has  35 messages (  1- 35); cur= 23.
       /rnd/phyl/Mail/EP has  82 messages (  1-108); cur= 82.
       ff                has  no messages.
       inbox+            has  16 messages (  3- 22); cur=  5.
       mh                has  76 messages (  1- 76); cur= 70.
       notes             has   2 messages (  1-  2); cur=  1.
       ucom              has 124 messages (  1-124); cur=  6; (others).
                 TOTAL=      339 messages in 7 folders

       The "+" after inbox indicates that it is the current  folder.   The
       "(others)"  indicates that the folder `ucom' has files which aren't
       messages.  These files may either be  sub-folders,  or  files  that
       don't belong under the MH file naming scheme.

       The header is output if either an `-all' or a `-header'  switch  is
       specified;  it  is  suppressed  by `-noheader'.  Also, if _\bf_\bo_\bl_\bd_\be_\br is

  [mh.6]                           MH.6.7                      UCI version









  FOLDER(1)                         -34-                         FOLDER(1)


       invoked by a name ending  with  "s"  (e.g.,  _\bf_\bo_\bl_\bd_\be_\br_\bs ),  `-all'  is
       assumed.  A `-total' switch will produce only the summary line.

       If a `+folder' and/or `msg' is given along with the `-all'  switch,
       _\bf_\bo_\bl_\bd_\be_\br  will, in addition to setting the current folder and/or mes-
       sage, list the top-level  folders  for  the  current  folder  (with
       `-norecurse')  or  list all folders under the current folder recur-
       sively (with `-recurse').

       If `-fast' is given, only the folder name (or names in the case  of
       `-all')  will  be listed.  (This is faster because the folders need
       not be read.)

       The `-pack' switch will compress the message  names  in  a  folder,
       removing holes in message numbering.

       The `-recurse' switch will list each folder  recursively.   Use  of
       this  option  effectively  defeats  the  speed  enhancement  of the
       `-fast' option, since each folder must be searched for  subfolders.
       Nevertheless, the combination of these options is useful.

       If the specified (or default) folder doesn't exist, the  user  will
       be  queried as to whether the folder should be created.  When stan-
       dard input is not a tty, the folder is created without  any  query.
       (This is the easy way to create an empty folder for use later.)

       The `-push' switch directs _\bf_\bo_\bl_\bd_\be_\br to push the current  folder  onto
       the  _\bf_\bo_\bl_\bd_\be_\br-_\bs_\bt_\ba_\bc_\bk,  and  make  the  `+folder'  argument the current
       folder.  If `+folder' is not given, the current folder and the  top
       of the _\bf_\bo_\bl_\bd_\be_\br-_\bs_\bt_\ba_\bc_\bk are exchanged.  This corresponds to the "pushd"
       operation in the _\bC_\bS_\bh_\be_\bl_\bl.

       The `-pop'  switch  directs  _\bf_\bo_\bl_\bd_\be_\br  to  discard  the  top  of  the
       _\bf_\bo_\bl_\bd_\be_\br-_\bs_\bt_\ba_\bc_\bk,  after  setting the current folder to that value.  No
       `+folder' argument is allowed.   This  corresponds  to  the  "popd"
       operation  in the _\bC_\bS_\bh_\be_\bl_\bl.  The `-push' switch and the `-pop' switch
       are mutually exclusive: the last occurrence of either one overrides
       any previous occurrence of the other.

       The `-list' switch directs _\bf_\bo_\bl_\bd_\be_\br  to  list  the  contents  of  the
       _\bf_\bo_\bl_\bd_\be_\br-_\bs_\bt_\ba_\bc_\bk.   No `+folder' argument is allowed.  After a success-
       ful  `-push'  or  `-pop',  the  `-list'  action  is  taken.    This
       corresponds to the "dirs" operation in the _\bC_\bS_\bh_\be_\bl_\bl.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile





\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  FOLDER(1)                         -35-                         FOLDER(1)


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Current-Folder:      To find the default current folder
       Folder-Protect:      To set mode when creating a new folder
       Folder-Stack:        To determine the folder stack
       lsproc:              Program to list the contents of a folder


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       refile(1), mhpath(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to the current folder
       `msg' defaults to none
       `-nofast'
       `-noheader'
       `-nototal'
       `-nopack'
       `-norecurse'
       `-print' is the default if no `-list', `-push', or `-pop' is specified


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       If `+folder' and/or `msg' are given, they will become  the  current
       folder and/or message.


  _\bH_\bi_\bs_\bt_\bo_\br_\by
       In previous versions of _\bM_\bH, the `-fast'  switch  prevented  context
       changes  from  occurring for the current folder.  This is no longer
       the case: if `+folder' is given, then _\bf_\bo_\bl_\bd_\be_\br will always change the
       current folder to that.


















\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  FORW(1)                           -36-                           FORW(1)


  _\bN_\bA_\bM_\bE
       forw - forward messages

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       forw [+folder] [msgs] [-annotate] [-noannotate]
            [-draftfolder +folder] [-draftmessage msg] [-nodraftfolder]
            [-editor editor] [-noedit] [-filter filterfile]
            [-form formfile] [-format] [-noformat] [-inplace] [-noinplace]
            [-whatnowproc program] [-nowhatnowproc] [-help]

       forw [+folder] [msgs] [-digest list] [-issue number]
            [-volume number] [other switches for _\bf_\bo_\br_\bw] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bF_\bo_\br_\bw may be used to prepare a message  containing  other  messages.
       It   constructs  the  new  message  from  the  components  file  or
       `-form formfile'  (see  _\bc_\bo_\bm_\bp ),  with  a  body  composed   of   the
       message(s)  to  be forwarded.  An editor is invoked as in _\bc_\bo_\bm_\bp, and
       after editing is complete, the user is prompted before the  message
       is sent.

       The default message form contains the following elements:

            To:
            cc:
            Subject:
            --------

       If the file named "forwcomps" exists in the user's MH directory, it
       will be used instead of this form.  In either case, the file speci-
       fied by `-form formfile' will be used if given.

       If the draft already exists, _\bf_\bo_\br_\bw will ask you as to  the  disposi-
       tion  of  the  draft.  A reply of quit will abort _\bf_\bo_\br_\bw, leaving the
       draft intact; replace will replace the existing draft with a  blank
       skeleton; and list will display the draft.

       If the `-annotate' switch is given, each  message  being  forwarded
       will be annotated with the lines

            Forwarded: date
            Forwarded: addrs

       where each address list contains as many lines as  required.   This
       annotation  will  be done only if the message is sent directly from
       _\bf_\bo_\br_\bw.   If  the  message  is  not  sent  immediately   from   _\bf_\bo_\br_\bw,
       "comp -use"  may  be  used to re-edit and send the constructed mes-
       sage, but the annotations won't take place.  The '-inplace'  switch
       causes annotation to be done in place in order to preserve links to
       the annotated message.
\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  FORW(1)                           -37-                           FORW(1)


       See _\bc_\bo_\bm_\bp (1) for a  description  of  the  `-editor'  and  `-noedit'
       switches.

       Although _\bf_\bo_\br_\bw uses the `-form formfile' switch to direct it how  to
       construct  the  beginning  of  the draft, the `-filter filterfile',
       `-format', and `-noformat' switches direct _\bf_\bo_\br_\bw as to how each for-
       warded  message  should  be formatted in the body of the draft.  If
       `-noformat' is specified, then each  forwarded  message  is  output
       exactly  as  it  appears.   If `-format' or `-filter filterfile' is
       specified, then each forwarded message is  filtered  (re-formatted)
       prior  to  being  output to the body of the draft.  The filter file
       for _\bf_\bo_\br_\bw should be a standard form  file  for  _\bm_\bh_\bl,  as  _\bf_\bo_\br_\bw  will
       invoke  _\bm_\bh_\bl  to format the forwarded messages.  The default message
       filter (what you get with `-format') is:

            width=80,overflowtext=,overflowoffset=10
            leftadjust,compress,compwidth=9
            Date:formatfield="%<(nodate{text})%{text}%|%(tws{text})%>"
            From:
            To:
            cc:
            Subject:
            :
            body:nocomponent,overflowoffset=0,noleftadjust,nocompress

       If the file named "mhl.forward" exists in the user's MH  directory,
       it  will  be  used  instead of this form.  In either case, the file
       specified by `-filter filterfile' will be used if given.   To  sum-
       marize:  `-noformat' will reproduce each forwarded message exactly,
       `-format' will use _\bm_\bh_\bl and a default filterfile, "mhl.forward",  to
       format  each  forwarded  message, and `-filter filterfile' will use
       the named filterfile to format each forwarded message with _\bm_\bh_\bl.

       Each forwarded message is separated with an encapsulation delimiter
       and  dashes  in  the first column of the forwarded messages will be
       prepended with `- ' so that when received, the message is  suitable
       for  bursting  by  _\bb_\bu_\br_\bs_\bt (1).   This  follows  the Internet RFC-934
       guidelines.

       For users of  _\bp_\br_\bo_\bm_\bp_\bt_\be_\br (1),  by  specifying  prompter's  `-prepend'
       switch  in  the  .mh_profile  file,  any commentary text is entered
       before the forwarded messages.  (A major win!)

       The `-draftfolder +folder' and `-draftmessage msg' switches  invoke
       the _\bM_\bH draft folder facility.  This is an advanced (and highly use-
       ful) feature.  Consult the Advanced  Features  section  of  the  _\bM_\bH
       manual for more information.

       Upon exiting from the editor, _\bf_\bo_\br_\bw will invoke the _\bw_\bh_\ba_\bt_\bn_\bo_\bw program.
       See _\bw_\bh_\ba_\bt_\bn_\bo_\bw (1) for a discussion of available options.  The invoca-
       tion of this program can be inhibited by using the `-nowhatnowproc'
       switch.   (In truth of fact, it is the _\bw_\bh_\ba_\bt_\bn_\bo_\bw program which starts

  [mh.6]                           MH.6.7                      UCI version









  FORW(1)                           -38-                           FORW(1)


       the initial edit.  Hence, `-nowhatnowproc' will  prevent  any  edit
       from occurring.)

       The `-digest list', `-issue number', and `-volume number'  switches
       implement  a  digest  facility  for  _\bM_\bH.  Specifying these switches
       enables and/or overloads the following escapes:

       _\bT_\by_\bp_\be       _\bE_\bs_\bc_\ba_\bp_\be  _\bR_\be_\bt_\bu_\br_\bn_\bs  _\bD_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn
       _\bc_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt  _\bd_\bi_\bg_\be_\bs_\bt  string   Argument to `-digest'
       _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn   _\bc_\bu_\br     integer  Argument to `-volume'
       _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn   _\bm_\bs_\bg     integer  Argument to `-issue'

       Consult the Advanced Features section of the _\bM_\bH User's  Manual  for
       more information on making digests.

  _\bF_\bi_\bl_\be_\bs
       /usr/local/lib/mh/forwcomps         The message skeleton
       or <mh-dir>/forwcomps               Rather than the standard skeleton
       /usr/local/lib/mh/digestcomps       The message skeleton if `-digest' is given
       or <mh-dir>/digestcomps             Rather than the standard skeleton
       /usr/local/lib/mh/mhl.forward       The message filter
       or <mh-dir>/mhl.forward             Rather than the standard filter
       $HOME/.mh_profile                   The user profile
       <mh-dir>/draft                      The draft file


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Current-Folder:      To find the default current folder
       Draft-Folder:        To find the default draft-folder
       Editor:              To override the default editor
       Msg-Protect:         To  set  mode  when  creating  a  new  message
       (draft)
       fileproc:            Program to refile the message
       mhlproc:             Program to filter messages being forwarded
       whatnowproc:         Program to ask the "What now?" questions


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       _\bP_\br_\bo_\bp_\bo_\bs_\be_\bd _\bS_\bt_\ba_\bn_\bd_\ba_\br_\bd _\bf_\bo_\br _\bM_\be_\bs_\bs_\ba_\bg_\be _\bE_\bn_\bc_\ba_\bp_\bs_\bu_\bl_\ba_\bt_\bi_\bo_\bn (aka RFC-934),
       comp(1), dist(1), repl(1), send(1), whatnow(1), mh-format(5)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to the current folder
       `msgs' defaults to cur
       `-noannotate'
       `-nodraftfolder'
       `-noformat'
       `-noinplace'

\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  FORW(1)                           -39-                           FORW(1)


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       If a folder is given, it will become the current folder.  The first
       message forwarded will become the current message.


  _\bB_\bu_\bg_\bs
       If _\bw_\bh_\ba_\bt_\bn_\bo_\bw_\bp_\br_\bo_\bc is _\bw_\bh_\ba_\bt_\bn_\bo_\bw, then _\bf_\bo_\br_\bw uses a  built-in  _\bw_\bh_\ba_\bt_\bn_\bo_\bw,  it
       does  not  actually  run the _\bw_\bh_\ba_\bt_\bn_\bo_\bw program.  Hence, if you define
       your own _\bw_\bh_\ba_\bt_\bn_\bo_\bw_\bp_\br_\bo_\bc, don't call it _\bw_\bh_\ba_\bt_\bn_\bo_\bw since  _\bf_\bo_\br_\bw  won't  run
       it.

       When _\bf_\bo_\br_\bw is told to annotate the messages it forwards, it  doesn't
       actually  annotate  them  until the draft is successfully sent.  If
       from the _\bw_\bh_\ba_\bt_\bn_\bo_\bw_\bp_\br_\bo_\bc, you _\bp_\bu_\bs_\bh instead of _\bs_\be_\bn_\bd,  it's  possible  to
       confuse   _\bf_\bo_\br_\bw   by   re-ordering   the   file   (e.g.,   by  using
       `folder -pack') before the message is successfully sent.  _\bD_\bi_\bs_\bt  and
       _\br_\be_\bp_\bl don't have this problem.

       To avoid prepending the leading dash characters in  forwarded  mes-
       sages,  there  is  a  `-nodashmunging'  option.   See  the  "Hidden
       Features" section of the _\bM_\bH _\bA_\bd_\bm_\bi_\bn_\bi_\bs_\bt_\br_\ba_\bt_\bo_\br'_\bs _\bG_\bu_\bi_\bd_\be for more details.






























\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  INC(1)                            -40-                            INC(1)


  _\bN_\bA_\bM_\bE
       inc - incorporate new mail

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       inc [+folder] [-audit audit-file] [-noaudit] [-changecur]
            [-nochangecur] [-form formatfile] [-format string]
            [-file name] [-silent] [-nosilent] [-truncate] [-notruncate]
            [-width columns] [-host host] [-user user] [-pack file]
            [-nopack] [-rpop] [-norpop] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bI_\bn_\bc incorporates mail from the user's incoming mail drop into an _\bM_\bH
       folder.   If `+folder' isn't specified, the folder named "inbox" in
       the user's _\bM_\bH directory will  be  used.   The  new  messages  being
       incorporated  are  assigned  numbers starting with the next highest
       number in the folder.  If the specified (or default) folder doesn't
       exist, the user will be queried prior to its creation.  As the mes-
       sages are processed, a _\bs_\bc_\ba_\bn listing of the new mail is produced.

       If the user's profile contains a "Msg-Protect: nnn" entry, it  will
       be  used as the protection on the newly created messages, otherwise
       the _\bM_\bH default of 0644 will be used.  During all operations on mes-
       sages,  this  initially  assigned  protection will be preserved for
       each message, so _\bc_\bh_\bm_\bo_\bd(1) may be used to set  a  protection  on  an
       individual   message,   and   its   protection  will  be  preserved
       thereafter.

       If the  switch  `-audit audit-file'  is  specified  (usually  as  a
       default  switch in the profile), then _\bi_\bn_\bc will append a header line
       and a line per message to the end of the specified audit-file  with
       the format:

            <<inc>> date
                 <scan line for first message>
                 <scan line for second message>
                           <etc.>

       This is useful for keeping track of volume and source  of  incoming
       mail.   Eventually,  _\br_\be_\bp_\bl,  _\bf_\bo_\br_\bw,  _\bc_\bo_\bm_\bp,  and _\bd_\bi_\bs_\bt may also produce
       audits to this (or another) file, perhaps with "Message-Id:" infor-
       mation  to keep an exact correspondence history.  "Audit-file" will
       be in the user's MH directory unless a full path is specified.

       _\bI_\bn_\bc will incorporate even improperly formatted  messages  into  the
       user's  MH  folder,  inserting  a blank line prior to the offending
       component and printing a comment identifying the bad message.

       In all cases, the user's mail  drop  will  be  zeroed,  unless  the
       `-notruncate' switch is given.

       If the profile entry "Unseen-Sequence" is  present  and  non-empty,

  [mh.6]                           MH.6.7                      UCI version









  INC(1)                            -41-                            INC(1)


       then  _\bi_\bn_\bc  will add each of the newly incorporated messages to each
       sequence named by the  profile  entry.   This  is  similar  to  the
       "Previous-Sequence"  profile  entry  supported  by  all _\bM_\bH commands
       which take `msgs' or `msg' arguments.  Note that _\bi_\bn_\bc will not  zero
       each sequence prior to adding messages.

       The interpretation of the `-form formatfile', `-format string', and
       `-width columns' switches is the same as in _\bs_\bc_\ba_\bn (1).

       By using the `-file name' switch, one can direct _\bi_\bn_\bc to incorporate
       messages from a file other than the user's maildrop.  Note that the
       name file will NOT be zeroed,  unless  the  `-truncate'  switch  is
       given.

       If the envariable $MAILDROP is set, then _\bi_\bn_\bc uses it as  the  loca-
       tion  of  the  user's  maildrop  instead  of  the  default  (the `-
       file name' switch still overrides this, however).  If this  envari-
       able is not set, then _\bi_\bn_\bc will consult the profile entry "MailDrop"
       for this information.  If the value found is not absolute, then  it
       is  interpreted  relative to the user's _\bM_\bH directory.  If the value
       is not found, then _\bi_\bn_\bc will look in the  standard  system  location
       for the user's maildrop.

       The `-silent' switch directs _\bi_\bn_\bc to be quiet and not ask any  ques-
       tions at all.  This is useful for putting _\bi_\bn_\bc in the background and
       going on to other things.

       If the local host  is  configured  as  a  POP  client,  or  if  the
       `-host host'  switch  is given, then _\bi_\bn_\bc will query the POP service
       host as to the status of mail waiting.  The `-user user' switch may
       be  given  to  specify  the  name of the POP subscriber you wish to
       check mail for on the POP service host.  The  `-rpop'  switch  uses
       the  UNIX  _\br_\bP_\bO_\bP  (authentication done via trusted connections).  In
       contrast, the `-norpop' switch uses the ARPA _\bP_\bO_\bP (in which case _\bi_\bn_\bc
       will prompt for a password).

       If _\bi_\bn_\bc uses POP, then the `-pack file' switch  is  considered.   If
       given,  then  _\bi_\bn_\bc simply uses the POP to _\bp_\ba_\bc_\bk_\bf (1) the user's mail-
       drop from the POP service host to the named file.  This  switch  is
       provided  for those users who prefer to use _\bm_\bs_\bh to read their mail-
       drops.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile
       /usr/local/lib/mh/mtstailor         tailor file
       /usr/spool/mail/$USER               Location of mail drop





\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  INC(1)                            -42-                            INC(1)


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Alternate-Mailboxes: To determine the user's mailboxes
       Folder-Protect:      To set mode when creating a new folder
       Msg-Protect:         To set mode when creating a  new  message  and
       audit-file
       Unseen-Sequence:     To name sequences denoting unseen messages


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       _\bP_\bo_\bs_\bt _\bO_\bf_\bf_\bi_\bc_\be _\bP_\br_\bo_\bt_\bo_\bc_\bo_\bl - _\bv_\be_\br_\bs_\bi_\bo_\bn _\b3 (aka RFC-1081),
       mhmail(1), scan(1), mh-mail(5), post(8)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to "inbox"
       `-noaudit'
       `-changecur'
       `-format' defaulted as described above
       `-nosilent'
       `-truncate' if `-file name' not given, `-notruncate' otherwise
       `-width' defaulted to the width of the terminal
       `-nopack'
       `-rpop'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       The folder into which messages are being incorporated  will  become
       the current folder.  The first message incorporated will become the
       current message, unless the  `-nochangecur'  option  is  specified.
       This leaves the context ready for a _\bs_\bh_\bo_\bw of the first new message.


  _\bB_\bu_\bg_\bs
       The argument to the `-format' switch must be interpreted as a  sin-
       gle  token by the shell that invokes _\bi_\bn_\bc.  Therefore, one must usu-
       ally place the argument to this switch inside double-quotes.














\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MARK(1)                           -43-                           MARK(1)


  _\bN_\bA_\bM_\bE
       mark - mark messages

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       mark [+folder] [msgs] [-sequence name ...] [-add] [-delete] [-list]
            [-public] [-nopublic] [-zero] [-nozero] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       The _\bm_\ba_\br_\bk command manipulates message sequences by adding or  delet-
       ing  message  numbers from folder-specific message sequences, or by
       listing those sequences and messages.  A message sequence is a key-
       word,  just  like  one  of  the  "reserved"  message names, such as
       "first" or "next".  Unlike the "reserved" message names, which have
       a fixed semantics on a per-folder basis, the semantics of a message
       sequence may be defined, modified, and removed by the  user.   Mes-
       sage  sequences are folder-specific, e.g., the sequence name "seen"
       in the context of folder "+inbox" need not have any relation  what-
       soever  to the sequence of the same name in a folder of a different
       name.

       Three action switches direct the operation of _\bm_\ba_\br_\bk.  These switches
       are  mutually  exclusive:  the last occurrence of any of them over-
       rides any previous occurrence of the other two.

       The `-add' switch tells _\bm_\ba_\br_\bk to add messages  to  sequences  or  to
       create   a   new   sequence.   For  each  sequence  named  via  the
       `-sequence name' argument (which must occur at least once) the mes-
       sages  named  via  `msgs' (which defaults to "cur" if no `msgs' are
       given), are added to the sequence.  The messages to be  added  need
       not  be  absent from the sequence.  If the `-zero' switch is speci-
       fied, the sequence will be emptied prior to  adding  the  messages.
       Hence,  `-add -zero' means that each sequence should be initialized
       to the indicated messages, while  `-add -nozero'  means  that  each
       sequence should be appended to by the indicated messages.

       The `-delete' switch tells _\bm_\ba_\br_\bk to delete messages from  sequences,
       and  is  the  dual of `-add'.  For each of the named sequences, the
       named messages are removed from the sequence.  These messages  need
       not  be  already present in the sequence.  If the `-zero' switch is
       specified, then all messages in the  folder  are  appended  to  the
       sequence  prior  to  removing the messages.  Hence, `-delete -zero'
       means that each sequence should contain all messages  except  those
       indicated,  while  `-delete -nozero'  means that only the indicated
       messages should be removed from each sequence.   As  expected,  the
       command   `mark -sequence seen -delete all'  deletes  the  sequence
       "seen" from the current folder.

       When creating (or modifying) a sequence, the `-public' switch indi-
       cates that the sequence should be made readable for other _\bM_\bH users.
       In contrast, the `-nopublic' switch  indicates  that  the  sequence
       should be private to the user's _\bM_\bH environment.

  [mh.6]                           MH.6.7                      UCI version









  MARK(1)                           -44-                           MARK(1)


       The `-list' switch tells _\bm_\ba_\br_\bk to list both  the  sequences  defined
       for  the  folder  and the messages associated with those sequences.
       _\bM_\ba_\br_\bk will list each sequence named via `-sequence name' (or all  of
       them  if  `-sequence' isn't used), and the messages associated with
       that sequence.  The `-zero' switch does not affect the operation of
       `-list'.

       The current restrictions on sequences are:

         The name used to denote a message sequence  must  consist  of  an
         alphabetic  character followed by zero or more alphanumeric char-
         acters, and can not be one of the "reserved" message names (e.g.,
         "first", "cur", and so forth).

         Only a certain number of sequences may be  defined  for  a  given
         folder.  This number is usually limited to 10.

         Message ranges with user-defined sequence names are restricted to
         the  form  "name:n"  or "name:-n", and refer to the first or last
         `n' messages of the sequence `name', respectively.  Constructs of
         the form "name1-name2" are forbidden.

  _\bF_\bi_\bl_\be_\bs
      $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Current-Folder:      To find the default current folder


  _\bS_\be_\be _\bA_\bl_\bs_\bo
      pick (1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to the current folder
       `-add' if `-sequence' is specified, `-list' otherwise
       `msgs' defaults to cur (or all if `-list' is specified)
       `-nopublic' if the folder is read-only, `-public' otherwise
       `-nozero'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
      If a folder is given, it will become the current folder.






\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MHL(1)                            -45-                            MHL(1)


  _\bN_\bA_\bM_\bE
       mhl - produce formatted listings of MH messages

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       /usr/local/lib/mh/mhl [-bell] [-nobell] [-clear] [-noclear]
            [-folder +folder] [-form formfile] [-length lines]
            [-width columns] [-moreproc program] [-nomoreproc] [files ...]
            [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bM_\bh_\bl is a formatted message listing program.  It can be  used  as  a
       replacement  for  _\bm_\bo_\br_\be (1)  (the default _\bs_\bh_\bo_\bw_\bp_\br_\bo_\bc ).  As with _\bm_\bo_\br_\be,
       each of the messages specified as arguments (or the standard input)
       will  be  output.   If more than one message file is specified, the
       user will be prompted prior to each one, and a  <RETURN>  or  <EOT>
       will  begin  the  output,  with  <RETURN>  clearing  the screen (if
       appropriate), and <EOT> (usually  CTRL-D)  suppressing  the  screen
       clear.  An <INTERRUPT> (usually CTRL-C) will abort the current mes-
       sage output, prompting for the next message (if there is one),  and
       a  <QUIT> (usually CTRL-\) will terminate the program (without core
       dump).

       The `-bell' option tells _\bm_\bh_\bl to ring the terminal's bell at the end
       of  each  page,  while  the  `-clear' option tells _\bm_\bh_\bl to clear the
       scree at the end of each page (or output a formfeed after each mes-
       sage).   Both  of  these  switches (and their inverse counterparts)
       take effect only if the  profile  entry  _\bm_\bo_\br_\be_\bp_\br_\bo_\bc  is  defined  but
       empty,  and _\bm_\bh_\bl is outputting to a terminal.  If the _\bm_\bo_\br_\be_\bp_\br_\bo_\bc entry
       is defined and non-empty, and _\bm_\bh_\bl is outputting to a terminal, then
       _\bm_\bh_\bl  will  cause the _\bm_\bo_\br_\be_\bp_\br_\bo_\bc to be placed between the terminal and
       _\bm_\bh_\bl and the switches are ignored.   Furthermore,  if  the  `-clear'
       switch is used and _\bm_\bh_\bl'_\bs output is directed to a terminal, then _\bm_\bh_\bl
       will consult the $TERM and $TERMCAP envariables  to  determine  the
       user's  terminal type in order to find out how to clear the screen.
       If the `-clear' switch is used and _\bm_\bh_\bl'_\bs output is not directed  to
       a  terminal (e.g., a pipe or a file), then _\bm_\bh_\bl will send a formfeed
       after each message.

       To override the default _\bm_\bo_\br_\be_\bp_\br_\bo_\bc and the  profile  entry,  use  the
       `-moreproc program'  switch.   Note  that  _\bm_\bh_\bl  will  never start a
       _\bm_\bo_\br_\be_\bp_\br_\bo_\bc if invoked on a hardcopy terminal.

       The `-length length' and `-width width'  switches  set  the  screen
       length  and width, respectively.  These default to the values indi-
       cated by $TERMCAP, if appropriate, otherwise they default to 40 and
       80, respectively.

       The default format file used by _\bm_\bh_\bl is called _\bm_\bh_\bl._\bf_\bo_\br_\bm_\ba_\bt (which  is
       first  searched  for in the user's _\bM_\bH directory, and then sought in
       the /_\bu_\bs_\br/_\bl_\bo_\bc_\ba_\bl/_\bl_\bi_\bb/_\bm_\bh directory), this can be changed by using  the
       `-form formatfile' switch.

  [mh.6]                           MH.6.7                      UCI version









  MHL(1)                            -46-                            MHL(1)


       Finally, the `-folder +folder' switch  sets  the  _\bM_\bH  folder  name,
       which  is  used  for the "messagename:" field described below.  The
       envariable $mhfolder is consulted  for  the  default  value,  which
       _\bs_\bh_\bo_\bw, _\bn_\be_\bx_\bt, and _\bp_\br_\be_\bv initialize appropriately.

       _\bM_\bh_\bl operates in two phases: 1) read and parse the format file,  and
       2)  process  each  message  (file).   During  phase  1, an internal
       description of the format is produced as  a  structured  list.   In
       phase  2,  this list is walked for each message, outputting message
       information under the format constraints from the format file.

       The "mhl.format" form file contains information controlling  screen
       clearing,  screen size, wrap-around control, transparent text, com-
       ponent ordering, and component formatting.  Also, a  list  of  com-
       ponents  to ignore may be specified, and a couple of "special" com-
       ponents are defined to provide added functionality.  Message output
       will be in the order specified by the order in the format file.

       Each line of mhl.format has one of the formats:

            ;comment
            :cleartext
            variable[,variable...]
            component:[variable,...]

       A line beginning with a `;' is a comment, and is ignored.   A  line
       beginning with a `:' is clear text, and is output exactly as is.  A
       line containing only a `:' produces a blank line in the output.   A
       line  beginning with "component:" defines the format for the speci-
       fied component, and finally,  remaining  lines  define  the  global
       environment.

       For example, the line:

            width=80,length=40,clearscreen,overflowtext="***",overflowoffset=5

       defines the screen size to be 80 columns by 40 rows, specifies that
       the screen should be cleared prior to each page, that the  overflow
       indentation  is  5,  and  that overflow text should be flagged with
       "***".

       Following are all of the current variables and their arguments.  If
       they  follow a component, they apply only to that component, other-
       wise, their affect is global.  Since the  whole  format  is  parsed
       before  any output processing, the last global switch setting for a
       variable applies to the whole message if that variable is used in a
       global context (i.e., bell, clearscreen, width, length).

            _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be       _\bt_\by_\bp_\be       _\bs_\be_\bm_\ba_\bn_\bt_\bi_\bc_\bs
            width          integer    screen width or component width
            length         integer    screen length or component length
            offset         integer    positions to indent "component: "

  [mh.6]                           MH.6.7                      UCI version









  MHL(1)                            -47-                            MHL(1)


            overflowtext   string     text to use at the beginning of an
                                      overflow line
            overflowoffset integer    positions to indent overflow lines
            compwidth      integer    positions to indent component text
                                      after the first line is output
            uppercase      flag       output text of this component in all
                                      upper case
            nouppercase    flag       don't uppercase
            clearscreen    flag/G     clear the screen prior to each page
            noclearscreen  flag/G     don't clearscreen
            bell           flag/G     ring the bell at the end of each page
            nobell         flag/G     don't bell
            component      string/L   name to use instead of "component" for
                                      this component
            nocomponent    flag       don't output "component: " for this
                                      component
            center         flag       center component on line (works for
                                      one-line components only)
            nocenter       flag       don't center
            leftadjust     flag       strip off leading whitespace on each
                                      line of text
            noleftadjust   flag       don't leftadjust
            compress       flag       change newlines in text to spaces
            nocompress     flag       don't compress
            split          flag       don't combine multiple fields into a single field
            nosplit        flag       combine multiple fields into a single field
            formatfield    string     format string for this component (see below)
            addrfield      flag       field contains addresses
            datefield      flag       field contains dates

       To specify the value of integer-valued and string-valued variables,
       follow   their   name   with   an   equals-sign   and   the  value.
       Integer-valued  variables   are   given   decimal   values,   while
       string-valued  variables  are  given  arbirtray  text  bracketed by
       double-quotes.  If a value is suffixed by "/G" or  "/L",  then  its
       value  is  useful  in  a global-only or local-only context (respec-
       tively).

       A line of the form:

           ignores=component,...

       specifies a list of components which are never output.

       The component  "MessageName"  (case-insensitive)  will  output  the
       actual  message name (file name) preceded by the folder name if one
       is specified or found in the environment.  The format is  identical
       to that produced by the `-header' option to _\bs_\bh_\bo_\bw.

       The component "Extras" will output all of  the  components  of  the
       message  which were not matched by explicit components, or included
       in the ignore list.  If this component is not specified, an  ignore

  [mh.6]                           MH.6.7                      UCI version









  MHL(1)                            -48-                            MHL(1)


       list  is  not  needed  since  all  non-specified components will be
       ignored.

       If "nocomponent" is NOT specified, then the component name will  be
       output as it appears in the format file.

       The default format is:

            : -- using template mhl.format --
            overflowtext="***",overflowoffset=5
            leftadjust,compwidth=9
            ignores=msgid,message-id,received
            Date:formatfield="%<(nodate{text})%{text}%|%(pretty{text})%>"
            To:
            cc:
            :
            From:
            Subject:
            :
            extras:nocomponent
            :
            body:nocomponent,overflowtext=,overflowoffset=0,noleftadjust

       The  variable  "formatfield"  specifies  a   format   string   (see
       _\bm_\bh-_\bf_\bo_\br_\bm_\ba_\bt (5)).   The  flag  variables  "addrfield" and "datefield"
       (which are mutually exclusive), tell _\bm_\bh_\bl to interpret  the  escapes
       in the format string as either addresses or dates, respectively.

       By default, _\bm_\bh_\bl does not apply any formatting string to fields con-
       taining  address  or  dates  (see  _\bm_\bh-_\bm_\ba_\bi_\bl (5)  for a list of these
       fields).  Note that this results in faster operation since _\bm_\bh_\bl must
       parse both addresses and dates in order to apply a format string to
       them.  If desired, _\bm_\bh_\bl can be given a  default  format  string  for
       either  address  or  date  fields (but not both).  To do this, on a
       global line specify: either the flag addrfield or datefield,  along
       with the apropriate formatfield variable string.

  _\bF_\bi_\bl_\be_\bs
       /usr/local/lib/mh/mhl.format        The message template
       or <mh-dir>/mhl.format              Rather than the standard template
       $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       moreproc:            Program to use as interactive front-end


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       show(1), ap(8), dp(8)


\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MHL(1)                            -49-                            MHL(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `-bell'
       `-noclear'
       `-length 40'
       `-width 80'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None


  _\bB_\bu_\bg_\bs
       There should be some way to pass `bell' and `clear' information  to
       the front-end.

       On hosts where _\bM_\bH was configured  with  the  BERK  option,  address
       parsing is not enabled.


































\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MHMAIL(1)                         -50-                         MHMAIL(1)


  _\bN_\bA_\bM_\bE
       mhmail - send or read mail

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       mhmail [ addrs ... [-body text] [-cc addrs ...] [-from addr]
            [-subject subject]] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bM_\bH_\bm_\ba_\bi_\bl is intended as a replacement for the standard Bell mail pro-
       gram  (_\bb_\be_\bl_\bl_\bm_\ba_\bi_\bl (1)),  compatible  with  _\bM_\bH.   When invoked without
       arguments, it simply invokes _\bi_\bn_\bc (1) to  incorporate  new  messages
       from  the  user's maildrop.  When one or more users is specified, a
       message is read from the standard input and spooled to a  temporary
       file.   _\bM_\bH_\bm_\ba_\bi_\bl then invokes _\bp_\bo_\bs_\bt (8) with the name of the temporary
       file as its argument to deliver the message to the specified user.

       The `-subject subject' switch can be used to specify the "Subject:"
       field  of  the  message.   The  `-body text'  switch can be used to
       specify the text of the message; if it is specified, then the stan-
       dard input is not read.  Normally, addresses appearing as arguments
       are put in the "To:" field.  If  the  `-cc'  switch  is  used,  all
       addresses following it are placed in the "cc:" field.

       By using `-from addr', you can specify the "From:"  header  of  the
       draft.    Naturally,   _\bp_\bo_\bs_\bt   will  fill-in  the  "Sender:"  header
       correctly.

       This program is intended for the use of programs  such  as  _\ba_\bt (1),
       which  expect  to  send  mail automatically to various users.  Nor-
       mally, real people (as opposed to the "unreal" ones) will prefer to
       use _\bc_\bo_\bm_\bp (1) and _\bs_\be_\bn_\bd (1) to send messages.

  _\bF_\bi_\bl_\be_\bs
       /usr/local/inc                      Program to incorporate a maildrop into a folder
       /usr/local/lib/mh/post              Program to deliver a message
       /tmp/mhmail*                        Temporary copy of message


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       None


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       inc(1), post(8)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       None


\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MHMAIL(1)                         -51-                         MHMAIL(1)


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       If _\bi_\bn_\bc is invoked, then _\bi_\bn_\bc's context changes occur.

















































\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MHOOK(1)                          -52-                          MHOOK(1)


  _\bN_\bA_\bM_\bE
       mhook - MH receive-mail hooks

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       $HOME/.maildelivery

       /usr/local/lib/mh/rcvdist [-form formfile] [switches for _\bp_\bo_\bs_\bt_\bp_\br_\bo_\bc]
            address ...  [-help]

       /usr/local/lib/mh/rcvpack file [-help]

       /usr/local/lib/mh/rcvtty [command] [-form formatfile]
            [-format string] [-bell] [-nobell] [-newline] [-nonewline]
            [-biff] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       A receive-mail hook is a program that is run whenever you receive a
       mail message.  You do NOT invoke the hook yourself, rather the hook
       is invoked on your behalf by _\bM_\bM_\bD_\bF.

       The ._\bm_\ba_\bi_\bl_\bd_\be_\bl_\bi_\bv_\be_\br_\by file, which is an ordinary ASCII  file,  controls
       how  local  delivery  is performed.  This file is read by the local
       channel.  See _\bm_\ba_\bi_\bl_\bd_\be_\bl_\bi_\bv_\be_\br_\by (5) for the details.

       Four programs are currently standardly available,  _\br_\bc_\bv_\bd_\bi_\bs_\bt  (redis-
       tribute  incoming messages to additional recipients), _\br_\bc_\bv_\bp_\ba_\bc_\bk (save
       incoming messages in a _\bp_\ba_\bc_\bk_\bf'd file), and _\br_\bc_\bv_\bt_\bt_\by  (notify  user  of
       incoming  messages).  The fourth program, _\br_\bc_\bv_\bs_\bt_\bo_\br_\be (1) is described
       separately.  They all reside in the /_\bu_\bs_\br/_\bl_\bo_\bc_\ba_\bl/_\bl_\bi_\bb/_\bm_\bh/ directory.

       The _\br_\bc_\bv_\bd_\bi_\bs_\bt program will resend a copy of the message to all of the
       addresses  listed  on  its command line.  It uses the format string
       facility described in _\bm_\bh-_\bf_\bo_\br_\bm_\ba_\bt (5).

       The _\br_\bc_\bv_\bp_\ba_\bc_\bk program will append a copy of the message to  the  file
       listed  on  its  command  line.  Its use is obsoleted by the ._\bm_\ba_\bi_\bl_\b-
       _\bd_\be_\bl_\bi_\bv_\be_\br_\by.

       The _\br_\bc_\bv_\bt_\bt_\by program executes the named file with the message as  its
       standard input, and writes the resulting output on your terminal.

       If no file is specified,  or  is  bogus,  etc.,  then  _\br_\bc_\bv_\bt_\bt_\by  will
       instead    write    a    one-line   scan   listing.    Either   the
       `-form formatfile' or `-format string' option may be used to  over-
       ride  the  default output format (see _\bm_\bh-_\bf_\bo_\br_\bm_\ba_\bt (5)).  A newline is
       output before the message output, and the  terminal  bell  is  rung
       after  the  output.   The  `-nonewline'  and `-nobell' options will
       inhibit these functions.

       Normally, _\br_\bc_\bv_\bt_\bt_\by obeys write permission  as  granted  by  _\bm_\be_\bs_\bg (1).
       With  the  `-biff' option, _\br_\bc_\bv_\bt_\bt_\by will obey the notification status

  [mh.6]                           MH.6.7                      UCI version









  MHOOK(1)                          -53-                          MHOOK(1)


       set by _\bb_\bi_\bf_\bf (1).  If the terminal access daemon (TTYD) is available
       on  your system, then _\br_\bc_\bv_\bt_\bt_\by will give its output to the daemon for
       output instead of writing on the user's terminal.

  _\bF_\bi_\bl_\be_\bs
       /usr/local/lib/mh/mtstailor         tailor file
       $HOME/.maildelivery                 The file controlling local delivery
       /usr/local/lib/mh/maildelivery      Rather than the standard file


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       rcvstore (1), maildelivery(5), mh-format(5)


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None


  _\bB_\bu_\bg_\bs
       Only two return codes are meaningful, others should be.

       Versions of _\bM_\bM_\bD_\bF with the _\bm_\ba_\bi_\bl_\bd_\be_\bl_\bi_\bv_\be_\br_\by  mechanism  aren't  entirely
       backwards-compatible   with  earlier  versions.   If  you  have  an
       old-style hook, the best you can do is to have  a  one-line  ._\bm_\ba_\bi_\bl-
       _\bd_\be_\bl_\bi_\bv_\be_\br_\by file:

        default - pipe A "bin/rcvmail $(address) $(info) $(sender)"
























\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MHPATH(1)                         -54-                         MHPATH(1)


  _\bN_\bA_\bM_\bE
       mhpath - print full pathnames of MH messages and folders

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       mhpath [+folder] [msgs] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bM_\bh_\bp_\ba_\bt_\bh expands and sorts the message list  `msgs'  and  writes  the
       full  pathnames of the messages to the standard output separated by
       newlines.  If no `msgs' are specified, _\bm_\bh_\bp_\ba_\bt_\bh  outputs  the  folder
       pathname  instead.   If  the  only argument is `+', your MH _\bP_\ba_\bt_\bh is
       output; this can be useful is shell scripts.

       Contrasted with other MH commands, a message argument to _\bm_\bh_\bp_\ba_\bt_\bh may
       often  be intended for _\bw_\br_\bi_\bt_\bi_\bn_\bg.  Because of this: 1) the name "new"
       has been added to _\bm_\bh_\bp_\ba_\bt_\bh's list of reserved message names (the oth-
       ers  are  "first",  "last", "prev", "next", "cur", and "all").  The
       new message is equivalent to the message after the last message  in
       a  folder  (and equivalent to 1 in a folder without messages).  The
       "new" message may not be used as  part  of  a  message  range.   2)
       Within a message list, the following designations may refer to mes-
       sages that do not exist: a single numeric message name, the  single
       message  name "cur", and (obviously) the single message name "new".
       All other message designations must refer to at least one  existing
       message.  3) An empty folder is not in itself an error.

       Message numbers greater than the  highest  existing  message  in  a
       folder  as  part  of a range designation are replaced with the next
       free message number.

       Examples: The current folder foo contains messages 3 5 6.   Cur  is
       4.

            % mhpath
            /r/phyl/Mail/foo

            % mhpath all
            /r/phyl/Mail/foo/3
            /r/phyl/Mail/foo/5
            /r/phyl/Mail/foo/6

            % mhpath 2001
            /r/phyl/Mail/foo/7

            % mhpath 1-2001
            /r/phyl/Mail/foo/3
            /r/phyl/Mail/foo/5
            /r/phyl/Mail/foo/6

            % mhpath new
            /r/phyl/Mail/foo/7

  [mh.6]                           MH.6.7                      UCI version









  MHPATH(1)                         -55-                         MHPATH(1)


            % mhpath last new
            /r/phyl/Mail/foo/6
            /r/phyl/Mail/foo/7

            % mhpath last-new
            bad message list "last-new".

            % mhpath cur
            /r/phyl/Mail/foo/4

            % mhpath 1-2
            no messages in range "1-2".

            % mhpath first:2
            /r/phyl/Mail/foo/3
            /r/phyl/Mail/foo/5

            % mhpath 1 2
            /r/phyl/Mail/foo/1
            /r/phyl/Mail/foo/2

       _\bM_\bH_\bp_\ba_\bt_\bh is also useful in back-quoted operations:

            % cd `mhpath +inbox`

            % echo `mhpath +`
            /r/phyl/Mail

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Current-Folder:      To find the default current folder


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       folder(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to the current folder
       `msgs' defaults to none


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None



\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MHPATH(1)                         -56-                         MHPATH(1)


  _\bB_\bu_\bg_\bs
       Like all MH commands, _\bm_\bh_\bp_\ba_\bt_\bh expands and sorts  [msgs].   So  don't
       expect

            mv `mhpath 501 500`

       to move 501 to 500.  Quite the reverse.  But

            mv `mhpath 501` `mhpath 500`

       will do the trick.

       Out of range message 0 is treated far more severely than large  out
       of range message numbers.





































\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MSGCHK(1)                         -57-                         MSGCHK(1)


  _\bN_\bA_\bM_\bE
       msgchk - check for messages

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       msgchk [-date] [-nodate] [-notify all/mail/nomail]
            [-nonotify all/mail/nomail] [-host host] [-user user] [-rpop]
            [-norpop] [users ...] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       The _\bm_\bs_\bg_\bc_\bh_\bk program checks all known mail drops for mail waiting for
       you.  For those drops which have mail for you, _\bm_\bs_\bg_\bc_\bh_\bk will indicate
       if it believes that you have seen the mail in question before.

       The `-notify type' switch indicates under what circumstances _\bm_\bs_\bg_\bc_\bh_\bk
       should  produce a message.  The default is `-notify all' which says
       that _\bm_\bs_\bg_\bc_\bh_\bk should always report the status of the users  maildrop.
       Other  values  for  `type'  include  `mail'  which says that _\bm_\bs_\bg_\bc_\bh_\bk
       should report the status of waiting mail; and, `nomail' which  says
       that  _\bm_\bs_\bg_\bc_\bh_\bk  should  report  the  status  of empty maildrops.  The
       `-nonotify type' switch has the inverted sense, so  `-nonotify all'
       directs  _\bm_\bs_\bg_\bc_\bh_\bk  to  never report the status of maildrops.  This is
       useful if the  user  wishes  to  check  _\bm_\bs_\bg_\bc_\bh_\bk's  exit  status.   A
       non-zero  exit  status  indicates  that mail was not waiting for at
       least one of the indicated users.

       If _\bm_\bs_\bg_\bc_\bh_\bk produces output, then the `-date' switch  directs  _\bm_\bs_\bg_\bc_\bh_\bk
       to  print  out  the  last date mail was read, if this can be deter-
       mined.

       If the local host  is  configured  as  a  POP  client,  or  if  the
       `-host host'  switch  is  given,  _\bm_\bs_\bg_\bc_\bh_\bk will query the POP service
       host as to the status of mail waiting.  The `-user user' switch may
       be  given  to  specify  the  name of the POP subscriber you wish to
       check mail for on the POP service host.  The  `-rpop'  switch  uses
       the  UNIX  _\br_\bP_\bO_\bP  (authentication done via trusted connections).  In
       contrast, the `-norpop' switch uses the ARPA  _\bP_\bO_\bP  (in  which  case
       _\bm_\bs_\bg_\bc_\bh_\bk will prompt for a password).

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile
       /usr/local/lib/mh/mtstailor         tailor file
       /usr/spool/mail/$USER               Location of mail drop


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       None




\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MSGCHK(1)                         -58-                         MSGCHK(1)


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       _\bP_\bo_\bs_\bt _\bO_\bf_\bf_\bi_\bc_\be _\bP_\br_\bo_\bt_\bo_\bc_\bo_\bl - _\bv_\be_\br_\bs_\bi_\bo_\bn _\b3 (aka RFC-1081),
       inc(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `user' defaults to the current user
       `-date'
       `-notify all'
       `-rpop'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None





































\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MSH(1)                            -59-                            MSH(1)


  _\bN_\bA_\bM_\bE
       msh - MH shell (and BBoard reader)

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       msh [-prompt string] [-scan] [-noscan] [-topcur] [-notopcur] [file]
            [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bm_\bs_\bh is an interactive program that implements a subset of the  nor-
       mal _\bM_\bH commands operating on a single file in _\bp_\ba_\bc_\bk_\bf'd format.  That
       is, _\bm_\bs_\bh is used to read a file that contains a number of  messages,
       as  opposed  to the standard _\bM_\bH style of reading a number of files,
       each file being a separate message in a folder.  _\bm_\bs_\bh's chief advan-
       tage is that the normal _\bM_\bH style does not allow a file to have more
       than one message in it.  Hence, _\bm_\bs_\bh is ideal for  reading  _\bB_\bB_\bo_\ba_\br_\bd_\bs,
       as  these  files are delivered by the transport system in this for-
       mat.  In addition, _\bm_\bs_\bh can be used on other files, such as  message
       archives  which  have been _\bp_\ba_\bc_\bked (see _\bp_\ba_\bc_\bk_\bf (1)).  Finally, _\bm_\bs_\bh is
       an excellent _\bM_\bH tutor.  As the only commands available to the  user
       are  _\bM_\bH  commands,  this  allows _\bM_\bH beginners to concentrate on how
       commands to _\bM_\bH are formed and (more or less) what they mean.

       When invoked, _\bm_\bs_\bh reads the named file, and enters a command  loop.
       The  user  may type most of the normal _\bM_\bH commands.  The syntax and
       semantics of these commands typed to _\bm_\bs_\bh are identical to their  _\bM_\bH
       counterparts.   In  cases  where  the nature of _\bm_\bs_\bh would be incon-
       sistent (e.g., specifying a `+folder' with some commands), _\bm_\bs_\bh will
       duly inform the user.  The commands that _\bm_\bs_\bh currently supports (in
       some slightly modified or restricted forms) are:

            ali
            burst
            comp
            dist
            folder
            forw
            inc
            mark
            mhmail
            msgchk
            next
            packf
            pick
            prev
            refile
            repl
            rmm
            scan
            send
            show
            sortm

  [mh.6]                           MH.6.7                      UCI version









  MSH(1)                            -60-                            MSH(1)


            whatnow
            whom

       In addition, _\bm_\bs_\bh has a "help" command which gives a brief overview.
       To  terminate  _\bm_\bs_\bh, type CTRL-D, or use the "quit" command.  If _\bm_\bs_\bh
       is being invoked from _\bb_\bb_\bc, then typing CTRL-D will also tell _\bb_\bb_\bc to
       exit as well, while using the "quit" command will return control to
       _\bb_\bb_\bc, and _\bb_\bb_\bc will continue examining the list of BBoards that it is
       scanning.

       If the file is writable and has been modified,  then  using  "quit"
       will query the user if the file should be updated.

       The `-prompt string' switch sets the prompting string for _\bm_\bs_\bh.

       You may wish to use an alternate _\bM_\bH profile for the  commands  that
       _\bm_\bs_\bh  executes; see _\bm_\bh-_\bp_\br_\bo_\bf_\bi_\bl_\be (5) for details about the $MH envari-
       able.

       When invoked from _\bb_\bb_\bc, two special features are enabled: First, the
       `-scan' switch directs _\bm_\bs_\bh to do a `scan unseen' on start-up if new
       items are present in the BBoard.  This feature is  best  used  from
       _\bb_\bb_\bc,  which  correctly sets the stage.  Second, the _\bm_\ba_\br_\bk command in
       _\bm_\bs_\bh acts specially when you are reading a BBoard,  since  _\bm_\bs_\bh  will
       consult the sequence "unseen" in determining what messages you have
       actually read.  When _\bm_\bs_\bh exits, it reports this information to _\bb_\bb_\bc.
       In  addition,  if  you give the _\bm_\ba_\br_\bk command with no arguments, _\bm_\bs_\bh
       will interpret  it  as  `mark -sequence unseen -delete -nozero all'
       Hence,  to discard all of the messages in the current BBoard you're
       reading, just use the _\bm_\ba_\br_\bk command with no arguments.

       Normally, the "exit" command is identical to the "quit" command  in
       _\bm_\bs_\bh.   When  run  under _\bb_\bb_\bc however, "exit" directs _\bm_\bs_\bh to mark all
       messages as seen and then "quit".  For speedy type-in, this command
       is often abbreviated as just "e".

       When invoked from _\bv_\bm_\bh, another  special  feature  is  enabled:  The
       `topcur' switch directs _\bm_\bs_\bh to have the current message "track" the
       top line of the _\bv_\bm_\bh scan window.  Normally,  _\bm_\bs_\bh  has  the  current
       message  "track" the center of the window (under `-notopcur', which
       is the default).

       _\bm_\bs_\bh supports an output redirection facility.  Commands may be  fol-
       lowed by one of

            > _\bf_\bi_\bl_\be     write output to _\bf_\bi_\bl_\be
            >> _\bf_\bi_\bl_\be    append output to _\bf_\bi_\bl_\be
            | _\bc_\bo_\bm_\bm_\ba_\bn_\bd  pipe output to UNIX _\bc_\bo_\bm_\bm_\ba_\bn_\bd

       If _\bf_\bi_\bl_\be starts with a `~' (tilde), then a _\bc_\bs_\bh-like expansion  takes
       place.  Note that _\bc_\bo_\bm_\bm_\ba_\bn_\bd is interpreted by _\bs_\bh (1).  Also note that
       _\bm_\bs_\bh does NOT support history substitutions, variable substitutions,

  [mh.6]                           MH.6.7                      UCI version









  MSH(1)                            -61-                            MSH(1)


       or alias substitutions.

       When parsing commands to the left of any  redirection  symbol,  _\bm_\bs_\bh
       will honor `\' (back-slash) as the quote next-character symbol, and
       `"' (double-quote)  as  quote-word  delimiters.   All  other  input
       tokens are separated by whitespace (spaces and tabs).

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile
       /usr/local/lib/mh/mtstailor         tailor file


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Msg-Protect:         To set mode when creating a new `file'
       fileproc:            Program to file messages
       showproc:            Program to show messages


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       bbc(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `file' defaults to "./msgbox"
       `-prompt (msh) '
       `-noscan'
       `-notopcur'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None



















\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MSH(1)                            -62-                            MSH(1)


  _\bB_\bu_\bg_\bs
       The argument to the `-prompt' switch must be interpreted as a  sin-
       gle  token by the shell that invokes _\bm_\bs_\bh.  Therefore, one must usu-
       ally place the argument to this switch inside double-quotes.

       There is a strict limit of messages  per  file  in  _\bp_\ba_\bc_\bk_\bf'd  format
       which _\bm_\bs_\bh can handle.  Usually, this limit is 1000 messages.

       Please remember that _\bm_\bs_\bh is not the _\bC_\bS_\bh_\be_\bl_\bl, and that a lot  of  the
       nice facilities provided by the latter are not present in the form-
       er.

       In particular, _\bm_\bs_\bh does not understand back-quoting,  so  the  only
       effective  way  to  use  _\bp_\bi_\bc_\bk  inside  _\bm_\bs_\bh  is  to  always  use the
       `-seq select' switch.  Clever users of _\bM_\bH will put the line

            pick: -seq select -list

       in their .mh_profile file so that _\bp_\bi_\bc_\bk works equally well from both
       the shell and _\bm_\bs_\bh.

       _\bs_\bo_\br_\bt_\bm always uses "-noverbose" and if "-textfield field"  is  used,
       "-limit 0".

       The _\bm_\bs_\bh program inherits most (if not all) of the bugs from the  _\bM_\bH
       commands it implements.

























\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  NEXT(1)                           -63-                           NEXT(1)


  _\bN_\bA_\bM_\bE
       next - show the next message

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       next [+folder] [-header] [-noheader] [-showproc program]
            [-noshowproc] [switches for _\bs_\bh_\bo_\bw_\bp_\br_\bo_\bc] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bN_\be_\bx_\bt performs a _\bs_\bh_\bo_\bw on the  next  message  in  the  specified  (or
       current)  folder.  Like _\bs_\bh_\bo_\bw, it passes any switches on to the pro-
       gram _\bs_\bh_\bo_\bw_\bp_\br_\bo_\bc, which is called to list the message.   This  command
       is  almost  exactly  equivalent to "show next".  Consult the manual
       entry for _\bs_\bh_\bo_\bw (1) for all the details.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Current-Folder:      To find the default current folder
       showproc:            Program to show the message


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       show(1), prev(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to the current folder
       `-header'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       If a folder is specified, it will become the current  folder.   The
       message that is shown (i.e., the next message in sequence) will be-
       come the current message.


  _\bB_\bu_\bg_\bs
       _\bn_\be_\bx_\bt is really a link to the _\bs_\bh_\bo_\bw program.  As  a  result,  if  you
       make  a  link  to  _\bn_\be_\bx_\bt and that link is not called _\bn_\be_\bx_\bt, your link
       will  act  like  _\bs_\bh_\bo_\bw  instead.   To   circumvent   this,   add   a
       profile-entry  for the link to your _\bM_\bH profile and add the argument
       _\bn_\be_\bx_\bt to the entry.





\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  PACKF(1)                          -64-                          PACKF(1)


  _\bN_\bA_\bM_\bE
       packf - compress a folder into a single file

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       packf [+folder] [msgs] [-file name] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bP_\ba_\bc_\bk_\bf takes messages from a folder and  copies  them  to  a  single
       file.  Each message in the file is separated by four CTRL-A's and a
       newline (identical to the way messages are stored in your receiving
       mail drop).  Messages packed can be unpacked using _\bi_\bn_\bc.

       If the _\bn_\ba_\bm_\be given to the `-file name' switch exists, then the  mes-
       sages  specified will be appended to the end of the file, otherwise
       the file will be created and the messages appended.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Current-Folder:      To find the default current folder
       Msg-Protect:         To set mode when creating a new `file'


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       inc(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to the current folder
       `msgs' defaults to all
       `-file ./msgbox'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       If a folder is given, it will become the current folder.  The first
       message packed will become the current message.











\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  PICK(1)                           -65-                           PICK(1)


  _\bN_\bA_\bM_\bE
       pick - select messages by content

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       pick [+folder] [msgs] [-and ...] [-or ...] [-not ...]
            [-lbrace ... -rbrace] [--component pattern] [-after date]
            [-before date] [-datefield field] [-sequence name ...]
            [-public] [-nopublic] [-zero] [-nozero] [-list] [-nolist]
            [-help]

       typically:
            scan `pick -from jones`
            pick -to holloway -sequence select
            show `pick -before friday`

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bP_\bi_\bc_\bk searches messages within a folder for the specified  contents,
       and then identifies those messages.  Two types of search primitives
       are available: pattern matching and date constraint operations.

       A modified _\bg_\br_\be_\bp(1) is used to perform the  matching,  so  the  full
       regular  expression  (see _\be_\bd(1)) facility is available within `pat-
       tern'.  With `-search', `pattern' is used directly,  and  with  the
       others, the grep pattern constructed is:

            "component[ \t]*:.*pattern"

       This means that the pattern specified for a `-search' will be found
       everywhere in the message, including the header and the body, while
       the other pattern matching  requests  are  limited  to  the  single
       specified component.  The expression

            `--component pattern'

       is a shorthand for specifying

            `-search "component[ \t]*:.*pattern" '

       It is used to pick a component which is not one  of  "To:",  "cc:",
       "Date:",     "From:",     or    "Subject:".     An    example    is
       `pick --reply-to pooh'.

       Pattern matching is performed on  a  per-line  basis.   Within  the
       header  of the message, each component is treated as one long line,
       but in the body, each line is separate.  Lower-case letters in  the
       search  pattern  will  match either lower or upper case in the mes-
       sage, while upper case will match only upper case.

       Note that since the `-date' switch is a pattern matching  operation
       (as  described  above), to find messages sent on a certain date the
       pattern string must match the text of  the  "Date:"  field  of  the

  [mh.6]                           MH.6.7                      UCI version









  PICK(1)                           -66-                           PICK(1)


       message.

       Independent of  any  pattern  matching  operations  requested,  the
       switches `-after date' or `-before date' may also be used to intro-
       duce date/time contraints on all of the messages.  By default,  the
       "Date:"  field  is  consulted,  but  if another date yielding field
       (such as "BB-Posted:" or  "Delivery-Date:")  should  be  used,  the
       `-datefield field' switch may be used.

       With `-before' and `-after', _\bp_\bi_\bc_\bk  will  actually  parse  the  date
       fields in each of the messages specified in `msgs' and compare them
       to the date/time specified.  If `-after' is given, then only  those
       messages  whose  "Date:"  field  value is chronologically after the
       date specified will be considered.  The `-before' switch  specifies
       the complimentary action.

       Both the `-after' and `-before' switches take legal 822-style  date
       specifications  as  arguments.   _\bP_\bi_\bc_\bk  will default certain missing
       fields so that the entire date need not be specified.  These fields
       are  (in  order  of defaulting): timezone, time and timezone, date,
       date and timezone.  All defaults are taken from the  current  date,
       time, and timezone.

       In addition to 822-style dates, _\bp_\bi_\bc_\bk will also recognize any of the
       days  of  the week ("sunday", "monday", and so on), and the special
       dates "today", "yesterday" (24 hours ago), and "tomorrow" (24 hours
       from  now).   All  days of the week are judged to refer to a day in
       the past (e.g.,  telling  _\bp_\bi_\bc_\bk  "saturday"  on  a  "tuesday"  means
       "last saturday" not "this saturday").

       Finally, in addition to these  special  specifications,  _\bp_\bi_\bc_\bk  will
       also  honor a specification of the form "-dd", which means "dd days
       ago".

       _\bP_\bi_\bc_\bk supports complex boolean operations on  the  searching  primi-
       tives  with  the  `-and',  `-or', `-not', and `-lbrace ... -rbrace'
       switches.  For example,

            pick -after yesterday -and -lbrace -from freida -or -from fear -rbrace

       identifies messages recently sent by "frieda" or "fear".

       The matching primitives take precedence  over  the  `-not'  switch,
       which in turn takes precedence over `-and' which in turn takes pre-
       cedence over  `-or'.   To  override  the  default  precedence,  the
       `-lbrace'  and `-rbrace' switches are provided, which act just like
       opening and closing parentheses in logical expressions.

       Once the search has been performed, if the `-list' switch is given,
       the  message  numbers  of  the selected messages are written to the
       standard output separated by newlines.  This  is  _\be_\bx_\bt_\br_\be_\bm_\be_\bl_\by  useful
       for quickly generating arguments for other _\bM_\bH programs by using the

  [mh.6]                           MH.6.7                      UCI version









  PICK(1)                           -67-                           PICK(1)


       "backquoting" syntax of the shell.  For example, the command

            scan `pick +todo -after "31 Mar 83 0123 PST"`

       says to _\bs_\bc_\ba_\bn those messages in the indicated folder which meet  the
       appropriate criterion.  Note that since _\bp_\bi_\bc_\bk 's context changes are
       written out prior to _\bs_\bc_\ba_\bn 's invocation,  you  need  not  give  the
       folder argument to _\bs_\bc_\ba_\bn as well.

       Regardless of the operation of the `-list' switch,  the  `-sequence
       name' switch may be given once for each sequence the user wishes to
       define.  For each sequence named, that sequence will be defined  to
       mean exactly those messages selected by _\bp_\bi_\bc_\bk.  For example,

            pick -from frated -seq fred

       defines a new message sequence for the current folder called "fred"
       which contains exactly those messages that were selected.

       Note that whenever _\bp_\bi_\bc_\bk processes  a  `-sequence name'  switch,  it
       sets `-nolist'.

       By default, _\bp_\bi_\bc_\bk will zero the sequence  before  adding  it.   This
       action  can be disabled with the `-nozero' switch, which means that
       the messages selected by _\bp_\bi_\bc_\bk will be added to the sequence, if  it
       already  exists,  and  any messages already a part of that sequence
       will remain so.

       The `-public' and `-nopublic' switches are used by _\bp_\bi_\bc_\bk in the same
       way _\bm_\ba_\br_\bk uses them.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Current-Folder:      To find the default current folder


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       mark(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to the current folder
       `msgs' defaults to all
       `-datefield date'
       `-nopublic' if the folder is read-only, `-public' otherwise
       `-zero'
       `-list' is the default if no `-sequence', `-nolist' otherwise
\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  PICK(1)                           -68-                           PICK(1)


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       If a folder is given, it will become the current folder.


  _\bH_\bi_\bs_\bt_\bo_\br_\by
       In previous versions of _\bM_\bH, the _\bp_\bi_\bc_\bk command would _\bs_\bh_\bo_\bw,  _\bs_\bc_\ba_\bn,  or
       _\br_\be_\bf_\bi_\bl_\be  the  selected  messages.   This was rather "inverted logic"
       from the UNIX point of view, so _\bp_\bi_\bc_\bk  was  changed  to  define  se-
       quences  and  output  those  sequences.  Hence, _\bp_\bi_\bc_\bk can be used to
       generate the arguments for all other _\bM_\bH commands, instead of giving
       _\bp_\bi_\bc_\bk endless switches for invoking those commands itself.

       Also, previous versions of _\bp_\bi_\bc_\bk balked  if  you  didn't  specify  a
       search  string or a date/time constraint.  The current version does
       not, and merely matches the messages you specify.   This  lets  you
       type something like:

            show `pick last:20 -seq fear`

       instead of typing

            mark -add -nozero -seq fear last:20
            show fear

       Finally, timezones used to be ignored when  comparing  dates:  they
       aren't any more.


  _\bB_\bu_\bg_\bs
       The argument to the `-after' and `-before' switches must be  inter-
       preted  as  a  single token by the shell that invokes _\bp_\bi_\bc_\bk.  There-
       fore, one must usually place the argument  to  this  switch  inside
       double-quotes.  Furthermore, any occurance of `-datefield' must oc-
       cur prior to the `-after' or `-before' switch it applies to.

       If _\bp_\bi_\bc_\bk is used in a back-quoted operation, such as

            scan `pick -from jones`

       and _\bp_\bi_\bc_\bk fails (e.g., no messages are from "jones"), then the shell
       will still run the outer command (e.g., "scan").  Since no messages
       were matched, _\bp_\bi_\bc_\bk produced no output, and the  argument  given  to
       the outer command as a result of backquoting _\bp_\bi_\bc_\bk is empty.  In the
       case of _\bM_\bH programs, the outer command now acts as if  the  default
       `msg'  or `msgs' should be used (e.g., "all" in the case of _\bs_\bc_\ba_\bn ).
       To prevent this unexpected behavior, if `-list' was given,  and  if
       its  standard  output  is  not a tty, then _\bp_\bi_\bc_\bk outputs the illegal
       message number "0" when it fails.  This lets the outer command fail
       gracefully as well.


\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  PREV(1)                           -69-                           PREV(1)


  _\bN_\bA_\bM_\bE
       prev - show the previous message

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       prev [+folder] [-header] [-noheader] [-showproc program]
            [-noshowproc] [-switches for _\bs_\bh_\bo_\bw_\bp_\br_\bo_\bc] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bP_\br_\be_\bv performs a _\bs_\bh_\bo_\bw on the previous message in the  specified  (or
       current)  folder.  Like _\bs_\bh_\bo_\bw, it passes any switches on to the pro-
       gram named by _\bs_\bh_\bo_\bw_\bp_\br_\bo_\bc, which is called to list the message.   This
       command  is  almost exactly equivalent to "show prev".  Consult the
       manual entry for _\bs_\bh_\bo_\bw (1) for all the details.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Current-Folder:      To find the default current folder
       showproc:            Program to show the message


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       show(1), next(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to the current folder
       `-header'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       If a folder is specified, it will become the current  folder.   The
       message that is shown (i.e., the previous message in sequence) will
       become the current message.


  _\bB_\bu_\bg_\bs
       _\bp_\br_\be_\bv is really a link to the _\bs_\bh_\bo_\bw program.  As  a  result,  if  you
       make  a  link  to  _\bp_\br_\be_\bv and that link is not called _\bp_\br_\be_\bv, your link
       will  act  like  _\bs_\bh_\bo_\bw  instead.   To   circumvent   this,   add   a
       profile-entry  for the link to your _\bM_\bH profile and add the argument
       _\bp_\br_\be_\bv to the entry.





\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  PROMPTER(1)                       -70-                       PROMPTER(1)


  _\bN_\bA_\bM_\bE
       prompter - prompting editor front-end

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       prompter [-erase chr] [-kill chr] [-prepend] [-noprepend] [-rapid]
            [-norapid] [-doteof] [-nodoteof] file [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       This program is normally not invoked directly by  users  but  takes
       the  place  of  an  editor  and  acts  as  an editor front-end.  It
       operates on an 822-style message draft skeleton specified by  file,
       normally provided by _\bc_\bo_\bm_\bp, _\bd_\bi_\bs_\bt, _\bf_\bo_\br_\bw, or _\br_\be_\bp_\bl.

       _\bP_\br_\bo_\bm_\bp_\bt_\be_\br is an editor which allows rapid composition  of  messages.
       It  is particularly useful to network and low-speed (less than 2400
       baud) users of _\bM_\bH.  It is an _\bM_\bH program in that it can have its own
       profile  entry with switches, but it is not invoked directly by the
       user.  The commands _\bc_\bo_\bm_\bp, _\bd_\bi_\bs_\bt, _\bf_\bo_\br_\bw, and _\br_\be_\bp_\bl invoke  _\bp_\br_\bo_\bm_\bp_\bt_\be_\br  as
       an  editor,  either when invoked with `-editor prompter', or by the
       profile  entry  "Editor: prompter",  or  when  given  the   command
       `edit prompter' at "What now?" level.

       For each empty component _\bp_\br_\bo_\bm_\bp_\bt_\be_\br finds in the draft, the  user  is
       prompted  for a response; A <RETURN> will cause the whole component
       to be left out.  Otherwise, a `\' preceding a  <RETURN>  will  con-
       tinue  the  response  on the next line, allowing for multiline com-
       ponents.  Continuation lines must begin with a space or tab.

       Each non-empty component is copied to the draft  and  displayed  on
       the terminal.

       The start of the message body is denoted by a blank line or a  line
       of dashes.  If the body is non-empty, the prompt, which isn't writ-
       ten to the file, is

           "--------Enter additional text",

       or (if `-prepend' was given)

           "--------Enter initial text".

       Message-body typing is  terminated  with  an  end-of-file  (usually
       CTRL-D).   With  the  `-doteof'  switch,  a period on a line all by
       itself also  signifies  end-of-file.   At  this  point  control  is
       returned  to  the  calling  program,  where the user is asked "What
       now?".  See _\bw_\bh_\ba_\bt_\bn_\bo_\bw for the valid options to this query.

       By using the `-prepend' switch, the user can  add  type-in  to  the
       beginning of the message body and have the rest of the body follow.
       This is useful for the _\bf_\bo_\br_\bw command.
\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  PROMPTER(1)                       -71-                       PROMPTER(1)


       By using the `-rapid' switch, if the draft already contains text in
       the message-body, it is not displayed on the user's terminal.  This
       is useful for low-speed terminals.

       The line editing characters for kill and erase may be specified  by
       the  user via the arguments `-kill chr' and `-erase chr', where chr
       may be a character; or `\nnn', where "nnn" is the octal  value  for
       the character.

       An interrupt (usually CTRL-C) during component  typing  will  abort
       _\bp_\br_\bo_\bm_\bp_\bt_\be_\br  and  the _\bM_\bH command that invoked it.  An interrupt during
       message-body typing is equivalent to CTRL-D,  for  historical  rea-
       sons.  This means that _\bp_\br_\bo_\bm_\bp_\bt_\be_\br should finish up and exit.

       The first non-flag argument to _\bp_\br_\bo_\bm_\bp_\bt_\be_\br is taken as the name of the
       draft file, and subsequent non-flag arguments are ignored.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile
       /tmp/prompter*                      Temporary copy of message


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       prompter-next:       To name the editor to be  used  on  exit  from
       _\bp_\br_\bo_\bm_\bp_\bt_\be_\br
       Msg-Protect:         To set mode when creating a new draft


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       comp(1), dist(1), forw(1), repl(1), whatnow(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `-prepend'
       `-norapid'
       `-nodoteof'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None

  _\bH_\be_\bl_\bp_\bf_\bu_\bl _\bH_\bi_\bn_\bt_\bs

       The  `-rapid'  option  is  particularly  useful  with   _\bf_\bo_\br_\bw,   and
       `-noprepend' is useful with _\bc_\bo_\bm_\bp -_\bu_\bs_\be.

       The user may wish to link _\bp_\br_\bo_\bm_\bp_\bt_\be_\br under several names (e.g.,  "ra-
       pid")  and  give  appropriate switches in the profile entries under
       these names (e.g., "rapid:  -rapid").   This  facilitates  invoking
       prompter  differently for different _\bM_\bH commands (e.g., "forw: -edi-
       tor rapid").
\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  PROMPTER(1)                       -72-                       PROMPTER(1)


  _\bB_\bu_\bg_\bs
       _\bP_\br_\bo_\bm_\bp_\bt_\be_\br uses _\bs_\bt_\bd_\bi_\bo (3), so it will lose if  you  edit  files  with
       nulls in them.
















































\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  RCVSTORE(1)                       -73-                       RCVSTORE(1)


  _\bN_\bA_\bM_\bE
       rcvstore - incorporate new mail asynchronously

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       /usr/local/lib/mh/rcvstore [+folder] [-create] [-nocreate]
            [-sequence name ...] [-public] [-nopublic] [-zero] [-nozero]
            [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bR_\bc_\bv_\bs_\bt_\bo_\br_\be incorporates a message from the standard input into an  _\bM_\bH
       folder.   If `+folder' isn't specified, the folder named "inbox" in
       the user's _\bM_\bH directory will be  used  instead.   The  new  message
       being  incorporated  is  assigned  the  next  highest number in the
       folder.  If the specified (or default) folder doesn't  exist,  then
       it  will be created if the `-create' option is specified, otherwise
       _\br_\bc_\bv_\bs_\bt_\bo_\br_\be will exit.

       If the user's profile contains a "Msg-Protect: nnn" entry, it  will
       be  used as the protection on the newly created messages, otherwise
       the _\bM_\bH default of 0644 will be used.  During all operations on mes-
       sages,  this  initially  assigned  protection will be preserved for
       each message, so _\bc_\bh_\bm_\bo_\bd(1) may be used to set  a  protection  on  an
       individual   message,   and   its   protection  will  be  preserved
       thereafter.

       _\bR_\bc_\bv_\bs_\bt_\bo_\br_\be will incorporate anything except zero length messages into
       the user's MH folder.

       If the profile entry "Unseen-Sequence" is  present  and  non-empty,
       then  _\br_\bc_\bv_\bs_\bt_\bo_\br_\be  will  add  the  newly  incorporated message to each
       sequence named by the  profile  entry.   This  is  similar  to  the
       "Previous-Sequence"  profile  entry  supported  by  all _\bM_\bH commands
       which take `msgs' or `msg' arguments.  Note that _\br_\bc_\bv_\bs_\bt_\bo_\br_\be will  not
       zero each sequence prior to adding messages.

       Furthermore, the incoming messages may  be  added  to  user-defined
       sequences  as  they  arrive  by  appropriate use of the `-sequence'
       option.  As with _\bp_\bi_\bc_\bk, use of the `-zero'  and  `-nozero'  switches
       can  also  be used to zero old sequences or not.  Similarly, use of
       the `-public' and `-nopublic switches may be used  to  force  addi-
       tions to public and private sequences.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile






\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  RCVSTORE(1)                       -74-                       RCVSTORE(1)


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Folder-Protect:      To set mode when creating a new folder
       Msg-Protect:         To set mode when creating a new message
       Unseen-Sequence:     To name sequences denoting unseen messages


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       inc(1), pick(1), mh-mail(5)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to "inbox"
       `-create'
       `-nopublic' if the folder is read-only, `-public' otherwise
       `-nozero'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       No context changes will be attempted, with  the  exception  of  se-
       quence manipulation.






























\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  REFILE(1)                         -75-                         REFILE(1)


  _\bN_\bA_\bM_\bE
       refile - file message in other folders

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       refile [msgs] [-draft] [-link] [-nolink] [-preserve] [-nopreserve]
            [-src +folder] [-file file] [-rmmproc program] [-normmproc]
            +folder ...  [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bR_\be_\bf_\bi_\bl_\be moves (_\bm_\bv (1)) or links  (_\bl_\bn (1))  messages  from  a  source
       folder  into  one  or  more destination folders.  If you think of a
       message as a sheet of paper, this operation is  not  unlike  filing
       the  sheet  of  paper  (or copies) in file cabinet folders.  When a
       message is filed, it is linked into the  destination  folder(s)  if
       possible,  and  is  copied  otherwise.   As long as the destination
       folders are all on the same file  system,  multiple  filing  causes
       little  storage  overhead.   This  facility  provides a good way to
       cross-file or multiply-index messages.  For example, if  a  message
       is received from Jones about the ARPA Map Project, the command

            refile cur +jones +Map

       would allow the message to be found in either of  the  two  folders
       `jones' or `Map'.

       The option `-file file' directs _\br_\be_\bf_\bi_\bl_\be to use the specified file 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 _\bM_\bH message.  It should NOT be in mail drop for-
       mat (to convert a file in mail drop format to a folder of  _\bM_\bH  mes-
       sages, see _\bi_\bn_\bc (1)).

       If a destination folder doesn't exist, _\br_\be_\bf_\bi_\bl_\be will ask if you  want
       to create it.  A negative response will abort the file operation.

       The option `-link' preserves the source folder copy of the  message
       (i.e.,  it  does  a  _\bl_\bn(1) rather than a _\bm_\bv(1)), whereas, `-nolink'
       deletes the filed messages from the source folder.  Normally,  when
       a  message  is filed, it is assigned the next highest number avail-
       able in each of the destination folders.  Use  of  the  `-preserve'
       switch  will override this message renaming, but name conflicts may
       occur, so use this switch cautiously.

       If `-link' is not specified (or `-nolink' is specified), the  filed
       messages  will  be removed from the source folder, by renaming them
       with a site-dependent prefix (usually a comma).




\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  REFILE(1)                         -76-                         REFILE(1)


       If the user has a profile component such as

               rmmproc:        /bin/rm

       then _\br_\be_\bf_\bi_\bl_\be will instead call the named program to delete the  mes-
       sage files.  The user may specify `-rmmproc program' on the command
       line to override  this  profile  specification.   The  `-normmproc'
       option  forces  the message files to be deleted by renaming them as
       described above.

       The `-draft' switch tells _\br_\be_\bf_\bi_\bl_\be to file the <mh-dir>/draft.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Current-Folder:      To find the default current folder
       Folder-Protect:      To set mode when creating a new folder
       rmmproc:             Program to delete the message


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       folder(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `-src +folder' defaults to the current folder
       `msgs' defaults to cur
       `-nolink'
       `-nopreserve'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       If `-src +folder' is given, it will become the current folder.   If
       neither  `-link' nor `all' is specified, the current message in the
       source folder will be set to the last message specified; otherwise,
       the current message won't be changed.

       If the Previous-Sequence profile entry is set, in addition  to  de-
       fining the named sequences from the source folder, _\br_\be_\bf_\bi_\bl_\be will also
       define  those  sequences  for   the   destination   folders.    See
       _\bm_\bh-_\bp_\br_\bo_\bf_\bi_\bl_\be (1) for information concerning the previous sequence.


  _\bB_\bu_\bg_\bs
       Since _\br_\be_\bf_\bi_\bl_\be uses your _\br_\bm_\bm_\bp_\br_\bo_\bc to delete the message,  the  _\br_\bm_\bm_\bp_\br_\bo_\bc
       must  NOT  call _\br_\be_\bf_\bi_\bl_\be without specifying `-normmproc', or you will
       create an infinte loop.

\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  REPL(1)                           -77-                           REPL(1)


  _\bN_\bA_\bM_\bE
       repl - reply to a message

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       repl [+folder] [msg] [-annotate] [-noannotate] [-cc all/to/cc/me]
            [-nocc all/to/cc/me] [-draftfolder +folder]
            [-draftmessage msg] [-nodraftfolder] [-editor editor]
            [-noedit] [-fcc +folder] [-filter filterfile] [-form formfile]
            [-inplace] [-noinplace] [-query] [-noquery] [-width columns]
            [-whatnowproc program] [-nowhatnowproc] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bR_\be_\bp_\bl aids a user in producing a reply to an existing message.  _\bR_\be_\bp_\bl
       uses  a  reply  template to guide its actions when constructing the
       message draft of the reply.  In its simplest form  (with  no  argu-
       ments),  it  will  set  up  a message-form skeleton in reply to the
       current message in the  current  folder,  and  invoke  the  whatnow
       shell.   The  default  reply template will direct _\br_\be_\bp_\bl to construct
       the composed message as follows:

            To: <Reply-To> or <From>
            cc: <cc>, <To>, and yourself
            Subject: Re: <Subject>
            In-reply-to: Your message of <Date>.
                         <Message-Id>

       where field names enclosed in angle  brackets  (< >)  indicate  the
       contents  of the named field from the message to which the reply is
       being made.  A  reply  template  is  simply  a  format  file.   See
       _\bm_\bh-_\bf_\bo_\br_\bm_\ba_\bt (5) for the details.

       The `-cc type' switch takes an argument which  specifies  who  gets
       placed  on  the "cc:" list of the reply.  The `-query' switch modi-
       fies the action of `-cc type' switch by interactively asking you if
       each  address  that normally would be placed in the "To:" and "cc:"
       list  should  actually  be  sent  a  copy.   (This  is  useful  for
       special-purpose  replies.)  Note that the position of the `-cc' and
       `-nocc' switches, like all other switches which take a positive and
       negative form, is important.

       Lines beginning with the fields "To:", "cc:", and  "Bcc:"  will  be
       standardized  and  have  duplicate addresses removed.  In addition,
       the `-width columns' switch will guide _\br_\be_\bp_\bl's formatting  of  these
       fields.

       If the file named "replcomps" exists in the user's MH directory, it
       will be used instead of the default form.  In either case, the file
       specified by `-form formfile' will be used if given.

       If the draft already exists, _\br_\be_\bp_\bl will ask you as to  the  disposi-
       tion  of  the  draft.  A reply of quit will abort _\br_\be_\bp_\bl, leaving the

  [mh.6]                           MH.6.7                      UCI version









  REPL(1)                           -78-                           REPL(1)


       draft intact; replace will replace the existing draft with a  blank
       skeleton; and list will display the draft.

       See _\bc_\bo_\bm_\bp (1) for a  description  of  the  `-editor'  and  `-noedit'
       switches.  Note that while in the editor, the message being replied
       to is available through a link  named  "@"  (assuming  the  default
       _\bw_\bh_\ba_\bt_\bn_\bo_\bw_\bp_\br_\bo_\bc ).   In addition, the actual pathname of the message is
       stored in the envariable $editalt, and the pathname of  the  folder
       containing the message is stored in the envariable $mhfolder.

       Although _\br_\be_\bp_\bl uses the `-form formfile' switch to direct it how  to
       construct  the  beginning  of  the  draft, the `-filter filterfile'
       switch directs _\br_\be_\bp_\bl as to how the message being  replied-to  should
       be  formatted in the body of the draft.  If `-filter' is not speci-
       fied, then the message being replied-to is not included in the body
       of  the draft.  If `-filter filterfile' is specified, then the mes-
       sage being replied-to is filtered  (re-formatted)  prior  to  being
       output  to  the body of the draft.  The filter file for _\br_\be_\bp_\bl should
       be a standard form file for _\bm_\bh_\bl, as _\br_\be_\bp_\bl will invoke _\bm_\bh_\bl to  format
       the  message  being replied-to.  There is no default message filter
       (`-filter' must be followed by a file name).  A filter file that is
       commonly used is:

            :
            body:nocomponent,compwidth=9,offset=9

       which says to output a blank line and then the body of the  message
       being replied-to, indented by one tab-stop.  Another format popular
       on USENET is:

            message-id:nocomponent,formatfield=\
            "In message %{text}you write:"
            body:component=">",overflowtext=">",overflowoffset=0

       Which cites the Message-ID of the  message  being  replied-to,  and
       then outputs each line of the body prefaced with the ">" character.

       If the `-annotate' switch is given, the  message  being  replied-to
       will be annotated with the lines

            Replied: date
            Replied: addrs

       where the address list contains one line for each  addressee.   The
       annotation  will  be done only if the message is sent directly from
       _\br_\be_\bp_\bl.   If  the  message  is  not  sent  immediately   from   _\br_\be_\bp_\bl,
       "comp -use"  may  be  used to re-edit and send the constructed mes-
       sage, but the annotations won't take place.  The `-inplace'  switch
       causes annotation to be done in place in order to preserve links to
       the annotated message.

       The `-fcc +folder' switch can be used to  automatically  specify  a

  [mh.6]                           MH.6.7                      UCI version









  REPL(1)                           -79-                           REPL(1)


       folder  to  receive Fcc:s.  More than one folder, each preceeded by
       `-fcc' can be named.

       In addition to the standard _\bm_\bh-_\bf_\bo_\br_\bm_\ba_\bt (5) escapes, _\br_\be_\bp_\bl also recog-
       nizes the following additional _\bc_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt escape:

       _\bE_\bs_\bc_\ba_\bp_\be  _\bR_\be_\bt_\bu_\br_\bn_\bs  _\bD_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn
       _\bf_\bc_\bc     string   Any folders specified with `-fcc folder'

       To avoid reiteration, _\br_\be_\bp_\bl strips any leading `Re: '  strings  from
       the _\bs_\bu_\bb_\bj_\be_\bc_\bt component.

       The `-draftfolder +folder' and `-draftmessage msg' switches  invoke
       the _\bM_\bH draft folder facility.  This is an advanced (and highly use-
       ful) feature.  Consult the Advanced  Features  section  of  the  _\bM_\bH
       manual for more information.

       Upon exiting from the editor, _\br_\be_\bp_\bl will invoke the _\bw_\bh_\ba_\bt_\bn_\bo_\bw program.
       See _\bw_\bh_\ba_\bt_\bn_\bo_\bw (1) for a discussion of available options.  The invoca-
       tion of this program can be inhibited by using the `-nowhatnowproc'
       switch.   (In truth of fact, it is the _\bw_\bh_\ba_\bt_\bn_\bo_\bw program which starts
       the initial edit.  Hence, `-nowhatnowproc' will  prevent  any  edit
       from occurring.)

  _\bF_\bi_\bl_\be_\bs
       /usr/local/lib/mh/replcomps         The reply template
       or <mh-dir>/replcomps               Rather than the standard template
       $HOME/.mh_profile                   The user profile
       <mh-dir>/draft                      The draft file


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Alternate-Mailboxes: To determine the user's mailboxes
       Current-Folder:      To find the default current folder
       Draft-Folder:        To find the default draft-folder
       Editor:              To override the default editor
       Msg-Protect:         To  set  mode  when  creating  a  new  message
       (draft)
       fileproc:            Program to refile the message
       mhlproc:             Program to filter message being replied-to
       whatnowproc:         Program to ask the "What now?" questions


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       comp(1), dist(1), forw(1), send(1), whatnow(1), mh-format(5)





\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  REPL(1)                           -80-                           REPL(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to the current folder
       `msg' defaults to cur
       `-nocc all' at ATHENA sites, `-cc all' otherwise
       `-noannotate'
       `-nodraftfolder'
       `-noinplace'
       `-noquery'
       `-width 72'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       If a folder is given, it will become the current folder.  The  mes-
       sage replied-to will become the current message.


  _\bH_\bi_\bs_\bt_\bo_\br_\by
       Prior to using the format string  mechanism,  `-noformat'  used  to
       cause  address  headers to be output as-is.  Now all address fields
       are formatted using Internet standard guidelines.


  _\bB_\bu_\bg_\bs
       If any addresses occur in the reply template, addresses in the tem-
       plate that do not contain hosts are defaulted incorrectly.  Instead
       of using the localhost for the  default,  _\br_\be_\bp_\bl  uses  the  sender's
       host.   Moral of the story: if you're going to include addresses in
       a reply template, include the host portion of the address.

       The `-width columns' switch is only  used  to  do  address-folding;
       other headers are not line-wrapped.

       If _\bw_\bh_\ba_\bt_\bn_\bo_\bw_\bp_\br_\bo_\bc is _\bw_\bh_\ba_\bt_\bn_\bo_\bw, then _\br_\be_\bp_\bl uses a  built-in  _\bw_\bh_\ba_\bt_\bn_\bo_\bw,  it
       does  not  actually  run the _\bw_\bh_\ba_\bt_\bn_\bo_\bw program.  Hence, if you define
       your own _\bw_\bh_\ba_\bt_\bn_\bo_\bw_\bp_\br_\bo_\bc, don't call it _\bw_\bh_\ba_\bt_\bn_\bo_\bw since  _\br_\be_\bp_\bl  won't  run
       it.

       If your current working directory is not writable, the  link  named
       "@" is not available.












\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  RMF(1)                            -81-                            RMF(1)


  _\bN_\bA_\bM_\bE
       rmf - remove folder

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       rmf [+folder] [-interactive] [-nointeractive] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bR_\bm_\bf removes all of the messages (files) within  the  specified  (or
       default)  folder,  and  then removes the folder (directory) itself.
       If there are any files within the folder which are not  a  part  of
       _\bM_\bH,  they  will  _\bn_\bo_\bt be removed, and an error will be produced.  If
       the folder is given explicitly or the  `-nointeractive'  option  is
       given,  then the folder will be removed without confirmation.  Oth-
       erwise, the user will be asked for confirmation.  If _\br_\bm_\bf can't find
       the  current  folder,  for  some  reason,  the folder to be removed
       defaults to `+inbox' with confirmation.

       _\bR_\bm_\bf irreversibly deletes messages that don't have other  links,  so
       use it with caution.

       If the folder being removed is a subfolder, the parent folder  will
       become  the new current folder, and _\br_\bm_\bf will produce a message tel-
       ling the user this has happened.  This provides an  easy  mechanism
       for selecting a set of messages, operating on the list, then remov-
       ing the list and returning to the current  folder  from  which  the
       list was extracted.

       _\bR_\bm_\bf of a read-only folder will delete the private sequence and  cur
       information  (i.e.,  "atr-_\bs_\be_\bq-_\bf_\bo_\bl_\bd_\be_\br"  entries)  from  the  profile
       without affecting the folder itself.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Current-Folder:      To find the default current folder


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       rmm(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to the current folder, usually with confirmation
       `-interactive' if +folder' not given, `-nointeractive' otherwise



\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  RMF(1)                            -82-                            RMF(1)


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       _\bR_\bm_\bf will set the current folder to the parent folder if a subfolder
       is  removed; or if the current folder is removed, it will make "in-
       box" current.  Otherwise, it doesn't change the current  folder  or
       message.


  _\bB_\bu_\bg_\bs
       Although intuitively one would suspect that _\br_\bm_\bf works  recursively,
       it  does  not.   Hence if you have a sub-folder within a folder, in
       order to _\br_\bm_\bf the parent, you must first _\br_\bm_\bf each of the children.








































\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  RMM(1)                            -83-                            RMM(1)


  _\bN_\bA_\bM_\bE
       rmm - remove messages

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       rmm [+folder] [msgs] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bR_\bm_\bm removes the specified messages by renaming  the  message  files
       with preceding commas.  Many sites consider files that start with a
       comma to be a temporary backup, and arrange for _\bc_\br_\bo_\bn (8) to  remove
       such files once a day.

       If the user has a profile component such as

               rmmproc:        /bin/rm

       then instead of simply renaming the message file, _\br_\bm_\bm will call the
       named program to delete the file.  Note that at most installations,
       _\bc_\br_\bo_\bn (8) is told to remove files that begin with  a  comma  once  a
       night.

       Some users of csh prefer the following:

               alias rmm 'refile +d'

       where folder +d is a folder for deleted messages, and

               alias mexp 'rm `mhpath +d all`'

       is used to "expunge" deleted messages.

       The current message is not changed by _\br_\bm_\bm, so a _\bn_\be_\bx_\bt  will  advance
       to the next message in the folder as expected.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Current-Folder:      To find the default current folder
       rmmproc:             Program to delete the message


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       rmf(1)




\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  RMM(1)                            -84-                            RMM(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to the current folder
       `msgs' defaults to cur


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       If a folder is given, it will become the current folder.

  _\bH_\be_\bl_\bp_\bf_\bu_\bl _\bH_\bi_\bn_\bt_\bs

       If you're not a csh user, and you  have  an  _\br_\bm_\bm_\bp_\br_\bo_\bc  script  which
       _\br_\be_\bf_\bi_\bl_\bes messages, be sure you use something like:

            mv `mhpath msgs` `mhpath new +folder`

       Other work-arounds are possible, such as:

            cd `mhpath +`
            MH=/dev/null MHCONTEXT=/dev/null refile $* +folder


  _\bB_\bu_\bg_\bs
       Since _\br_\be_\bf_\bi_\bl_\be uses your _\br_\bm_\bm_\bp_\br_\bo_\bc to delete the message,  the  _\br_\bm_\bm_\bp_\br_\bo_\bc
       must  NOT  call _\br_\be_\bf_\bi_\bl_\be without specifying `-normmproc', or you will
       create an infinte loop.


























\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  SCAN(1)                           -85-                           SCAN(1)


  _\bN_\bA_\bM_\bE
       scan - produce a one line per message scan listing

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       scan [+folder] [msgs] [-clear] [-noclear] [-form formatfile]
            [-format string] [-header] [-noheader] [-width columns]
            [-reverse] [-noreverse] [-file filename] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bS_\bc_\ba_\bn produces a one-line-per-message listing of the specified  mes-
       sages.   Each  _\bs_\bc_\ba_\bn  line  contains  the message number (name), the
       date, the "From:" field, the "Subject" field, and, if room  allows,
       some of the body of the message.  For example:

            15+  7/ 5  Dcrocker  nned  <<Last week I asked some of
            16 - 7/ 5  dcrocker  message id format  <<I recommend
            18   7/ 6  Obrien    Re: Exit status from mkdir
            19   7/ 7  Obrien    "scan" listing format in MH

       The `+' on message 15 indicates that it  is  the  current  message.
       The  `-'  on  message  16 indicates that it has been replied to, as
       indicated by a "Replied:"  component  produced  by  an  `-annotate'
       switch to the _\br_\be_\bp_\bl command.

       If there is sufficient room left on the _\bs_\bc_\ba_\bn line  after  the  sub-
       ject,  the line will be filled with text from the body, preceded by
       <<, and terminated by >> if the body is sufficiently  short.   _\bS_\bc_\ba_\bn
       actually  reads  each  of the specified messages and parses them to
       extract the desired fields.  During parsing, appropriate error mes-
       sages  will  be  produced  if there are format errors in any of the
       messages.

       The `-header' switch produces a header line prior to the _\bs_\bc_\ba_\bn list-
       ing.   Currently,  the  name of the folder and the current date and
       time are output (see the HISTORY section for more information).

       If the `-clear' switch is used and _\bs_\bc_\ba_\bn'_\bs output is directed  to  a
       terminal, then _\bs_\bc_\ba_\bn will consult the $TERM and $TERMCAP envariables
       to determine your terminal type in order to find out how  to  clear
       the  screen  prior  to exiting.  If the `-clear' switch is used and
       _\bs_\bc_\ba_\bn'_\bs output is not directed to a terminal  (e.g.,  a  pipe  or  a
       file), then _\bs_\bc_\ba_\bn will send a formfeed prior to exiting.

       For example, the command:

            (scan -clear -header; show all -show pr -f) | lpr

       produces a scan listing  of  the  current  folder,  followed  by  a
       formfeed,  followed  by  a formatted listing of all messages in the
       folder, one per page.  Omitting `-show pr -f' will cause  the  mes-
       sages  to  be  concatenated, separated by a one-line header and two

  [mh.6]                           MH.6.7                      UCI version









  SCAN(1)                           -86-                           SCAN(1)


       blank lines.

       If _\bs_\bc_\ba_\bn encounters a message without a "Date:" field,  rather  than
       leaving  that  portion  of  the  scan  listing  blank,  the date is
       filled-in with the last write date of the message,  and  post-fixed
       with  a  `*'.   This  is  particularly  handy  for scanning a _\bd_\br_\ba_\bf_\bt
       _\bf_\bo_\bl_\bd_\be_\br, as message drafts usually aren't allowed to have  dates  in
       them.

       To override the output format used by _\bs_\bc_\ba_\bn, the `-format string' or
       `-format file'  switches  are used.  This permits individual fields
       of the scan listing to be extracted with ease.  The string is  sim-
       ply  a  format  string  and  the file is simply a format file.  See
       _\bm_\bh-_\bf_\bo_\br_\bm_\ba_\bt (5) for the details.

       In addition to the standard _\bm_\bh-_\bf_\bo_\br_\bm_\ba_\bt (5) escapes, _\bs_\bc_\ba_\bn also recog-
       nizes the following additional _\bc_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt escape:

       _\bE_\bs_\bc_\ba_\bp_\be  _\bR_\be_\bt_\bu_\br_\bn_\bs  _\bD_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn
       body    string   the (compressed) first part of the body

       Also, if no date header was present in the  message,  the  _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn
       escapes  which operate on {_\bd_\ba_\bt_\be} will return values for the date of
       last modification of the message file itself.


       _\bs_\bc_\ba_\bn will update the _\bM_\bH context prior to starting the  listing,  so
       interrupting  a  long  _\bs_\bc_\ba_\bn  listing preserves the new context.  _\bM_\bH
       purists hate this idea.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Alternate-Mailboxes: To determine the user's mailboxes
       Current-Folder:      To find the default current folder


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       inc(1), pick(1), show(1), mh-format(5)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to the folder current
       `msgs' defaults to all
       `-format' defaulted as described above
       `-noheader'
       `-width' defaulted to the width of the terminal

\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  SCAN(1)                           -87-                           SCAN(1)


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       If a folder is given, it will become the current folder.


  _\bH_\bi_\bs_\bt_\bo_\br_\by
       Prior to using the format string mechanism, `-header' used to  gen-
       erate a heading saying what each column in the listing was.  Format
       strings prevent this from happening.


  _\bB_\bu_\bg_\bs
       The argument to the `-format' switch must be interpreted as a  sin-
       gle token by the shell that invokes _\bs_\bc_\ba_\bn.  Therefore, one must usu-
       ally place the argument to this switch inside double-quotes.
       The value of each _\bc_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt escape is set by _\bs_\bc_\ba_\bn to  the  contents
       of  the first message header _\bs_\bc_\ba_\bn encounters with the corresponding
       component name; any following headers with the same component  name
       are ignored.

       The switch `-reverse', makes _\bs_\bc_\ba_\bn list the messages in reverse ord-
       er; this should be considered a bug.

       The `-file filename' switch allows the user to obtain a _\bs_\bc_\ba_\bn  list-
       ing of a maildrop file as produced by _\bp_\ba_\bc_\bk_\bf.  This listing includes
       every message in the file.  The user should use _\bm_\bs_\bh for more selec-
       tive  processing  of the file.  `-reverse' is ignored with this op-
       tion.
























\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  SEND(1)                           -88-                           SEND(1)


  _\bN_\bA_\bM_\bE
       send - send a message

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       send [-alias aliasfile] [-draft] [-draftfolder +folder]
            [-draftmessage msg] [-nodraftfolder] [-filter filterfile]
            [-nofilter] [-format] [-noformat] [-forward] [-noforward]
            [-msgid] [-nomsgid] [-push] [-nopush] [-verbose] [-noverbose]
            [-watch] [-nowatch] [-width columns] [file ...] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bS_\be_\bn_\bd will cause each of the specified files to  be  delivered  (via
       _\bp_\bo_\bs_\bt (8))  to each of the destinations in the "To:", "cc:", "Bcc:",
       and "Fcc:" fields of the message.  If  _\bs_\be_\bn_\bd  is  re-distributing  a
       message,  as invoked from _\bd_\bi_\bs_\bt, then the corresponding "Resent-xxx"
       fields are examined instead.

       If `-push' is specified, _\bs_\be_\bn_\bd will detach itself  from  the  user's
       terminal and perform its actions in the background.  If _\bp_\bu_\bs_\bh 'd and
       the draft can't be sent, then the `-forward' switch says that draft
       should be forwarded with the failure notice sent to the user.  This
       differs from putting _\bs_\be_\bn_\bd in the background because the  output  is
       trapped and analyzed by _\bM_\bH.

       If `-verbose' is specified, _\bs_\be_\bn_\bd  will  indicate  the  interactions
       occurring  with the transport system, prior to actual delivery.  If
       `-watch' is specified _\bs_\be_\bn_\bd will monitor the delivery of  local  and
       network  mail.   Hence, by specifying both switches, a large detail
       of information can be gathered about each  step  of  the  message's
       entry into the transport system.

       The `-draftfolder +folder' and `-draftmessage msg' switches  invoke
       the _\bM_\bH draft folder facility.  This is an advanced (and highly use-
       ful) feature.  Consult the Advanced  Features  section  of  the  _\bM_\bH
       manual for more information.

       _\bS_\be_\bn_\bd with no _\bf_\bi_\bl_\be argument will query  whether  the  draft  is  the
       intended  file, whereas `-draft' will suppress this question.  Once
       the transport system has successfully accepted custody of the  mes-
       sage,  the  file will be renamed with a leading comma, which allows
       it to be retrieved until the next draft message is sent.  If  there
       are errors in the formatting of the message, _\bs_\be_\bn_\bd will abort with a
       (hopefully) helpful error message.

       If a "Bcc:" field is encountered, its addresses will  be  used  for
       delivery,  and  the  "Bcc:"  field will be removed from the message
       sent to sighted recipients.  The blind recipients will  receive  an
       entirely  new  message  with a minimal set of headers.  Included in
       the body of the message will be a copy of the message sent  to  the
       sighted  recipients.   If  `-filter filterfile'  is specified, then
       this copy is filtered (re-formatted) prior to  being  sent  to  the

  [mh.6]                           MH.6.7                      UCI version









  SEND(1)                           -89-                           SEND(1)


       blind recipients.

       Prior to sending the message, the  fields  "From: user@local",  and
       "Date: now" will be appended to the headers in the message.  If the
       envariable $SIGNATURE is set, then its value is used as  your  per-
       sonal  name  when constructing the "From:" line of the message.  If
       this envariable is not set, then  _\bs_\be_\bn_\bd  will  consult  the  profile
       entry "Signature" for this information.  On hosts where _\bM_\bH was con-
       figured with the UCI option, if $SIGNATURE is not set and the "Sig-
       nature"   profile   entry   is   not   present,   then   the   file
       $HOME/.signature is consulted.  If `-msgid' is  specified,  then  a
       "Message-ID:" field will also be added to the message.

       If _\bs_\be_\bn_\bd is re-distributing a message (when invoked by _\bd_\bi_\bs_\bt ),  then
       "Resent-"  will  be  prepended  to  each  of these fields: "From:",
       "Date:", and "Message-ID:".  If  the  message  already  contains  a
       "From:"  field,  then a "Sender: user@local" field will be added as
       well.  (An already existing "Sender:" field is an error!)

       By using the `-format' switch, each of the entries in the "To:" and
       "cc:" fields will be replaced with "standard" format entries.  This
       standard format is designed to be usable  by  all  of  the  message
       handlers  on  the various systems around the Internet.  If `-nofor-
       mat' is given, then headers are output exactly as  they  appear  in
       the message draft.

       If an "Fcc: folder" is encountered, the message will be  copied  to
       the  specified folder for the sender in the format in which it will
       appear to any non-Bcc receivers of the message.  That is,  it  will
       have the appended fields and field reformatting.  The "Fcc:" fields
       will be removed from all outgoing copies of the message.

       By using the `-width columns' switch, the user can direct  _\bs_\be_\bn_\bd  as
       to how long it should make header lines containing addresses.

       The file specified by the profile entry "Aliasfile:" and any  addi-
       tional  alias  files given by the `-alias aliasfile' switch will be
       read (more than one file,  each   preceeded  by  `-alias',  can  be
       named).  See _\bm_\bh-_\ba_\bl_\bi_\ba_\bs (5) for more information.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Draft-Folder:        To find the default draft-folder
       Aliasfile:           For a default alias file
       Signature:           To determine the user's mail signature
       mailproc:            Program to post failure notices
       postproc:            Program to post the message
\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  SEND(1)                           -90-                           SEND(1)


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       comp(1), dist(1), forw(1), repl(1), mh-alias(5), post(8)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `file' defaults to <mh-dir>/draft
       `-alias /usr/local/lib/mh/MailAliases'
       `-nodraftfolder'
       `-nofilter'
       `-format'
       `-forward'
       `-nomsgid'
       `-nopush'
       `-noverbose'
       `-nowatch'
       `-width 72'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None































\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  SHOW(1)                           -91-                           SHOW(1)


  _\bN_\bA_\bM_\bE
       show - show (list) messages

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       show [+folder] [msgs] [-draft] [-header] [-noheader]
            [-showproc program] [-noshowproc] [switches for _\bs_\bh_\bo_\bw_\bp_\br_\bo_\bc]
            [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bS_\bh_\bo_\bw lists each of the specified messages to  the  standard  output
       (typically,  the  terminal).   Typically,  the  messages are listed
       exactly as they are, with no reformatting.  A program named by  the
       _\bs_\bh_\bo_\bw_\bp_\br_\bo_\bc  profile  component  is invoked to do the listing, and any
       switches not recognized by _\bs_\bh_\bo_\bw are passed along to  that  program.
       The  default program is known as _\bm_\bo_\br_\be (1).  To override the default
       and the _\bs_\bh_\bo_\bw_\bp_\br_\bo_\bc profile  component,  use  the  `-showproc program'
       switch.   For  example, `-show pr' will cause the _\bp_\br (1) program to
       list the messages.  The _\bM_\bH command _\bm_\bh_\bl can be used as a _\bs_\bh_\bo_\bw_\bp_\br_\bo_\bc to
       show  messages in a more uniform format.  Normally, this program is
       specified as the _\bs_\bh_\bo_\bw_\bp_\br_\bo_\bc is the user's .mh_profile.   See  _\bm_\bh_\bl (1)
       for  the  details.   If  the  `-noshowproc'  option  is  specified,
       `/bin/cat' is used instead of _\bs_\bh_\bo_\bw_\bp_\br_\bo_\bc.

       The `-header' switch tells _\bs_\bh_\bo_\bw to display a  one-line  description
       of  the  message being shown.  This description includes the folder
       and the message number.

       If no `msgs' are specified, the current message is used.   If  more
       than  one  message  is  specified,  _\bm_\bo_\br_\be will prompt for a <RETURN>
       prior to listing each message.  _\bm_\bo_\br_\be will list each message, a page
       at  a  time.   When  the end of page is reached, _\bm_\bo_\br_\be will ring the
       bell and wait for a <SPACE> or <RETURN>.  If a <RETURN> is entered,
       _\bm_\bo_\br_\be  will print the next line, whereas <SPACE> will print the next
       screenful.  To exit _\bm_\bo_\br_\be, type "q".

       If the standard output is not a terminal, no queries are made,  and
       each file is listed with a one-line header and two lines of separa-
       tion.

       "show -draft" will list the file <mh-dir>/draft if it exists.

       If the profile entry "Unseen-Sequence" is  present  and  non-empty,
       then _\bs_\bh_\bo_\bw will remove each of the messages shown from each sequence
       named  by  the   profile   entry.    This   is   similar   to   the
       "Previous-Sequence"  profile  entry  supported  by  all _\bM_\bH commands
       which take `msgs' or `msg' arguments.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile

\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  SHOW(1)                           -92-                           SHOW(1)


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Current-Folder:      To find the default current folder
       Unseen-Sequence:     To name sequences denoting unseen messages
       showproc:            Program to show messages


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       mhl(1), more(1), next(1), pick(1), prev(1), scan(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to the current folder
       `msgs' defaults to cur
       `-header'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       If a folder is given, it will become the current folder.  The  last
       message shown will become the current message.































\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  SHOW(1)                           -93-                           SHOW(1)


  _\bB_\bu_\bg_\bs
       The `-header' switch doesn't work when `msgs' expands to more  than
       one  message.   If the _\bs_\bh_\bo_\bw_\bp_\br_\bo_\bc is _\bm_\bh_\bl, then is problem can be cir-
       cumvented by referencing the "messagename" field in the _\bm_\bh_\bl  format
       file.

       _\bS_\bh_\bo_\bw updates the user's context before showing the message.   Hence
       _\bs_\bh_\bo_\bw  will  mark messages as seen prior to the user actually seeing
       them.  This is generally not a problem, unless the user  relies  on
       the  "unseen"  messages  mechanism, and interrupts _\bs_\bh_\bo_\bw while it is
       showing "unseen" messages.

       If _\bs_\bh_\bo_\bw_\bp_\br_\bo_\bc is _\bm_\bh_\bl, then _\bs_\bh_\bo_\bw uses a built-in _\bm_\bh_\bl: it does not  ac-
       tually  run  the  _\bm_\bh_\bl  program.   Hence,  if  you  define  your own
       _\bs_\bh_\bo_\bw_\bp_\br_\bo_\bc, don't call it _\bm_\bh_\bl since _\bs_\bh_\bo_\bw won't run it.

       If _\bm_\bo_\br_\be (1) is your showproc (the default), then avoid running _\bs_\bh_\bo_\bw
       in  the  background  with only its standard output piped to another
       process, as in

            show | imprint &

       Due to a bug in _\bm_\bo_\br_\be, show will go into a "tty  input"  state.   To
       avoid  this  problem,  re-direct  _\bs_\bh_\bo_\bw's diagnostic output as well.
       For users of _\bc_\bs_\bh:

            show |& imprint &

       For users of _\bs_\bh:

            show 2>&1 | imprint &




















\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  SORTM(1)                          -94-                          SORTM(1)


  _\bN_\bA_\bM_\bE
       sortm - sort messages

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       sortm [+folder] [msgs] [-datefield field] [-textfield field]
            [-notextfield] [-limit days] [-nolimit] [-verbose]
            [-noverbose] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bS_\bo_\br_\bt_\bm sorts the specified messages in the named folder according to
       the chronological order of the "Date:" field of each message.

       The `-verbose' switch directs _\bs_\bo_\br_\bt_\bm to tell the  user  the  general
       actions that it is taking to place the folder in sorted order.

       The `-datefield field' switch tells _\bs_\bo_\br_\bt_\bm the name of the field  to
       use  when  making  the  date comparison.  If the user has a special
       field in each message, such as  "BB-Posted:"  or  "Delivery-Date:",
       then  the  `-datefield'  switch  can  be used to direct _\bs_\bo_\br_\bt_\bm which
       field to examine.

       The `-textfield field' switch causes _\bs_\bo_\br_\bt_\bm to sort messages by  the
       specified  text  field.   If  this  field is "subject", any leading
       "re:" is stripped off.  In any case, all characters except  letters
       and  numbers  are  stripped  and  the  resulting strings are sorted
       datefield-major, textfield-minor, using  a  case  insensitive  com-
       parison.

       With `-textfield field', if `-limit days'  is  specified,  messages
       with  similar textfields that are dated within `days' of each other
       appear together.  Specifying `-nolimit' makes the  limit  infinity.
       With   `-limit  0',  the  sort  is  instead  made  textfield-major,
       date-minor.

       For example, to order a folder by date-major, subject-minor, use:

            sortm -textfield subject +folder


  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Current-Folder:      To find the default current folder


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       folder (1)
\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  SORTM(1)                          -95-                          SORTM(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `+folder' defaults to the current folder
       `msgs' defaults to all
       `-datefield date'
       `-notextfield'
       `-noverbose'
       `-nolimit'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       If a folder is given, it will become the current  folder.   If  the
       current  message  is  moved,  _\bs_\bo_\br_\bt_\bm  will  preserve  its  status as
       current.


  _\bH_\bi_\bs_\bt_\bo_\br_\by
       Timezones used to be ignored when comparing dates: they aren't  any
       more.

       Messages which were in the folder, but  not  specified  by  `msgs',
       used  to  be  moved to the end of the folder; now such messages are
       left untouched.

       Previously, _\bs_\bo_\br_\bt_\bm would try to fill any gaps in a folder within the
       range  of  messages  it  sorted.  To improve performance, _\bs_\bo_\br_\bt_\bm now
       minimizes the number of message  moves.   To  pack  a  folder,  use
       "_\bf_\bo_\bl_\bd_\be_\br -_\bp_\ba_\bc_\bk" instead.


  _\bB_\bu_\bg_\bs
       If _\bs_\bo_\br_\bt_\bm encounters a message without a date-field, or if the  mes-
       sage  has a date-field that _\bs_\bo_\br_\bt_\bm cannot parse, then _\bs_\bo_\br_\bt_\bm attempts
       to keep the message in the same relative position.  This  does  not
       always  work.  For instance, if the first message encountered lacks
       a date which can be parsed, then it will usually be placed  at  the
       end of the messages being sorted.

       When _\bs_\bo_\br_\bt_\bm complains about a message which it can't temporally ord-
       er,  it  complains  about  the message number _\bp_\br_\bi_\bo_\br to sorting.  It
       should indicate what the message number will be _\ba_\bf_\bt_\be_\br sorting.











\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  VMH(1)                            -96-                            VMH(1)


  _\bN_\bA_\bM_\bE
       vmh - visual front-end to MH

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       vmh [-prompt string] [-vmhproc program] [-novmhproc]
            [switches for _\bv_\bm_\bh_\bp_\br_\bo_\bc] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bv_\bm_\bh is a program which implements the server side of the _\bM_\bH  window
       management  protocol  and  uses  _\bc_\bu_\br_\bs_\be_\bs (3)  routines to maintain a
       split-screen interface to any program which implements  the  client
       side  of the protocol.  This latter program, called the _\bv_\bm_\bh_\bp_\br_\bo_\bc, is
       specified using the `-vmhproc program' switch.

       The upshot of all this is that one can run _\bm_\bs_\bh on a display  termi-
       nal and get a nice visual interface.  To do this, for example, just
       add the line

            mshproc: vmh

       to your .mh_profile.  (This takes advantage of the fact that _\bm_\bs_\bh is
       the default _\bv_\bm_\bh_\bp_\br_\bo_\bc for _\bv_\bm_\bh.)

       In order to facilitate things, if the `-novmhproc' switch is given,
       and  _\bv_\bm_\bh  can't  run  on  the  user's  terminal, the _\bv_\bm_\bh_\bp_\br_\bo_\bc is run
       directly without the window management protocol.

       After initializing the protocol, _\bv_\bm_\bh prompts the user for a command
       to  be  given to the client.  Usually, this results in output being
       sent to one or more windows.  If a output to a window  would  cause
       it  to  scroll, _\bv_\bm_\bh prompts the user for instructions, roughly per-
       mitting the capabilities of _\bl_\be_\bs_\bs or  _\bm_\bo_\br_\be  (e.g.,  the  ability  to
       scroll backwards and forwards):

            SPACE      advance to the next windowful
            RETURN  *  advance to the next line
            y       *  retreat to the previous line
            d       *  advance to the next ten lines
            u       *  retreat to the previous ten lines
            g       *  go to an arbitrary line
                       (preceed g with the line number)
            G       *  go to the end of the window
                       (if a line number is given, this acts like `g')
            CTRL-L     refresh the entire screen
            h          print a help message
            q          abort the window

       (A `*' indicates that a numeric prefix is meaningful for this  com-
       mand.)

       Note that if a command resulted in more than one window's worth  of

  [mh.6]                           MH.6.7                      UCI version









  VMH(1)                            -97-                            VMH(1)


       information  being  displayed,  and  you allow the command which is
       generating information for the window to gracefully  finish  (i.e.,
       you  don't  use  the `q' command to abort information being sent to
       the window), then _\bv_\bm_\bh will give you one last change to  peruse  the
       window.   This  is  useful for scrolling back and forth.  Just type
       `q' when you're done.

       To abnormally terminate _\bv_\bm_\bh (without core dump), use  <QUIT>  (usu-
       ally  CTRL-\).   For instance, this does the "right" thing with _\bb_\bb_\bc
       and _\bm_\bs_\bh.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       msh(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `-prompt (vmh) '
       `-vmhproc msh'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None


  _\bB_\bu_\bg_\bs
       The argument to the `-prompt' switch must be interpreted as a  sin-
       gle  token by the shell that invokes _\bv_\bm_\bh.  Therefore, one must usu-
       ally place the argument to this switch inside double-quotes.

       At present, there is no way to pass signals (e.g., interrupt, quit)
       to the client.  However, generating QUIT when _\bv_\bm_\bh is reading a com-
       mand from the terminal is sufficient to tell the client to go  away
       quickly.

       Acts strangely (loses peer or botches  window  management  protocol
       with peer) on random occasions.







\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  WHATNOW(1)                        -98-                        WHATNOW(1)


  _\bN_\bA_\bM_\bE
       whatnow - prompting front-end for send

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       whatnow [-draftfolder +folder] [-draftmessage msg] [-nodraftfolder]
            [-editor editor] [-noedit] [-prompt string] [file] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bW_\bh_\ba_\bt_\bn_\bo_\bw is the default program that  queries  the  user  about  the
       disposition  of a composed draft.  It is normally invoked by one of
       _\bc_\bo_\bm_\bp, _\bd_\bi_\bs_\bt, _\bf_\bo_\br_\bw, or _\br_\be_\bp_\bl after the initial edit.

       When started, the editor is started on the draft (unless  `-noedit'
       is  given,  in  which  case the initial edit is suppressed).  Then,
       _\bw_\bh_\ba_\bt_\bn_\bo_\bw repetitively prompts the user with "What now?" and awaits a
       response.  The valid responses are:

       display         to list the message being distributed/replied-to on
                       the terminal
       edit            to re-edit using the same editor that was used on the
                       preceding round unless a profile entry
                       "<lasteditor>-next: <editor>" names an alternate editor
       edit <editor>   to invoke <editor> for further editing
       list            to list the draft on the terminal
       push            to send the message in the background
       quit            to terminate the session and preserve the draft
       quit -delete    to terminate, then delete the draft
       refile +folder  to refile the draft into the given folder
       send            to send the message
       send -watch     to cause the delivery process to be monitored
       whom            to list the addresses that the message will go to
       whom -check     to list the addresses and verify that they are
                       acceptable to the transport service

       For the edit response, any valid switch to  the  editor  is  valid.
       Similarly,  for  the  send  and whom responses, any valid switch to
       _\bs_\be_\bn_\bd (1) and _\bw_\bh_\bo_\bm (1) commands, respectively, are valid.   For  the
       push  response,  any  valid  switch  to  _\bs_\be_\bn_\bd (1) is valid (as this
       merely invokes _\bs_\be_\bn_\bd with  the  `-push'  option).   For  the  _\br_\be_\bf_\bi_\bl_\be
       response,  any  valid  switch  to  the  _\bf_\bi_\bl_\be_\bp_\br_\bo_\bc is valid.  For the
       display and list responses, any valid  argument  to  the  _\bl_\bp_\br_\bo_\bc  is
       valid.   If any non-switch arguments are present, then the pathname
       of the draft will be excluded from the argument list given  to  the
       _\bl_\bp_\br_\bo_\bc (this is useful for listing another _\bM_\bH message).

       See _\bm_\bh-_\bp_\br_\bo_\bf_\bi_\bl_\be (5) for further information about  how  editors  are
       used  by MH.  It also discusses how complex envariables can be used
       to direct _\bw_\bh_\ba_\bt_\bn_\bo_\bw's actions.

       The `-prompt string' switch sets the prompting string for _\bw_\bh_\ba_\bt_\bn_\bo_\bw.
\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  WHATNOW(1)                        -99-                        WHATNOW(1)


       The `-draftfolder +folder' and `-draftmessage msg' switches  invoke
       the _\bM_\bH draft folder facility.  This is an advanced (and highly use-
       ful) feature.  Consult the Advanced  Features  section  of  the  _\bM_\bH
       manual for more information.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile
       <mh-dir>/draft                      The draft file


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Draft-Folder:        To find the default draft-folder
       Editor:              To override the default editor
       <lasteditor>-next:   To name an editor to be used after  exit  from
       <lasteditor>
       fileproc:            Program to refile the message
       lproc:               Program to list the contents of a message
       sendproc:            Program to use to send the message
       whomproc:            Program to determine who a message would go to


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       send(1), whom(1)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `-prompt "What Now? "'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None


  _\bB_\bu_\bg_\bs
       The argument to the `-prompt' switch must be interpreted as a  sin-
       gle  token  by the shell that invokes _\bw_\bh_\ba_\bt_\bn_\bo_\bw.  Therefore, one must
       usually place the argument to this switch inside double-quotes.

       If the initial edit fails, _\bw_\bh_\ba_\bt_\bn_\bo_\bw deletes your draft (by  renaming
       it  with  a  leading  comma); failure of a later edit preverves the
       draft.

       If _\bw_\bh_\ba_\bt_\bn_\bo_\bw_\bp_\br_\bo_\bc is _\bw_\bh_\ba_\bt_\bn_\bo_\bw, then _\bc_\bo_\bm_\bp, _\bd_\bi_\bs_\bt, _\bf_\bo_\br_\bw, and  _\br_\be_\bp_\bl  use  a
       built-in  _\bw_\bh_\ba_\bt_\bn_\bo_\bw,  and  do  not  actually run the _\bw_\bh_\ba_\bt_\bn_\bo_\bw program.
       Hence, if you define your own _\bw_\bh_\ba_\bt_\bn_\bo_\bw_\bp_\br_\bo_\bc, don't  call  it  _\bw_\bh_\ba_\bt_\bn_\bo_\bw
       since it won't be run.

       If _\bs_\be_\bn_\bd_\bp_\br_\bo_\bc is _\bs_\be_\bn_\bd, then _\bw_\bh_\ba_\bt_\bn_\bo_\bw uses a built-in _\bs_\be_\bn_\bd, it does not
       actually  run  the  _\bs_\be_\bn_\bd  program.   Hence,  if you define your own
       _\bs_\be_\bn_\bd_\bp_\br_\bo_\bc, don't call it _\bs_\be_\bn_\bd since _\bw_\bh_\ba_\bt_\bn_\bo_\bw won't run it.
\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  WHATNOW(1)                       -100-                        WHATNOW(1)


  _\bN_\bA_\bM_\bE
       whom - report to whom a message would go

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       whom [-alias aliasfile] [-check] [-nocheck] [-draft]
            [-draftfolder +folder] [-draftmessage msg] [-nodraftfolder]
            [file] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bW_\bh_\bo_\bm is used to expand the headers of  a  message  into  a  set  of
       addresses  and  optionally verify that those addresses are deliver-
       able at that time (if `-check' is given).

       The `-draftfolder +folder' and `-draftmessage msg' switches  invoke
       the _\bM_\bH draft folder facility.  This is an advanced (and highly use-
       ful) feature.  Consult the Advanced  Features  section  of  the  _\bM_\bH
       manual for more information.

       The file specified by the profile entry "Aliasfile:" and any  addi-
       tional  alias  files given by the `-alias aliasfile' switch will be
       read (more than one file,  each   preceeded  by  `-alias',  can  be
       named).  See _\bm_\bh-_\ba_\bl_\bi_\ba_\bs (5) for more information.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To determine the user's MH directory
       Draft-Folder:        To find the default draft-folder
       Aliasfile:           For a default alias file
       postproc:            Program to post the message


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       mh-alias(5), post(8)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `file' defaults to <mh-dir>/draft
       `-nocheck'
       `-alias /usr/local/lib/mh/MailAliases'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None




\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  WHOM(1)                          -101-                           WHOM(1)


  _\bB_\bu_\bg_\bs
       With the `-check' option, _\bw_\bh_\bo_\bm makes no  guarantees  that  the  ad-
       dresses  listed  as being ok are really deliverable, rather, an ad-
       dress being listed as ok means that at the time that _\bw_\bh_\bo_\bm  was  run
       the address was thought to be deliverable by the transport service.
       For local addresses, this is absolute; for  network  addresses,  it
       means  that the host is known; for uucp addresses, it (often) means
       that the _\bU_\bU_\bC_\bP network is available for use.











































\e9
\e9       [mh.6]                           MH.6.7                      UCI version









                                        -102-


       _\bM_\bO_\bR_\bE _\bD_\bE_\bT_\bA_\bI_\bL_\bS

            This section describes some of the more intense points  of  the  _\bM_\bH
       system,  by  expanding  on  topics  previously  discussed.   The  format
       presented conforms to the standard form  for  the  description  of  UNIX
  documentation.













































\e9
\e9









  MH-ALIAS(5)                      -103-                       MH-ALIAS(5)


  _\bN_\bA_\bM_\bE
       mh-alias - alias file for MH message system

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       any _\bM_\bH command

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       This describes both _\bM_\bH personal alias files and the (primary) alias
       file for mail delivery, the file

               /usr/local/lib/mh/MailAliases

       It does not describe aliases files used by  the  message  transport
       system.  Each line of the alias file has the format:

               alias : address-group
       or
               alias ; address-group
       or
               < alias-file
       or
               ; comment

       where:

               address-group  :=  address-list
                              |   "<" file
                              |   "=" UNIX-group
                              |   "+" UNIX-group
                              |   "*"

               address-list   :=  address
                              |   address-list, address

       Continuation lines in alias files end with `\' followed by the new-
       line character.

       Alias-file and file are UNIX file names.   UNIX-group  is  a  group
       name  (or  number)  from  /_\be_\bt_\bc/_\bg_\br_\bo_\bu_\bp.   An  address  is  a "simple"
       Internet-style address.  Througout  this  file,  case  is  ignored,
       except for alias-file names.

       If the line starts with a `<', then the file named after the `<' is
       read  for more alias definitions.  The reading is done recursively,
       so a `<' may occur in the beginning  of  an  alias  file  with  the
       expected results.

       If the address-group starts with a `<', then the file  named  after
       the  `<' is read and its contents are added to the address-list for
       the alias.
\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MH-ALIAS(5)                      -104-                       MH-ALIAS(5)


       If the address-group starts with an `=', then the  file  /_\be_\bt_\bc/_\bg_\br_\bo_\bu_\bp
       is  consulted  for  the UNIX-group named after the `='.  Each login
       name  occurring  as  a  member  of  the  group  is  added  to   the
       address-list for the alias.

       In contrast, if the address-group starts with a `+', then the  file
       /_\be_\bt_\bc/_\bg_\br_\bo_\bu_\bp is consulted to determine the group-id of the UNIX-group
       named after the `+'.  Each login name occurring in the  /_\be_\bt_\bc/_\bp_\ba_\bs_\bs_\bw_\bd
       file  whose  group-id  is  indicated  by this group is added to the
       address-list for the alias.

       If the address-group is simply `*', then the  file  /_\be_\bt_\bc/_\bp_\ba_\bs_\bs_\bw_\bd  is
       consulted and all login names with a userid greater than some magic
       number (usually 200) are added to the address-list for the alias.

       In match, a trailing * on an alias will match just  about  anything
       appropriate.  (See example below.)

       An approximation of the way aliases are resolved at posting time is
       (it's not really done this way):

            1) Build a list of  all  addresses  from  the  message  to  be
            delivered, eliminating duplicate addresses.

            2) If this draft originated on the local host, then for  those
            addresses  in the message that have no host specified, perform
            alias resolution.

            3) For each line in the alias file,  compare  "alias"  against
            all of the existing addresses.  If a match, remove the matched
            "alias" from the address list, and add each new address in the
            address-group  to the address list if it is not already on the
            list.  The alias itself is  not  usually  output,  rather  the
            address-group  that  the  alias maps to is 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  _\bM_\bH  aliases  and  personal
            aliases are unknown to the mail transport system.)

       Since the alias file is read line by line, forward references work,
       but  backward  references  are  not  recognized,  thus, there is no
       recursion.

       Example:
            </usr/local/lib/mh/BBoardAliases
            sgroup: fred, fear, freida
            fred: frated@UCI
            UNIX-committee: <unix.aliases
            staff: =staff
            wheels: +wheel
            everyone: *
            news.*: news

  [mh.6]                           MH.6.7                      UCI version









  MH-ALIAS(5)                      -105-                       MH-ALIAS(5)


       The first line says that more aliases should  immediately  be  read
       from  the  file  /_\bu_\bs_\br/_\bl_\bo_\bc_\ba_\bl/_\bl_\bi_\bb/_\bm_\bh/_\bB_\bB_\bo_\ba_\br_\bd_\bA_\bl_\bi_\ba_\bs_\be_\bs.   Following this,
       "fred" is defined as an alias for  "frated@UCI",  and  "sgroup"  is
       defined  as  an alias for the three names "frated@UCI", "fear", and
       "freida".  Next, the definition of  "UNIX-committee"  is  given  by
       reading the file _\bu_\bn_\bi_\bx._\ba_\bl_\bi_\ba_\bs_\be_\bs in the users _\bM_\bH directory, "staff" is
       defined as all users who are listed as members of the group "staff"
       in  the /_\be_\bt_\bc/_\bg_\br_\bo_\bu_\bp file, and "wheels" is defined as all users whose
       group-id  in  /_\be_\bt_\bc/_\bp_\ba_\bs_\bs_\bw_\bd  is  equivalent  to  the  "wheel"  group.
       Finally,  "everyone"  is  defined  as  all  users with a user-id in
       /_\be_\bt_\bc/_\bp_\ba_\bs_\bs_\bw_\bd  greater  than  200,  and  all  aliases  of  the   form
       "news.<anything>" are defined to be "news".

       The key thing to understand about aliasing in _\bM_\bH is that aliases in
       _\bM_\bH  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 is given  a  message  to  deliver  to  a  list  of
       addresses, for each address that appears to be local, a system-wide
       alias file is consulted.  These aliases are NOT expanded  into  the
       headers of messages delivered.

  _\bH_\be_\bl_\bp_\bf_\bu_\bl _\bH_\bi_\bn_\bt_\bs

       To use aliasing in _\bM_\bH quickly, do the following:

            First, in your ._\bm_\bh__\bp_\br_\bo_\bf_\bi_\bl_\be, choose a  name  for  your  primary
            alias file, say "aliases", and add the line:

                 Aliasfile: aliases

            Second, create the file "aliases" in your _\bM_\bH directory.

            Third,  start  adding  aliases  to  your  "aliases"  file   as
            appropriate.

  _\bF_\bi_\bl_\be_\bs
       /usr/local/lib/mh/MailAliases       Primary alias file


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Aliasfile:           For a default alias file


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       ali(1), send(1), whom(1), group(5), passwd(5), conflict(8), post(8)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       None

\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MH-ALIAS(5)                      -106-                       MH-ALIAS(5)


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None


  _\bH_\bi_\bs_\bt_\bo_\br_\by
       In previous releases of _\bM_\bH, only  a  single,  system-wide  mh-alias
       file  was  supported.  Now that _\bM_\bH uses _\bM_\bM_\bD_\bF as a transport system,
       the system-wide aliasing facility can  be  more  consistently  con-
       trolled  by  the  latter.   This  means  that  at  most  sites, the
       system-wide mh-alias file will  be  empty  (or  trivial  at  best).
       Hence,  the semantics of mh-alias were extended to support personal
       alias files.  Users of _\bM_\bH no longer need to bother mail-system  ad-
       ministrators for keeping information in the system-wide alias file,
       as each _\bM_\bH user can create/modify/remove aliases at will  from  any
       number of personal files.


  _\bB_\bu_\bg_\bs
       Although  the  forward-referencing  semantics  of  _\bm_\bh-_\ba_\bl_\bi_\ba_\bs   files
       prevent  recursion,  the  "< alias-file"  command  may defeat this.
       Since the number of file descriptors is finite (and very  limited),
       such  infinite recursion will terminate with a meaningless diagnos-
       tic when all the fds are used up.




























\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MH-FORMAT(5)                     -107-                      MH-FORMAT(5)


  _\bN_\bA_\bM_\bE
       mh-format - format file for MH message system

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       some _\bM_\bH commands

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       Several _\bM_\bH commands utilize either a _\bf_\bo_\br_\bm_\ba_\bt string or a _\bf_\bo_\br_\bm_\ba_\bt file
       during their execution.  For example, _\bs_\bc_\ba_\bn (1) uses a format string
       which directs it how to generate the scan listing for each message;
       _\br_\be_\bp_\bl (1)  uses  a  format file which directs it how to generate the
       reply to a message, and so on.

       Format strings are designed to be efficiently parsed  by  _\bM_\bH  which
       means  they  are  not  necessarily  simple to write and understand.
       This means that novice, casual, or even advanced users of _\bM_\bH should
       not  have  to deal with them.  Some canned scan listing formats are
       in  /usr/local/lib/mh/scan.time,  /usr/local/lib/mh/scan.size,  and
       /usr/local/lib/mh/scan.timely.  Look in /usr/local/lib/mh for other
       _\bs_\bc_\ba_\bn and _\br_\be_\bp_\bl format files which may  have  been  written  at  your
       site.

       It suffices to have your local _\bM_\bH expert actually write new  format
       commands or modify existing ones.  This manual section explains how
       to do that.   Note:  familiarity  with  the  C  _\bp_\br_\bi_\bn_\bt_\bf  routine  is
       assumed.

       A format string consists  of  ordinary  text,  and  special  multi-
       character _\be_\bs_\bc_\ba_\bp_\be sequences which begin with `%'.  When specifying a
       format string, the usual C backslash characters are honored:  `\b',
       `\f', `\n', `\r', and `\t'.  Continuation lines in format files end
       with `\' followed by the newline character.  There are three  types
       of  _\be_\bs_\bc_\ba_\bp_\be  sequences:  header _\bc_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs, built-in _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\bs, and,
       flow _\bc_\bo_\bn_\bt_\br_\bo_\bl.

       A _\bc_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt escape is specified as `%{_\bc_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt}', and  exists  for
       each  header  found  in  the  message being processed.  For example
       `%{date}' refers to the "Date:" field of the  appropriate  message.
       All  component  escapes  have  a string value.  Normally, component
       values are compressed by converting any control characters (tab and
       newline  included)  to spaces, then eliding any leading or multiple
       spaces.  However, commands may give  different  interpretations  to
       some  component  escapes; be sure to refer to each command's manual
       entry for complete details.

       A _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn escape is specified as `%(_\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn)'.  All functions are
       built-in, and most have a string or numeric value.



\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MH-FORMAT(5)                     -108-                      MH-FORMAT(5)


    _\bC_\bo_\bn_\bt_\br_\bo_\bl-_\bf_\bl_\bo_\bw _\be_\bs_\bc_\ba_\bp_\be_\bs

       A _\bc_\bo_\bn_\bt_\br_\bo_\bl escape is one of: `%<', `%?', `%|', or  `%>'.  These  are
       combined into the conditional execution construct:

               %<condition
                       _\bf_\bo_\br_\bm_\ba_\bt _\bt_\be_\bx_\bt _\b1
               %?condition2
                       _\bf_\bo_\br_\bm_\ba_\bt _\bt_\be_\bx_\bt _\b2
               %?condition3
                       _\bf_\bo_\br_\bm_\ba_\bt _\bt_\be_\bx_\bt _\b3
               ...
               %|
                       _\bf_\bo_\br_\bm_\ba_\bt _\bt_\be_\bx_\bt _\bN
               %>

       Extra white space is shown here only for clarity.  These constructs
       may   be   nested   without   ambiguity.    They   form  a  general
       if-elseif-else-endif block where only one of the _\bf_\bo_\br_\bm_\ba_\bt  _\bt_\be_\bx_\bt  seg-
       ments is interpreted.

       The `%<'  and  `%?'  control  escapes  causes  a  condition  to  be
       evaluated.  This condition may be either a _\bc_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt or a _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn.
       The four constructs have the following syntax:

               %<{component}
               %<(function)
               %?{component}
               %?(function)

       These control escapes test whether the function or component  value
       is   non-zero  (for  integer-valued  escapes),  or  non-empty  (for
       string-valued escapes).

       If this test evaulates true, then the format text up  to  the  next
       corresponding control escape (one of `%|', `%?', or `%>') is inter-
       preted normally.  Next, all format text  up  to  the  corresponding
       `%>'  control  escape (if any) is skipped.  The `%>' control escape
       is not interpreted; normal interpretation resumes  after  the  `%>'
       escape.

       If the test evaluates false, however, then the format  text  up  to
       the next corresponding control escape (again, one of `%|', `%?', or
       `%>') is skipped, instead of being  interpreted.   If  the  control
       escape  encountered  was  `%?',  then the condition associated with
       that control escape is evaluated, and interpretation proceeds after
       that  test  as described in the previous paragraph.  If the control
       escape encountered was  `%|',  then  the  format  text  up  to  the
       corresponding  `%>'  escape is interpreted normally.  As above, the
       `%>' escape is not interpreted and  normal  interpretation  resumes
       after the `%>' escape.
\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MH-FORMAT(5)                     -109-                      MH-FORMAT(5)


       The `%?' control escape and its following format text is  optional,
       and  may  be  included zero or more times.  The `%|' control escape
       and its following format text is also optional, and may be included
       zero or one times.


    _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn _\be_\bs_\bc_\ba_\bp_\be_\bs

       Most functions expect an argument of a particular type:

       _\bA_\br_\bg_\bu_\bm_\be_\bn_\bt _\bD_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn            _\bE_\bx_\ba_\bm_\bp_\bl_\be _\bS_\by_\bn_\bt_\ba_\bx
       literal  A literal number,      %(_\bf_\bu_\bn_\bc 1234)
                or string              %(_\bf_\bu_\bn_\bc text string)
       comp     Any header component   %(_\bf_\bu_\bn_\bc{_\bi_\bn-_\br_\be_\bp_\bl_\by-_\bt_\bo})
       date     A date component       %(_\bf_\bu_\bn_\bc{_\bd_\ba_\bt_\be})
       addr     An address component   %(_\bf_\bu_\bn_\bc{_\bf_\br_\bo_\bm})
       expr     An optional component, %(_\bf_\bu_\bn_\bc(_\bf_\bu_\bn_\bc_\b2))
                function or control,   %(_\bf_\bu_\bn_\bc %<{_\br_\be_\bp_\bl_\by-_\bt_\bo}%|%{_\bf_\br_\bo_\bm}%>)
                perhaps nested         %(_\bf_\bu_\bn_\bc(_\bf_\bu_\bn_\bc_\b2{_\bc_\bo_\bm_\bp}))

       The types _\bd_\ba_\bt_\be and _\ba_\bd_\bd_\br have the same syntax as _\bc_\bo_\bm_\bp,  but  require
       that  the  header  component  be  a date string, or address string,
       respectively.

       All arguments except those of type _\be_\bx_\bp_\br are required.  For the _\be_\bx_\bp_\br
       argument  type,  the  leading `%' must be omitted for component and
       function escape arguments, and must  be  present  (with  a  leading
       space) for control escape arguments.

       The evaluation of format strings is based on a simple machine  with
       an  integer  register  _\bn_\bu_\bm, and a text string register _\bs_\bt_\br.  When a
       function escape is processed, if it accepts an optional _\be_\bx_\bp_\br  argu-
       ment which is not present, it reads the current value of either _\bn_\bu_\bm
       or _\bs_\bt_\br as appropriate.


    _\bR_\be_\bt_\bu_\br_\bn _\bv_\ba_\bl_\bu_\be_\bs

       Component escapes write the value of their message header  in  _\bs_\bt_\br.
       Function  escapes  write  their  return  value in _\bn_\bu_\bm for functions
       returning _\bi_\bn_\bt_\be_\bg_\be_\br or _\bb_\bo_\bo_\bl_\be_\ba_\bn  values,  and  in  _\bs_\bt_\br  for  functions
       returning string values.  (The _\bb_\bo_\bo_\bl_\be_\ba_\bn type is a subset of integers
       with usual values 0=false and 1=true.)

       All component escapes, and those function escapes which  return  an
       _\bi_\bn_\bt_\be_\bg_\be_\br  or  _\bs_\bt_\br_\bi_\bn_\bg  value, pass this value back to their caller in
       addition to setting _\bs_\bt_\br or _\bn_\bu_\bm.  These escapes will print out  this
       value  unless  called  as  part  of  an  argument to another escape
       sequence.  Function escapes which return a _\bb_\bo_\bo_\bl_\be_\ba_\bn  value  do  pass
       this  value  back  to  their  caller,  but will never print out the
       value.
\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MH-FORMAT(5)                     -110-                      MH-FORMAT(5)


       _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn   _\bA_\br_\bg_\bu_\bm_\be_\bn_\bt _\bR_\be_\bt_\bu_\br_\bn   _\bD_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn
       msg                 integer  message number
       cur                 integer  message is current
       size                integer  size of message
       strlen              integer  length of _\bs_\bt_\br
       width               integer  output buffer size in bytes
       charleft            integer  bytes left in output buffer
       timenow             integer  seconds since the UNIX epoch
       me                  string   the user's mailbox
       eq         literal  boolean  _\bn_\bu_\bm == _\ba_\br_\bg
       ne         literal  boolean  _\bn_\bu_\bm != _\ba_\br_\bg
       gt         literal  boolean  _\bn_\bu_\bm > _\ba_\br_\bg
       match      literal  boolean  _\bs_\bt_\br contains _\ba_\br_\bg
       amatch     literal  boolean  _\bs_\bt_\br starts with _\ba_\br_\bg
       plus       literal  integer  _\ba_\br_\bg plus _\bn_\bu_\bm
       minus      literal  integer  _\ba_\br_\bg minus _\bn_\bu_\bm
       divide     literal  integer  _\bn_\bu_\bm divided by _\ba_\br_\bg
       num        literal  integer  Set _\bn_\bu_\bm to _\ba_\br_\bg
       lit        literal  string   Set _\bs_\bt_\br to _\ba_\br_\bg
       nonzero    expr     boolean  _\bn_\bu_\bm is non-zero
       zero       expr     boolean  _\bn_\bu_\bm is zero
       null       expr     boolean  _\bs_\bt_\br is empty
       nonnull    expr     boolean  _\bs_\bt_\br is non-empty
       void       expr              Set _\bs_\bt_\br or _\bn_\bu_\bm
       comp       comp     string   Set _\bs_\bt_\br to component text
       compval    comp     integer  _\bn_\bu_\bm set to "atoi(_\bs_\bt_\br)"
       trim       expr              trim trailing white-space from _\bs_\bt_\br
       putstr     expr              print _\bs_\bt_\br
       putstrf    expr              print _\bs_\bt_\br in a fixed width
       putnum     expr              print _\bn_\bu_\bm
       putnumf    expr              print _\bn_\bu_\bm in a fixed width

       These functions require a date component as an argument:

       _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn   _\bA_\br_\bg_\bu_\bm_\be_\bn_\bt _\bR_\be_\bt_\bu_\br_\bn   _\bD_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn
       sec        date     integer  seconds of the minute
       min        date     integer  minutes of the hour
       hour       date     integer  hours of the day (0-23)
       wday       date     integer  day of the week (Sun=0)
       day        date     string   day of the week (abbrev.)
       weekday    date     string   day of the week
       sday       date     integer  day of the week known?
                                    (0=implicit,-1=unknown)
       mday       date     integer  day of the month
       yday       date     integer  day of the year
       mon        date     integer  month of the year
       month      date     string   month of the year (abbrev.)
       lmonth     date     string   month of the year
       year       date     integer  year of the century
       zone       date     integer  timezone in hours
       tzone      date     string   timezone string
       szone      date     integer  timezone explicit?

  [mh.6]                           MH.6.7                      UCI version









  MH-FORMAT(5)                     -111-                      MH-FORMAT(5)


                                    (0=implicit,-1=unknown)
       date2local date              coerce date to local timezone
       date2gmt   date              coerce date to GMT
       dst        date     integer  daylight savings in effect?
       clock      date     integer  seconds since the UNIX epoch
       rclock     date     integer  seconds prior to current time
       tws        date     string   official 822 rendering
       pretty     date     string   user-friendly rendering
       nodate     date     integer  _\bs_\bt_\br not a date string

       These functions require an address component as  an  argument.  The
       return  value of functions noted with `*' pertain only to the first
       address present in the header component.

       _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn   _\bA_\br_\bg_\bu_\bm_\be_\bn_\bt _\bR_\be_\bt_\bu_\br_\bn   _\bD_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn
       proper     addr     string   official 822 rendering
       friendly   addr     string   user-friendly rendering
       addr       addr     string   mbox@host or host!mbox rendering*
       pers       addr     string   the personal name*
       note       addr     string   commentary text*
       mbox       addr     string   the local mailbox*
       mymbox     addr     integer  the user's addresses? (0=no,1=yes)
       host       addr     string   the host domain*
       nohost     addr     integer  no host was present*
       type       addr     integer  host type* (0=local,1=network,
                                    -1=uucp,2=unknown)
       path       addr     string   any leading host route*
       ingrp      addr     integer  address was inside a group*
       gname      addr     string   name of group*
       formataddr expr              append _\ba_\br_\bg to _\bs_\bt_\br as a
                                    (comma separated) address list
       putaddr    literal           print _\bs_\bt_\br address list with
                                    _\ba_\br_\bg as optional label;
                                    get line width from _\bn_\bu_\bm

       When escapes are nested, evaluation  is  done  from  inner-most  to
       outer-most.   The  outer-most escape must begin with `%'; the inner
       escapes must not.  For example,

            %<(mymbox{from}) To: %{to}%>

       writes the value of the header component "From:" to _\bs_\bt_\br; then (_\bm_\by_\bm_\b-
       _\bb_\bo_\bx)  reads  _\bs_\bt_\br  and  writes  its  result to _\bn_\bu_\bm; then the control
       escape evaluates _\bn_\bu_\bm.  If _\bn_\bu_\bm is non-zero, the  string  "To:  "  is
       printed followed by the value of the header component "To:".

       A minor explanation of (_\bm_\by_\bm_\bb_\bo_\bx{_\bc_\bo_\bm_\bp}) is in order.  In general,  it
       checks each of the addresses in the header component "_\bc_\bo_\bm_\bp" against
       the user's mailbox name and any  _\bA_\bl_\bt_\be_\br_\bn_\ba_\bt_\be-_\bM_\ba_\bi_\bl_\bb_\bo_\bx_\be_\bs.   It  returns
       true  if  any address matches, however, it also returns true if the
       "_\bc_\bo_\bm_\bp" header is not present in the message.  If needed, the (_\bn_\bu_\bl_\bl)
       function can be used to explicitly test for this condition.

  [mh.6]                           MH.6.7                      UCI version









  MH-FORMAT(5)                     -112-                      MH-FORMAT(5)


       When a function or component escape is interpreted and  the  result
       will  be immediately printed, an optional field width can be speci-
       fied to print the field in exactly a given  number  of  characters.
       For  example,  a  numeric escape like %4(_\bs_\bi_\bz_\be) will print at most 4
       digits of the message size; overflow will be indicated by a `?'  in
       the first position (like `?234').  A string escape like %4(_\bm_\be) will
       print the first 4 characters and truncate at the end. Short  fields
       are  padded  at  the  right  with  the  fill character (normally, a
       blank).  If the field width argument begins with  a  leading  zero,
       then the fill character is set to a zero.

       As above, the functions (_\bp_\bu_\bt_\bn_\bu_\bm_\bf) and (_\bp_\bu_\bt_\bs_\bt_\br_\bf) print their  result
       in  exactly  the  number  of  characters specified by their leading
       field width argument. For example,  %06(_\bp_\bu_\bt_\bn_\bu_\bm_\bf(_\bs_\bi_\bz_\be))  will  print
       the message size in a field six characters wide filled with leading
       zeros; %14(_\bp_\bu_\bt_\bs_\bt_\br_\bf{_\bf_\br_\bo_\bm}) will print the "From:"  header  component
       in  fourteen  characters with trailing spaces added as needed.  For
       _\bp_\bu_\bt_\bs_\bt_\br_\bf, using a negative value for the field width  causes  right-
       justification  of  the string within the field, with padding on the
       left up to the field width.  The functions  (_\bp_\bu_\bt_\bn_\bu_\bm)  and  (_\bp_\bu_\bt_\bs_\bt_\br)
       print  their  result  in the minimum number of characters required,
       and ignore any leading field width argument.

       The available output width is kept in  an  internal  register;  any
       output past this width will be truncated.

       With all this in mind, here's the default format string  for  _\bs_\bc_\ba_\bn.
       It's  been  divided into several pieces for readability.  The first
       part is:

            %4(putnumf(msg))%<(cur)+%| %>%<{replied}-%| %>

       which says that the  message  number  should  be  printed  in  four
       digits,  if  the  message  is the current message then a `+' else a
       space should be printed, and if a "Replied:" field is present  then
       a `-' else a space should be printed.  Next:

            %02(putnumf(mon{date}))/%02(putnumf(mday{date}))

       the month  and  date  are  printed  in  two  digits  (zero  filled)
       separated by a slash.  Next,

            %<{date} %|*>

       If a "Date:" field was present, then a space is printed,  otherwise
       a `*'.  Next,

            %<(mymbox{from})To:%14(putstrf(friendly{to}))

       if the message is  from  me,  print  `To:'  followed  by  a  "user-
       friendly"  rendering of the first address in the "To:" field.  Con-
       tinuing,

  [mh.6]                           MH.6.7                      UCI version









  MH-FORMAT(5)                     -113-                      MH-FORMAT(5)


            %|%17(putstrf(friendly{from}))%>

       if the message isn't from me, then the print the "From:" address is
       printed.  And finally,

            %{subject}%<{body}<<%{body}%>

       the subject and initial body (if any) are printed.

       For a more complicated example, next consider the default _\br_\be_\bp_\bl_\bc_\bo_\bm_\bp_\bs
       format file.

            %(lit)%(formataddr %<{reply-to}%|

       This clears _\bs_\bt_\br and formats the "Reply-To:" header if present.   If
       not present, the else clause is executed:

            %<{from}%|%<{sender}%|%<{return-path}%>%>%>%>)\

       This formats the "From:",  "Sender:"  and  "Return-Path:"  headers,
       stopping as soon as one of them is present.  Next:

            %<(nonnull)%(void(width))%(putaddr To: )\n%>\

       If the _\bf_\bo_\br_\bm_\ba_\bt_\ba_\bd_\bd_\br result is non-null, it is printed as  an  address
       (with  line folding if needed) in a field _\bw_\bi_\bd_\bt_\bh wide with a leading
       label of "To: ".

            %(lit)%(formataddr{to})%(formataddr{cc})%(formataddr(me))\

       _\bs_\bt_\br is cleared, and the "To:" and "Cc:"  headers,  along  with  the
       user's  address  (depending  on  what  was specified with the "-cc"
       switch to _\br_\be_\bp_\bl) are formatted.

            %<(nonnull)%(void(width))%(putaddr cc: )\n%>\

       If the result is non-null, it is printed as above  with  a  leading
       label of "cc: ".

            %<{fcc}Fcc: %{fcc}\n%>\

       If a "-fcc folder" switch was given to _\br_\be_\bp_\bl (see _\br_\be_\bp_\bl (1) for  more
       details about %{_\bf_\bc_\bc}), an "Fcc:" header is output.

            %<{subject}Subject: Re: %{subject}\n%>\

       If a subject component was present, a  suitable  reply  subject  is
       output.

            %<{date}In-reply-to: Your message of "\
            %<(nodate{date})%{date}%|%(tws{date})%>."%<{message-id}
                         %{message-id}%>\n%>\

  [mh.6]                           MH.6.7                      UCI version









  MH-FORMAT(5)                     -114-                      MH-FORMAT(5)


            --------

       If a date component was present, an "In-Reply-To:" header is output
       with the preface "Your message of ".  If the date was parseable, it
       is output in official format, otherwise it is  output  as-is.   The
       message-id is included if present.  As with all plain-text, the row
       of dashes are output as-is.

       This last part is a good example for  a  little  more  elaboration.
       Here's that part again in pseudo-code:

            if (comp_exists(date))  then
                 print ("In-reply-to: Your message of \"")
                 if (not_date_string(date.value) then
                      print (date.value)
                 else
                      print (rfc822(date.value))
                 endif
                 print ("\"")
                 if (comp_exists(message-id)) then
                      print ("\n\t")
                      print (message-id.value)
                 endif
                 print ("\n")
            endif

       Although this seems complicated, in point of fact, this  method  is
       flexible  enough to extract individual fields and print them in any
       format the user desires.

  _\bF_\bi_\bl_\be_\bs
       None


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       None


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       scan(1), repl(1), ap(8), dp(8)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       None


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None



\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MH-FORMAT(5)                     -115-                      MH-FORMAT(5)


  _\bH_\bi_\bs_\bt_\bo_\br_\by
       This software was contributed for MH 6.3.  Prior  to  this,  output
       format  specifications  were much easier to write, but considerably
       less flexible.


  _\bB_\bu_\bg_\bs
       On hosts where _\bM_\bH was configured  with  the  BERK  option,  address
       parsing is not enabled.










































\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MH-MAIL(5)                       -116-                        MH-MAIL(5)


  _\bN_\bA_\bM_\bE
       mh-mail - message format for MH message system

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       any _\bM_\bH command

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bM_\bH processes messages in a particular format.  It should  be  noted
       that  although  neither  Bell  nor Berkeley mailers produce message
       files in the format that _\bM_\bH prefers, _\bM_\bH can read message  files  in
       that antiquated format.

       Each user possesses a mail drop box which  initially  receives  all
       messages  processed  by _\bp_\bo_\bs_\bt (8).  _\bI_\bn_\bc (1) will read from that drop
       box and incorporate the new messages found there  into  the  user's
       own  mail folders (typically `+inbox').  The mail drop box consists
       of one or more messages.  To facilitate the separation of messages,
       each  message begins and ends with a line consisting of nothing but
       four CTRL-A (octal 001) characters.

       Messages are expected to consist of lines of  text.   Graphics  and
       binary data are not handled.  No data compression is accepted.  All
       text is clear ASCII 7-bit data.

       The general "memo" framework of RFC-822 is used.   A  message  con-
       sists of a block of information in a rigid format, followed by gen-
       eral text with no specified format.  The  rigidly  formatted  first
       part of a message is called the header, and the free-format portion
       is 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 _\bM_\bH, the header and body may
       be separated by a line consisting of dashes:

            To:
            cc:
            Subject:
            --------

       The header is composed of one or more header  items.   Each  header
       item  can  be  viewed as a single logical line of ASCII characters.
       If the text of a header item extends across several real lines, the
       continuation lines are indicated by leading spaces or tabs.

       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 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.

       The  text  for  most  formatted  components  (e.g.,   "Date:"   and

  [mh.6]                           MH.6.7                      UCI version









  MH-MAIL(5)                       -117-                        MH-MAIL(5)


       "Message-Id:") is produced automatically.  The only ones entered by
       the user are address fields such as "To:",  "cc:",  etc.   Internet
       addresses  are  assigned mailbox names and host computer specifica-
       tions.  The rough format is "local@domain", such  as  "MH@UCI",  or
       "MH@UCI-ICSA.ARPA".  Multiple addresses are separated by commas.  A
       missing host/domain is assumed to be the local host/domain.

       As mentioned above, a blank line (or a line of dashes) signals that
       all  following text up to the end of the file is the body.  No for-
       matting is expected or enforced within the body.

       Following is a list of header components that are considered  mean-
       ingful to various MH programs.
       Date:
            Added by _\bp_\bo_\bs_\bt (8), contains date and  time  of  the  message's
            entry into the transport system.

       From:
            Added by _\bp_\bo_\bs_\bt (8), contains  the  address  of  the  author  or
            authors  (may  be  more  than  one  if  a  "Sender:"  field is
            present).  Replies are typically directed to addresses in  the
            "Reply-To:"  or  "From:"  field  (the former has precedence if
            present).

       Sender:
            Added by _\bp_\bo_\bs_\bt (8) in the event that the message already has  a
            "From:"  line.   This  line contains the address of the actual
            sender.  Replies are never sent to addresses in the  "Sender:"
            field.

       To:
            Contains addresses of primary recipients.

       cc:
            Contains addresses of secondary recipients.

       Bcc:
            Still more recipients.  However, the "Bcc:" line is not copied
            onto  the  message  as  delivered, so these recipients are not
            listed.  _\bM_\bH uses an encapsulation method for blind copies, see
            _\bs_\be_\bn_\bd (1).

       Fcc:
            Causes _\bp_\bo_\bs_\bt (8) to copy the message into the specified  folder
            for  the  sender, if the message was successfully given to the
            transport system.

       Message-ID:
            A unique message identifier added by _\bp_\bo_\bs_\bt (8) if the  `-msgid'
            flag is set.

       Subject:

  [mh.6]                           MH.6.7                      UCI version









  MH-MAIL(5)                       -118-                        MH-MAIL(5)


            Sender's commentary.  It is displayed by _\bs_\bc_\ba_\bn (1).

       In-Reply-To:
            A commentary line added by _\br_\be_\bp_\bl (1) when replying  to  a  mes-
            sage.

       Resent-Date:
            Added when redistributing a message by _\bp_\bo_\bs_\bt (8).

       Resent-From:
            Added when redistributing a message by _\bp_\bo_\bs_\bt (8).

       Resent-To:
            New recipients for a message resent by _\bd_\bi_\bs_\bt (1).

       Resent-cc:
            Still more recipients.  See "cc:" and "Resent-To:".

       Resent-Bcc:
            Even more recipients.  See "Bcc:" and "Resent-To:".

       Resent-Fcc:
            Copy  resent  message  into  a   folder.    See   "Fcc:"   and
            "Resent-To:".

       Resent-Message-Id:
            A unique identifier glued on by _\bp_\bo_\bs_\bt (8) if the `-msgid'  flag
            is set.  See "Message-Id:" and "Resent-To:".

       Resent:
            Annotation for _\bd_\bi_\bs_\bt (1) under the `-annotate' option.

       Forwarded:
            Annotation for _\bf_\bo_\br_\bw (1) under the `-annotate' option.

       Replied:
            Annotation for _\br_\be_\bp_\bl (1) under the `-annotate' option.


  _\bF_\bi_\bl_\be_\bs
       /usr/spool/mail/$USER               Location of mail drop


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       None


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       _\bS_\bt_\ba_\bn_\bd_\ba_\br_\bd _\bf_\bo_\br  _\bt_\bh_\be  _\bF_\bo_\br_\bm_\ba_\bt  _\bo_\bf  _\bA_\bR_\bP_\bA  _\bI_\bn_\bt_\be_\br_\bn_\be_\bt  _\bT_\be_\bx_\bt  _\bM_\be_\bs_\bs_\ba_\bg_\be_\bs  (aka
       RFC-822)

\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MH-MAIL(5)                       -119-                        MH-MAIL(5)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       None


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None













































\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MH-PROFILE(5)                    -120-                     MH-PROFILE(5)


  _\bN_\bA_\bM_\bE
        .mh_profile - user customization for MH message system

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       any _\bM_\bH command

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       Each user of _\bM_\bH is expected to have a file named ._\bm_\bh__\bp_\br_\bo_\bf_\bi_\bl_\be in his
       or her home directory.  This file contains a set of user parameters
       used by some or all of the _\bM_\bH family of programs.  Each line of the
       file is of the format

           _\bp_\br_\bo_\bf_\bi_\bl_\be-_\bc_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt: _\bv_\ba_\bl_\bu_\be

       The  possible  profile  components  are  exemplified  below.   Only
       `Path:'  is  mandatory.  The others are optional; some have default
       values if they are not present.  In the notation used below,  (pro-
       file,  default)  indicates  whether  the information is kept in the
       user's _\bM_\bH profile or _\bM_\bH context, and  indicates  what  the  default
       value is.

       Path: Mail
                 Locates _\bM_\bH transactions in directory  "Mail".   (profile,
                 no default)

       context: context
                 Declares the location of the _\bM_\bH  context  file,  see  the
                 HISTORY     section     below.      (profile,    default:
                 <mh-dir>/context)

       Current-Folder: inbox
                 Keeps  track  of  the  current  open  folder.   (context,
                 default: +inbox)

       Previous-Sequence: pseq
                 Names the sequences which should be defined as the `msgs'
                 or  `msg' argument given to the program.  If not present,
                 or empty, no sequences are defined.  Otherwise, for  each
                 name  given,  the  sequence is first zero'd and then each
                 message is added to the sequence.  (profile, no default)

       Sequence-Negation: not
                 Defines the string which, when  prefixed  to  a  sequence
                 name,  negates that sequence.  Hence, "notseen" means all
                 those messages that are not  a  member  of  the  sequence
                 "seen".  (profile, no default)

       Unseen-Sequence: unseen
                 Names the sequences which should be defined as those mes-
                 sages recently incorporated by _\bi_\bn_\bc.  _\bS_\bh_\bo_\bw knows to remove
                 messages from this sequence once it thinks they have been

  [mh.6]                           MH.6.7                      UCI version









  MH-PROFILE(5)                    -121-                     MH-PROFILE(5)


                 seen.   If  not  present,  or  empty,  no  sequences  are
                 defined.  Otherwise, for each name given, the sequence is
                 first  zero'd  and  then  each  message  is  added to the
                 sequence.  (profile, no default)

       mh-sequences: .mh_sequences
                 The name of the file in each folder which defines  public
                 sequences.  To disable the use of public sequences, leave
                 the  value  portion  of  this  entry  blank.    (profile,
                 default: .mh_sequences)

       atr-_\bs_\be_\bq-_\bf_\bo_\bl_\bd_\be_\br: 172 178-181 212
                 Keeps track of the private sequence  called  _\bs_\be_\bq  in  the
                 specified folder.  (context, no default)

       Editor: /usr/ucb/ex
                 Defines  editor  to  be  used  by   _\bc_\bo_\bm_\bp (1),   _\bd_\bi_\bs_\bt (1),
                 _\bf_\bo_\br_\bw (1), and _\br_\be_\bp_\bl (1).  (profile, default: prompter)

       Msg-Protect: 644
                 Defines octal protection bits  for  message  files.   See
                 _\bc_\bh_\bm_\bo_\bd (1)  for an explanation of the octal number.  (pro-
                 file, default: 0644)

       Folder-Protect: 711
                 Defines protection bits for  folder  directories.   (pro-
                 file, default: 0711)

       _\bp_\br_\bo_\bg_\br_\ba_\bm: default switches
                 Sets default switches to be used whenever the mh  program
                 _\bp_\br_\bo_\bg_\br_\ba_\bm  is invoked.  For example, one could override the
                 _\bE_\bd_\bi_\bt_\bo_\br: profile component when replying  to  messages  by
                 adding a component such as:
                         repl: -editor /bin/ed
                 (profile, no defaults)

       _\bl_\ba_\bs_\bt_\be_\bd_\bi_\bt_\bo_\br-next: nexteditor
                 Names "nexteditor" to be the default editor  after  using
                 "lasteditor".   This takes effect at "What now?" level in
                 _\bc_\bo_\bm_\bp, _\bd_\bi_\bs_\bt, _\bf_\bo_\br_\bw, and _\br_\be_\bp_\bl.  After editing the draft with
                 "lasteditor",  the  default editor is set to be "nextedi-
                 tor".  If the user types "edit" without any arguments  to
                 "What  now?",  then  "nexteditor"  is used.  (profile, no
                 default)

       bboards: system
                 Tells _\bb_\bb_\bc which BBoards you are interested in.  (profile,
                 default: system)

       Folder-Stack: _\bf_\bo_\bl_\bd_\be_\br_\bs
                 The contents of the folder-stack for the _\bf_\bo_\bl_\bd_\be_\br  command.
                 (context, no default)

  [mh.6]                           MH.6.7                      UCI version









  MH-PROFILE(5)                    -122-                     MH-PROFILE(5)


       mhe:
                 If present, tells _\bi_\bn_\bc to  compose  an  _\bM_\bH_\bE  auditfile  in
                 addition  to  its other tasks.  _\bM_\bH_\bE is Brian Reid's _\bE_\bm_\ba_\bc_\bs
                 front-end for _\bM_\bH.  An early version is supplied with  the
                 _\bm_\bh._\b6 distribution.  (profile, no default)

  Alternate-Mailboxes: mh@uci-750a, bug-mh*
                 Tells _\br_\be_\bp_\bl and _\bs_\bc_\ba_\bn which addresses are really yours.  In
                 this  way,  _\br_\be_\bp_\bl knows which addresses should be included
                 in the reply, and _\bs_\bc_\ba_\bn knows if the message  really  ori-
                 ginated  from  you.   Addresses  must  be  separated by a
                 comma, and the hostnames listed should be the  "official"
                 hostnames  for the mailboxes you indicate, as local nick-
                 names for hosts are not replaced with their official site
                 names.   For  each  address, if a host is not given, then
                 that address on any host is considered  to  be  you.   In
                 addition,  an asterisk (`*') may appear at either or both
                 ends of the mailbox and host to indicate wild-card match-
                 ing.  (profile, default: your user-id)

       Aliasfile: aliases
                 Indicates a default aliases file for _\ba_\bl_\bi, _\bw_\bh_\bo_\bm, and _\bs_\be_\bn_\bd.
                 This  may  be  used  instead of the `-alias file' switch.
                 (profile, no default)

       Draft-Folder: drafts
                 Indicates a default draft folder for  _\bc_\bo_\bm_\bp,  _\bd_\bi_\bs_\bt,  _\bf_\bo_\br_\bw,
                 and _\br_\be_\bp_\bl.  (profile, no default)

       digest-issue-_\bl_\bi_\bs_\bt: 1
                 Tells _\bf_\bo_\br_\bw the last issue of the last volume sent for the
                 digest _\bl_\bi_\bs_\bt.  (context, no default)

       digest-volume-_\bl_\bi_\bs_\bt: 1
                 Tells _\bf_\bo_\br_\bw the last volume  sent  for  the  digest  _\bl_\bi_\bs_\bt.
                 (context, no default)

       MailDrop: .mail
                 Tells _\bi_\bn_\bc your maildrop, if different from  the  default.
                 This  is  superceded  by the $MAILDROP envariable.  (pro-
                 file, default: /usr/spool/mail/$USER)

       Signature: RAND MH System (agent: Marshall Rose)
                 Tells _\bs_\be_\bn_\bd your mail signature.  This  is  superceded  by
                 the $SIGNATURE envariable.  On hosts where _\bM_\bH was config-
                 ured with the UCI option, if $SIGNATURE is  not  set  and
                 this   profile   entry   is   not   present,   the   file
                 $HOME/.signature is consulted.  Your  signature  will  be
                 added  to the address _\bs_\be_\bn_\bd puts in the "From:" header; do
                 not include an address in the signature text.   (profile,
                 no default)
\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MH-PROFILE(5)                    -123-                     MH-PROFILE(5)


       The following profile elements are  used  whenever  an  _\bM_\bH  program
       invokes  some  other program such as _\bm_\bo_\br_\be (1).  The ._\bm_\bh__\bp_\br_\bo_\bf_\bi_\bl_\be can
       be used to select alternate  programs  if  the  user  wishes.   The
       default values are given in the examples.

            fileproc:     /usr/local/refile
            incproc:      /usr/local/inc
            installproc:  /usr/local/lib/mh/install-mh
            lproc:        /usr/ucb/more
            mailproc:     /usr/local/mhmail
            mhlproc:      /usr/local/lib/mh/mhl
            moreproc:     /usr/ucb/more
            mshproc:      /usr/local/msh
            packproc:     /usr/local/packf
            postproc:     /usr/local/lib/mh/post
            rmmproc:      none
            rmfproc:      /usr/local/rmf
            sendproc:     /usr/local/send
            showproc:     /usr/ucb/more
            whatnowproc:  /usr/local/whatnow
            whomproc:     /usr/local/whom

       If you define the envariable $MH, you can specify a  profile  other
       than ._\bm_\bh__\bp_\br_\bo_\bf_\bi_\bl_\be to be read by the _\bM_\bH programs that you invoke.  If
       the value of $MH is not absolute, (i.e., does not begin with a / ),
       it  will  be  presumed to start from the current working directory.
       This is one of the very few exceptions  in  _\bM_\bH  where  non-absolute
       pathnames are not considered relative to the user's _\bM_\bH directory.

       Similarly, if you define the envariable $MHCONTEXT, you can specify
       a  context  other than the normal context file (as specified in the
       _\bM_\bH profile).  As always, unless the value of  $MHCONTEXT  is  abso-
       lute, it will be presumed to start from your _\bM_\bH directory.

       _\bM_\bH programs also support other envariables:

       $MAILDROP : tells _\bi_\bn_\bc the default maildrop
            This supercedes the "MailDrop:" profile entry.

       $SIGNATURE : tells _\bs_\be_\bn_\bd and _\bp_\bo_\bs_\bt your mail signature
            This supercedes the "Signature:" profile entry.

       $HOME : tells all _\bM_\bH programs your home directory

       $SHELL : tells _\bb_\bb_\bl the default shell to run

       $TERM : tells _\bM_\bH your terminal type
            The $TERMCAP envariable is  also  consulted.   In  particular,
            these  tells  _\bs_\bc_\ba_\bn and _\bm_\bh_\bl how to clear your terminal, and how
            many columns wide your terminal is.  They also  tell  _\bm_\bh_\bl  how
            many lines long your terminal screen is.
\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MH-PROFILE(5)                    -124-                     MH-PROFILE(5)


       $editalt : the alternate message
            This is set by _\bd_\bi_\bs_\bt and _\br_\be_\bp_\bl during edit sessions so  you  can
            peruse  the message being distributed or replied-to.  The mes-
            sage is also available  through  a  link  called  "@"  in  the
            current  directory  if  your current working directory and the
            folder the message lives in are on the same UNIX filesystem.

       $mhdraft : the path to the working draft
            This is set by _\bc_\bo_\bm_\bp, _\bd_\bi_\bs_\bt, _\bf_\bo_\br_\bw, and _\br_\be_\bp_\bl to  tell  the  _\bw_\bh_\ba_\bt_\b-
            _\bn_\bo_\bw_\bp_\br_\bo_\bc  which  file  to  ask "What now?" questions about.  In
            addition, _\bd_\bi_\bs_\bt, _\bf_\bo_\br_\bw, and _\br_\be_\bp_\bl set $mhfolder  if  appropriate.
            Further,  _\bd_\bi_\bs_\bt  and _\br_\be_\bp_\bl set $mhaltmsg to tell the _\bw_\bh_\ba_\bt_\bn_\bo_\bw_\bp_\br_\bo_\bc
            about an alternate message associated with the draft (the mes-
            sage  being  distributed or replied-to), and _\bd_\bi_\bs_\bt sets $mhdist
            to tell the _\bw_\bh_\ba_\bt_\bn_\bo_\bw_\bp_\br_\bo_\bc that message re-distribution is occur-
            ring.   Also,  $mheditor  is  set  to tell the _\bw_\bh_\ba_\bt_\bn_\bo_\bw_\bp_\br_\bo_\bc the
            user's choice of  editor  (unless  overridden  by  `-noedit').
            Similarly, $mhuse may be set by _\bc_\bo_\bm_\bp.  Finally, $mhmessages is
            set by _\bd_\bi_\bs_\bt, _\bf_\bo_\br_\bw, and _\br_\be_\bp_\bl if annotations are to occur (along
            with  $mhannotate,  and  $mhinplace).   It's  amazing  all the
            information that has to get passed via envariables to make the
            "What now?" interface look squeaky clean to the _\bM_\bH user, isn't
            it?  The reason for all this is that the _\bM_\bH  user  can  select
            _\ba_\bn_\by  program as the _\bw_\bh_\ba_\bt_\bn_\bo_\bw_\bp_\br_\bo_\bc, including one of the standard
            shells.  As a result, it's not possible  to  pass  information
            via an argument list.
            If the WHATNOW option was set during  _\bM_\bH  configuration  (type
            `-help'  to an _\bM_\bH command to find out), and if this envariable
            is set, if the commands _\br_\be_\bf_\bi_\bl_\be, _\bs_\be_\bn_\bd, _\bs_\bh_\bo_\bw, or  _\bw_\bh_\bo_\bm  are  not
            given  any  `msgs'  arguments, then they will default to using
            the file indicated by $mhdraft.  This is  useful  for  getting
            the default behavior supplied by the default _\bw_\bh_\ba_\bt_\bn_\bo_\bw_\bp_\br_\bo_\bc.

       $mhfolder : the folder containing the alternate message
            This is set by _\bd_\bi_\bs_\bt and _\br_\be_\bp_\bl during edit sessions so  you  can
            peruse  other  messages  in the current folder besides the one
            being distributed or replied-to.  The $mhfolder envariable  is
            also set by _\bs_\bh_\bo_\bw, _\bp_\br_\be_\bv, and _\bn_\be_\bx_\bt for use by _\bm_\bh_\bl.

       $MHBBRC :
            If you define  the  envariable  $MHBBRC,  you  can  specify  a
            BBoards  information  file other than ._\bb_\bb_\br_\bc to be read by _\bb_\bb_\bc.
            If the value of $MHBBRC is not absolute, (i.e., does not begin
            with  a  / ),  it  will  be presumed to start from the current
            working directory.

       $MHFD :
            If the OVERHEAD option was set during _\bM_\bH  configuration  (type
            `-help' to an _\bM_\bH command to find out), then if this envariable
            is set, _\bM_\bH considers it to be the number of a  file-descriptor
            which  is  opened, read-only to the _\bM_\bH profile.  Similarly, if
            the envariable $MHCONTEXTFD is set, this is the  number  of  a

  [mh.6]                           MH.6.7                      UCI version









  MH-PROFILE(5)                    -125-                     MH-PROFILE(5)


            file-descriptor  which  is opened read-only to the _\bM_\bH context.
            This feature of _\bM_\bH is experimental, and  is  used  to  examine
            possible  speed  improvements for _\bM_\bH startup.  Note that these
            envariables must be set and non-empty to enable this  feature.
            However,  if OVERHEAD is enabled during _\bM_\bH configuration, then
            when _\bM_\bH programs call other _\bM_\bH programs, this scheme is  used.
            These file-descriptors are not closed throughout the execution
            of the _\bM_\bH program, so children may  take  advantage  of  this.
            This approach is thought to be completely safe and does result
            in some performance enhancements.


  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile
       or $MH                              Rather than the standard profile
       <mh-dir>/context                    The user context
       or $CONTEXT                         Rather than the standard context
       <folder>/.mh_sequences              Public sequences for <folder>


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       All


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       mh(1), environ(5)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       None


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       All

















\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MH-PROFILE(5)                    -126-                     MH-PROFILE(5)


  _\bH_\bi_\bs_\bt_\bo_\br_\by
       In previous versions of _\bM_\bH, the current-message value of a writable
       folder  was  kept  in a file called "cur" in the folder itself.  In
       _\bm_\bh._\b3, the ._\bm_\bh__\bp_\br_\bo_\bf_\bi_\bl_\be contained the current-message values for  all
       folders, regardless of their writability.

       In all versions of _\bM_\bH since _\bm_\bh._\b4,  the  ._\bm_\bh__\bp_\br_\bo_\bf_\bi_\bl_\be  contains  only
       static  information, which _\bM_\bH programs will NOT update.  Changes in
       context are made to the _\bc_\bo_\bn_\bt_\be_\bx_\bt file kept in the users MH  _\bd_\bi_\br_\be_\bc_\bt_\bo-
       _\br_\by.  This includes, but is not limited to: the "Current-Folder" en-
       try and all private sequence information.  Public sequence informa-
       tion is kept in a file called ._\bm_\bh__\bs_\be_\bq_\bu_\be_\bn_\bc_\be_\bs in each folder.

       To convert from the format used in releases of _\bM_\bH prior to the for-
       mat used in the _\bm_\bh._\b4 release, _\bi_\bn_\bs_\bt_\ba_\bl_\bl-_\bm_\bh should be invoked with the
       `-compat' switch.  This generally happens automatically on _\bM_\bH  sys-
       tems generated with the "COMPAT" option during _\bM_\bH configuration.

       The ._\bm_\bh__\bp_\br_\bo_\bf_\bi_\bl_\be may override the  path  of  the  _\bc_\bo_\bn_\bt_\be_\bx_\bt  file,  by
       specifying  a "context" entry (this must be in lower-case).  If the
       entry is not absolute (does not start with a / ), then it is inter-
       preted  relative  to the user's _\bM_\bH directory.  As a result, you can
       actually have more than one set of private sequences by using  dif-
       ferent context files.



























\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MH-PROFILE(5)                    -127-                     MH-PROFILE(5)


  _\bB_\bu_\bg_\bs
       The shell quoting conventions are not available in the .mh_profile.
       Each token is separated by whitespace.

       There is some question as to  what  kind  of  arguments  should  be
       placed  in  the  profile  as  options.  In order to provide a clear
       answer, recall command line semantics of all _\bM_\bH programs: conflict-
       ing  switches  (e.g., `-header and `-noheader') may occur more than
       one time on the command line, with the last switch  taking  effect.
       Other  arguments, such as message sequences, filenames and folders,
       are always remembered on the invocation line and are not superseded
       by  following  arguments  of  the  same type.  Hence, it is safe to
       place only switches (and their arguments) in the profile.

       If one finds that an _\bM_\bH program is being invoked  again  and  again
       with  the same arguments, and those arguments aren't switches, then
       there are a few possible solutions to this problem.  The  first  is
       to  create a (soft) link in your $_\bH_\bO_\bM_\bE/_\bb_\bi_\bn directory to the _\bM_\bH pro-
       gram of your choice.  By giving this link a different name, you can
       create  a new entry in your profile and use an alternate set of de-
       faults for the _\bM_\bH command.  Similarly, you  could  create  a  small
       shell script which called the _\bM_\bH program of your choice with an al-
       ternate set of invocation line switches (using links and an  alter-
       nate profile entry is preferable to this solution).

       Finally, the _\bc_\bs_\bh user could create an alias for the command of  the
       form:

            alias cmd 'cmd arg1 arg2 ...'

       In this way, the user can avoid lengthy type-in to the  shell,  and
       still  give  _\bM_\bH commands safely.  (Recall that some _\bM_\bH commands in-
       voke others, and that in all cases, the profile  is  read,  meaning
       that aliases are disregarded beyond an initial command invocation)

















\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MH-SEQUENCE(5)                   -128-                    MH-SEQUENCE(5)


  _\bN_\bA_\bM_\bE
       mh-sequence - sequence specification for MH message system

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       most _\bM_\bH commands

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       Most _\bM_\bH commands accept a  `msg'  or  `msgs'  specification,  where
       `msg'  indicates  one message and `msgs' indicates one or more mes-
       sages.  To designate a message,  you  may  use  either  its  number
       (e.g., 1, 10, 234) or one of these "reserved" message names:

            _\bN_\ba_\bm_\be      _\bD_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn
            first     the first message in the folder
            last      the last message in the folder
            cur       the most recently accessed message
            prev      the message numerically preceding "cur"
            next      the message numerically following "cur"

       In commands that take a `msg' argument, the default is "cur".  As a
       shorthand, "." is equivalent to "cur".

       For example: In a folder containing five messages numbered  5,  10,
       94,  177  and 325, "first" is 5 and "last" is 325.  If "cur" is 94,
       then "prev" is 10 and "next" is 177.

       The word `msgs' indicates that one or more messages may  be  speci-
       fied.   Such a specification consists of one message designation or
       of several message designations separated  by  spaces.   A  message
       designation  consists either of a message name as defined above, or
       a message range.

       A message range is specified as "name1-name2"  or  "name:n",  where
       `name',  `name1'  and  `name2'  are  message  names,  and `n' is an
       integer.

       The specification "name1-name2" designates  all  currently-existing
       messages from `name1' to `name2' inclusive.  The message name "all"
       is a shorthand for the message range "first-last".

       The specification "name:n" designates up to  `n'  messages.   These
       messages  start with `name' if `name' is a message number or one of
       the reserved names "first" "cur", or "next", The messages end  with
       `name'  if  `name'  is "prev" or "last".  The interpretation of `n'
       may be overridden by preceding `n' with a plus or minus sign;  `+n'
       always  means  up  to  `n'  messages starting with `name', and `-n'
       always means up to `n' messages ending with `name'.

       In commands which accept a `msgs' argument, the default  is  either
       "cur"  or  "all",  depending  on  which makes more sense.  Repeated
       specifications of the same message have the same effect as a single

  [mh.6]                           MH.6.7                      UCI version









  MH-SEQUENCE(5)                   -129-                    MH-SEQUENCE(5)


       specification of the message.


    _\bU_\bs_\be_\br-_\bD_\be_\bf_\bi_\bn_\be_\bd _\bM_\be_\bs_\bs_\ba_\bg_\be _\bS_\be_\bq_\bu_\be_\bn_\bc_\be_\bs

       In addition to the "reserved"  (pre-defined)  message  names  given
       above,  _\bM_\bH  supports  user-defined  sequence  names.   User-defined
       sequences allow the _\bM_\bH 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.

       The name used to denote a  message  sequence  must  consist  of  an
       alphabetic  character followed by zero or more alphanumeric charac-
       ters, and can not be one of the  "reserved"  message  names  above.
       After  defining  a  sequence, it can be used wherever an _\bM_\bH command
       expects a `msg' or `msgs' argument.

       Some  forms  of  message  ranges  are  allowed  with   user-defined
       sequences.   The  specification "name:n" may be used, and it desig-
       nates up to the first `n' messages (or last `n' messages for  `-n')
       which are elements of the user-defined sequence `name'.

       The specifications "name:next" and "name:prev" may  also  be  used,
       and  they  designate  the next or previous message (relative to the
       current message) which is an element of the  user-defined  sequence
       `name'.   The  specificaitions  "name:first"  and  "name:last"  are
       equivalent to "name:1" and "name:-1", respectively.  The specifica-
       tion  "name:cur" is not allowed (use just "cur" instead).  The syn-
       tax of these message range specifcations is subject  to  change  in
       the future.

       User-defined sequence names are specific to each folder.  They  are
       defined using the _\bp_\bi_\bc_\bk and _\bm_\ba_\br_\bk commands.


    _\bP_\bu_\bb_\bl_\bi_\bc _\ba_\bn_\bd _\bP_\br_\bi_\bv_\ba_\bt_\be _\bU_\bs_\be_\br-_\bD_\be_\bf_\bi_\bn_\be_\bd _\bS_\be_\bq_\bu_\be_\bn_\bc_\be_\bs

       There are two varieties of sequences: _\bp_\bu_\bb_\bl_\bi_\bc sequences and  _\bp_\br_\bi_\bv_\ba_\bt_\be
       sequences.   _\bP_\bu_\bb_\bl_\bi_\bc  sequences of a folder are accessible to any _\bM_\bH
       user that can read that folder and are kept  in  the  .mh_sequences
       file  in  the folder.  _\bP_\br_\bi_\bv_\ba_\bt_\be sequences are accessible only to the
       _\bM_\bH user that defined those sequences and are kept in the user's  _\bM_\bH
       context file.  By default, _\bp_\bi_\bc_\bk and _\bm_\ba_\br_\bk create _\bp_\bu_\bb_\bl_\bi_\bc sequences if
       the folder for which the sequences are being defined is writable by
       the  _\bM_\bH  user.  Otherwise, _\bp_\br_\bi_\bv_\ba_\bt_\be sequences are created.  This can
       be overridden with the `-public' and `-private' switches to _\bm_\ba_\br_\bk.


    _\bS_\be_\bq_\bu_\be_\bn_\bc_\be _\bN_\be_\bg_\ba_\bt_\bi_\bo_\bn

       _\bM_\bH provides the ability to select all messages not  elements  of  a
       user-defined  sequence.   To  do  this,  the user should define the

  [mh.6]                           MH.6.7                      UCI version









  MH-SEQUENCE(5)                   -130-                    MH-SEQUENCE(5)


       entry "Sequence-Negation" in the _\bM_\bH profile file; its value may  be
       any  string.  This string is then used to preface an existing user-
       defined sequence name.  This specification  then  refers  to  those
       messages not elements of the specified sequence name.  For example,
       if the profile entry is:

            Sequence-Negation: not

       then anytime an _\bM_\bH command is given "notfoo" as a `msg'  or  `msgs'
       argument, it would substitute all messages that are not elements of
       the sequence "foo".

       Obviously, the user should beware of defining sequences with  names
       that begin with the value of the "Sequence-Negation" profile entry.


    _\bT_\bh_\be _\bP_\br_\be_\bv_\bi_\bo_\bu_\bs _\bS_\be_\bq_\bu_\be_\bn_\bc_\be

       _\bM_\bH provides the ability to remember the `msgs'  or  `msg'  argument
       last  given to an _\bM_\bH command.  The entry "Previous-Sequence" should
       be defined in the _\bM_\bH profile; its value should be a  sequence  name
       or  multiple  sequence names separated by spaces.  If this entry is
       defined, when when an _\bM_\bH  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

            Previous-Sequence: pseq

       directs any _\bM_\bH command that accepts a `msg' or `msgs'  argument  to
       define the sequence "pseq" as those messages when it finishes.

       Note:  there  can  be  a   performance   penalty   in   using   the
       "Previous-Sequence"  facility.  If it is used, all _\bM_\bH programs have
       to write the sequence information to the .mh_sequences file for the
       folder  each  time  they  run.   If the "Previous-Sequence" profile
       entry is not included,  only  _\bp_\bi_\bc_\bk  and  _\bm_\ba_\br_\bk  will  write  to  the
       .mh_sequences file.


    _\bT_\bh_\be _\bU_\bn_\bs_\be_\be_\bn _\bS_\be_\bq_\bu_\be_\bn_\bc_\be

       Finally, some users like to indicate messages which have  not  been
       previously seen by them.  Both _\bi_\bn_\bc and _\bs_\bh_\bo_\bw honor the profile entry
       "Unseen-Sequence" to support this  activity.   This  entry  in  the
       .mh_profile  should  be  defined  as  one  or  more  sequence names
       separated by spaces.  If there is a value for "Unseen-Sequence"  in
       the profile, then whenever _\bi_\bn_\bc places new messages in a folder, the
       new messages will also be added to the  sequence(s)  named  in  the
       value of this entry.  Hence, a profile entry of

            Unseen-Sequence: unseen
\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  MH-SEQUENCE(5)                   -131-                    MH-SEQUENCE(5)


       directs _\bi_\bn_\bc to add new messages to the sequence  "unseen".   Unlike
       the  behavior of the "Previous-Sequence" entry in the profile, how-
       ever, the sequence(s) will not be zeroed by _\bi_\bn_\bc.

       Similarly, whenever _\bs_\bh_\bo_\bw (or _\bn_\be_\bx_\bt or _\bp_\br_\be_\bv) displays a message, that
       message   will   be   removed  from  any  sequences  named  by  the
       "Unseen-Sequence" entry in the profile.


  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile
       <mh-dir>/context                    The user context
       <folder>/.mh_sequences              Public sequences for <folder>


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Sequence-Negation:   To designate messages not in a sequence
       Previous-Sequence:   The last message specification given
       Unseen-Sequence:     Those messages not yet seen by the user


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       mh(1), mark(1), pick(1), mh-profile(5)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       None


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       All


  _\bB_\bu_\bg_\bs
       User-defined sequences are stored in the .mh_sequences  file  as  a
       series  of  message specifications separated by spaces.  If a user-
       defined sequence contains too many  individual  message  specifica-
       tions,  that line in the file may become too long for _\bM_\bH to handle.
       This will generate the error message ".mh_sequences is poorly  for-
       matted".   You'll  have  to edit the file by hand to remove the of-
       fending line.

       This can happen to users who define the  "Previous-Sequence"  entry
       in  the  _\bM_\bH profile and have a folder containing many messages with
       gaps in the numbering.  A workaround for large folders is to minim-
       ize numbering gaps by using "folder -pack" often.





\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  AP(8)                            -132-                             AP(8)


  _\bN_\bA_\bM_\bE
       ap - parse addresses 822-style

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       /usr/local/lib/mh/ap [-form formatfile] [-format string]
            [-normalize] [-nonormalize] [-width columns] addrs ...
            [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bA_\bp is a program that parses addresses according to the ARPA  Inter-
       net  standard.   It also understands many non-standard formats.  It
       is useful for seeing how _\bM_\bH will interpret an address.

       The _\ba_\bp program treats each argument as one or more  addresses,  and
       prints  those  addresses out in the official 822-format.  Hence, it
       is usually best to enclose each argument in double-quotes  for  the
       shell.

       To override the output format used by _\ba_\bp, the  `-format string'  or
       `-format file'  switches  are used.  This permits individual fields
       of the address to be extracted with ease.  The string is  simply  a
       format   stringand   thefile   is   simply   a  format  file.   See
       _\bm_\bh-_\bf_\bo_\br_\bm_\ba_\bt (5) for the details.

       In addition to the standard escapes, _\ba_\bp also recognizes the follow-
       ing additional escape:

       _\bE_\bs_\bc_\ba_\bp_\be  _\bR_\be_\bt_\bu_\br_\bn_\bs  _\bD_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn
       error   string   A diagnostic if the parse failed

       If the `-normalize' switch is given, _\ba_\bp will try to track down  the
       official hostname of the address.

       Here is the default format string used by _\ba_\bp:

            %<{error}%{error}: %{text}%|%(putstr(proper{text}))%>

       which says that if an error was detected, print the error,  a  `:',
       and  the address in error.  Otherwise, output the 822-proper format
       of the address.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile
       /usr/local/lib/mh/mtstailor         tailor file


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       None


\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  AP(8)                            -133-                             AP(8)


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       dp(8),
       _\bS_\bt_\ba_\bn_\bd_\ba_\br_\bd _\bf_\bo_\br  _\bt_\bh_\be  _\bF_\bo_\br_\bm_\ba_\bt  _\bo_\bf  _\bA_\bR_\bP_\bA  _\bI_\bn_\bt_\be_\br_\bn_\be_\bt  _\bT_\be_\bx_\bt  _\bM_\be_\bs_\bs_\ba_\bg_\be_\bs  (aka
       RFC-822)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `-format' defaults as described above
       `-normalize'
       `-width' defaults to the width of the terminal


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None


  _\bB_\bu_\bg_\bs
       The argument to the `-format' switch must be interpreted as a  sin-
       gle token by the shell that invokes _\ba_\bp.  Therefore, one must usual-
       ly place the argument to this switch inside double-quotes.

       On hosts where _\bM_\bH was configured  with  the  BERK  option,  address
       parsing is not enabled.




























\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  CONFLICT(8)                      -134-                       CONFLICT(8)


  _\bN_\bA_\bM_\bE
       conflict - search for alias/password conflicts

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       /usr/local/lib/mh/conflict [-mail name] [-search directory]
            [aliasfiles...] [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bC_\bo_\bn_\bf_\bl_\bi_\bc_\bt is a program that checks to see if the  interface  between
       _\bM_\bH and transport system is in good shape

       _\bC_\bo_\bn_\bf_\bl_\bi_\bc_\bt also checks for maildrops in /usr/spool/mail which do  not
       belong  to  a  valid user.  It assumes that no user name will start
       with `.', and thus ignores files  in  /usr/spool/mail  which  begin
       with  `.'.   It also checks for entries in the _\bg_\br_\bo_\bu_\bp (5) file which
       do not belong to a valid user, and for users  who  do  not  have  a
       valid  group  number.   In  addition duplicate users and groups are
       noted.

       If the `-mail name' switch is used, then the results will  be  sent
       to  the  specified  _\bn_\ba_\bm_\be.   Otherwise,  the results are sent to the
       standard output.

       The `-search directory' switch can be used  to  search  directories
       other  than /usr/spool/mail and to report anomalies in those direc-
       tories.  The `-search directory' switch can appear  more  than  one
       time in an invocation to _\bc_\bo_\bn_\bf_\bl_\bi_\bc_\bt.

       _\bC_\bo_\bn_\bf_\bl_\bi_\bc_\bt should be run under  _\bc_\br_\bo_\bn (8), or whenever system account-
       ing takes place.

  _\bF_\bi_\bl_\be_\bs
       /usr/local/lib/mh/mtstailor         tailor file
       /etc/passwd                         List of users
       /etc/group                          List of groups
       /usr/local/mhmail                   Program to send mail
       /usr/spool/mail/                    Directory of mail drop


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       None


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       mh-alias(5)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `aliasfiles' defaults to /usr/local/lib/mh/MailAliases

\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  CONFLICT(8)                      -135-                       CONFLICT(8)


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None

















































\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  DP(8)                            -136-                             DP(8)


  _\bN_\bA_\bM_\bE
       dp - parse dates 822-style

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       /usr/local/lib/mh/dp [-form formatfile] [-format string]
            [-width columns] dates ...  [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bD_\bp is a program that parses dates according to  the  ARPA  Internet
       standard.   It  also understands many non-standard formats, such as
       those  produced  by  TOPS-20  sites  and  some  UNIX  sites   using
       _\bc_\bt_\bi_\bm_\be (3).  It is useful for seeing how _\bM_\bH will interpret a date.

       The _\bd_\bp program treats each argument as a single  date,  and  prints
       the date out in the official 822-format.  Hence, it is usually best
       to enclose each argument in double-quotes for the shell.

       To override the output format used by _\bd_\bp, the  `-format string'  or
       `-format file'  switches  are used.  This permits individual fields
       of the address to be extracted with ease.  The string is  simply  a
       format   stringand   thefile   is   simply   a  format  file.   See
       _\bm_\bh-_\bf_\bo_\br_\bm_\ba_\bt (5) for the details.

       Here is the default format string used by _\bd_\bp:

            %<(nodate{text})error: %{text}%|%(putstr(pretty{text}))%>

       which says that if an error was detected, print the error,  a  `:',
       and  the date in error.  Otherwise, output the 822-proper format of
       the date.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       None


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       ap(8)
       _\bS_\bt_\ba_\bn_\bd_\ba_\br_\bd _\bf_\bo_\br  _\bt_\bh_\be  _\bF_\bo_\br_\bm_\ba_\bt  _\bo_\bf  _\bA_\bR_\bP_\bA  _\bI_\bn_\bt_\be_\br_\bn_\be_\bt  _\bT_\be_\bx_\bt  _\bM_\be_\bs_\bs_\ba_\bg_\be_\bs  (aka
       RFC-822)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `-format' default as described above
       `-width' default to the width of the terminal


\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  DP(8)                            -137-                             DP(8)


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None


  _\bB_\bu_\bg_\bs
       The argument to the `-format' switch must be interpreted as a  sin-
       gle token by the shell that invokes _\bd_\bp.  Therefore, one must usual-
       ly place the argument to this switch inside double-quotes.











































\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  INSTALL-MH(8)                    -138-                     INSTALL-MH(8)


  _\bN_\bA_\bM_\bE
       install-mh - initialize the MH environment

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       /usr/local/lib/mh/install-mh [-auto] [-compat]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       When a user runs any _\bM_\bH program for the  first  time,  the  program
       will  invoke _\bi_\bn_\bs_\bt_\ba_\bl_\bl-_\bm_\bh (with the `-auto' switch) to query the user
       for the initial _\bM_\bH environment.  The user does NOT invoke this pro-
       gram  directly.   The  user  is asked for the name of the directory
       that will be designated as the user's _\bM_\bH directory.  If this direc-
       tory  does  not  exist,  the user is asked if it should be created.
       Normally, this directory should be under the user's home directory,
       and  has  the  default name of Mail/.  After _\bi_\bn_\bs_\bt_\ba_\bl_\bl-_\bm_\bh has written
       the initial .mh_profile for the user, control returns to the origi-
       nal _\bM_\bH program.

       As with all  _\bM_\bH  commands,  _\bi_\bn_\bs_\bt_\ba_\bl_\bl-_\bm_\bh  first  consults  the  $HOME
       envariable to determine the user's home directory.  If $HOME is not
       set, then the /_\be_\bt_\bc/_\bp_\ba_\bs_\bs_\bw_\bd file is consulted.

       When converting from _\bm_\bh._\b3  to  _\bm_\bh._\b4,  _\bi_\bn_\bs_\bt_\ba_\bl_\bl-_\bm_\bh  is  automatically
       invoked with the `-compat' switch.

  _\bF_\bi_\bl_\be_\bs
       $HOME/.mh_profile                   The user profile


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       Path:                To set the user's MH directory


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       With `-auto', the current folder is changed to "inbox".















\e9
\e9  [mh.6]                           MH.6.7                      UCI version









  POST(8)                          -139-                           POST(8)


  _\bN_\bA_\bM_\bE
       post - deliver a message

  _\bS_\bY_\bN_\bO_\bP_\bS_\bI_\bS
       /usr/local/lib/mh/post [-alias aliasfile] [-filter filterfile]
            [-nofilter] [-format] [-noformat] [-msgid] [-nomsgid]
            [-verbose] [-noverbose] [-watch] [-nowatch] [-width columns]
            file [-help]

  _\bD_\bE_\bS_\bC_\bR_\bI_\bP_\bT_\bI_\bO_\bN

       _\bP_\bo_\bs_\bt is the program called by _\bs_\be_\bn_\bd (1) to deliver  the  message  in
       _\bf_\bi_\bl_\be  to  local  and  remote  users.  In fact, all of the functions
       attributed to _\bs_\be_\bn_\bd on its manual page are performed by  _\bp_\bo_\bs_\bt,  with
       _\bs_\be_\bn_\bd  acting as a relatively simple preprocessor.  Thus, it is _\bp_\bo_\bs_\bt
       which parses the various header fields,  appends  From:  and  Date:
       lines, and interacts with the _\bM_\bM_\bD_\bF transport system.  _\bP_\bo_\bs_\bt will not
       normally be called directly by the user.

       _\bP_\bo_\bs_\bt searches the "To:", "cc:", "Bcc:", "Fcc:",  and  "Resent-xxx:"
       header  lines  of  the specified message for destination addresses,
       checks these addresses for validity, and formats them so as to con-
       form  to  ARPAnet  Internet  Message  Format  protocol,  unless the
       `-noformat' flag is set.  This will normally cause "@_\bl_\bo_\bc_\ba_\bl-_\bs_\bi_\bt_\be" to
       be appended to each local destination address, as well as any local
       return addresses. The `-width columns' switch can be used to  indi-
       cate  the  preferred  length  of the header components that contain
       addresses.

       If a "Bcc:" field is encountered, its addresses will  be  used  for
       delivery,  and  the  "Bcc:"  field will be removed from the message
       sent to sighted recipients.  The blind recipients will  receive  an
       entirely  new  message  with a minimal set of headers.  Included in
       the body of the message will be a copy of the message sent  to  the
       sighted  recipients.   If  `-filter filterfile'  is specified, then
       this copy is filtered (re-formatted) prior to  being  sent  to  the
       blind recipients.

       The `-alias aliasfile' switch can be used to specify  a  file  that
       post  should  take  aliases from.  More than one file can be speci-
       fied, each being preceded with `-alias'.  In any event, the primary
       alias file is read first.

       The   `-msgid'   switch   indicates   that   a   "Message-ID:"   or
       "Resent-Message-ID:" field should be added to the header.

       The `-verbose' switch indicates that the user should be informed of
       each step of the posting/filing process.

       The `-watch' switch indicates that the user would like to watch the
       transport  system's handling of the message (e.g., local and "fast"
       delivery).

  [mh.6]                           MH.6.7                      UCI version









  POST(8)                          -140-                           POST(8)


       _\bP_\bo_\bs_\bt consults the envariable $SIGNATURE to determine  the  sender's
       personal name in constructing the "From:" line of the message.

  _\bF_\bi_\bl_\be_\bs
       /usr/local/lib/mh/mtstailor         tailor file
       /usr/local/refile                   Program to process Fcc:s
       /usr/local/lib/mh/mhl               Program to process Bcc:s
       /usr/local/lib/mh/MailAliases       Primary alias file


  _\bP_\br_\bo_\bf_\bi_\bl_\be _\bC_\bo_\bm_\bp_\bo_\bn_\be_\bn_\bt_\bs
       _\bp_\bo_\bs_\bt does NOT consult the user's .mh_profile


  _\bS_\be_\be _\bA_\bl_\bs_\bo
       _\bS_\bt_\ba_\bn_\bd_\ba_\br_\bd _\bf_\bo_\br  _\bt_\bh_\be  _\bF_\bo_\br_\bm_\ba_\bt  _\bo_\bf  _\bA_\bR_\bP_\bA  _\bI_\bn_\bt_\be_\br_\bn_\be_\bt  _\bT_\be_\bx_\bt  _\bM_\be_\bs_\bs_\ba_\bg_\be_\bs  (aka
       RFC-822),
       mhmail(1), send(1), mh-mail(5), mh-alias(5)


  _\bD_\be_\bf_\ba_\bu_\bl_\bt_\bs
       `-alias /usr/local/lib/mh/MailAliases'
       `-format'
       `-nomsgid'
       `-noverbose'
       `-width 72'
       `-nofilter'


  _\bC_\bo_\bn_\bt_\be_\bx_\bt
       None


  _\bB_\bu_\bg_\bs
       "Reply-To:" fields are allowed to have groups in them according  to
       the 822 specification, but _\bp_\bo_\bs_\bt won't let you use them.















\e9
\e9       [mh.6]                           MH.6.7                      UCI version












                                _\b5. _\bR_\bE_\bP_\bO_\bR_\bT_\bI_\bN_\bG _\bP_\bR_\bO_\bB_\bL_\bE_\bM_\bS



\e9
            If problems are encountered with an _\bM_\bH program, the problems should
       be  reported  to the local maintainers of _\bM_\bH.  When doing this, the name
       of the program should be reported, along with  the  version  information
       for  the  program.   To  find out what version of an _\bM_\bH program is being
       run, invoke the program with the `-help' switch.  In addition to listing
       the  syntax of the command, the program will list information pertaining
       to its version.  This information includes the version of _\bM_\bH,  the  host
       it was generated on, and the date the program was loaded.  A second line
       of information, found on versions of _\bM_\bH after #5.380 include  _\bM_\bH  confi-
       guration options.  For example,

            version: MH 6.1 #1[UCI] (nrtc-gremlin) of Wed Nov  6  01:13:53  PST
            1985
            options: [BSD42] [MHE] [NETWORK] [SENDMTS] [MMDFII] [SMTP] [POP]

       The `6.1 #1[UCI]' indicates that the program is from the UCI  _\bm_\bh._\b6  ver-
       sion  of  _\bM_\bH.   The  program was generated on the host `nrtc-gremlin' on
       `Wed Nov  6 01:13:53 PST 1985'.  It's usually a good idea  to  send  the
       output of the `-help' switch along with your report.

       If there is no local _\bM_\bH maintainer, try the  address  Bug-MH.   If  that
       fails, use the Internet mailbox Bug-MH@ICS.UCI.EDU.

























\e9                                        -141-












                                 _\b6. _\bA_\bD_\bV_\bA_\bN_\bC_\bE_\bD _\bF_\bE_\bA_\bT_\bU_\bR_\bE_\bS



\e9
            This section describes some  features  of  _\bM_\bH  that  were  included
       strictly for advanced _\bM_\bH users.  These capabilities permit _\bM_\bH to exhibit
       more powerful behavior for the seasoned _\bM_\bH users.


\e9       _\bU_\bS_\bE_\bR-_\bD_\bE_\bF_\bI_\bN_\bE_\bD _\bS_\bE_\bQ_\bU_\bE_\bN_\bC_\bE_\bS

            User-defined sequences allow the _\bM_\bH 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.  The
       user  may choose any name for a message sequence, as long as it consists
       of alphanumeric characters and does not conflict with  the  standard  _\bM_\bH
       reserved message names (e.g., "first", etc).  After defining a sequence,
       it can be used wherever an _\bM_\bH command expects a `msg'  or  `msgs'  argu-
       ment.

            A restricted form of message ranges are allowed  with  user-defined
       sequences.  The  form  "name:n",  specifies up to the first `n' messages
       which are part of the user-defined sequence `name'.  A leading plus sign
       is  allowed on `n', but is ignored.  The interpretation of n is overrid-
       den if n is preceded by a minus sign; `-n' always means up to  the  last
       `n' messages which are part of the sequence `name'.

            Although all _\bM_\bH commands expand user-defined sequences as appropri-
       ate, there are two commands that allow the user to define and manipulate
       them: _\bp_\bi_\bc_\bk and _\bm_\ba_\br_\bk.

       _\bP_\bi_\bc_\bk _\ba_\bn_\bd _\bU_\bs_\be_\br-_\bD_\be_\bf_\bi_\bn_\be_\bd _\bS_\be_\bq_\bu_\be_\bn_\bc_\be_\bs

            Most users of _\bM_\bH will use user-defined sequences only with the _\bp_\bi_\bc_\bk
       command.  By giving the `-sequence name' switch to _\bp_\bi_\bc_\bk (which can occur
       more than once on the command line), each sequence named is  defined  as
       those  messages  which _\bp_\bi_\bc_\bk matched according the the selection criteria
       it was given.  Hence,

            pick -from frated -seq fred

       finds all those messages in the current folder which were from "frated",
       creates  a  sequence  called "fred", and then adds them to the sequence.
       The user could then invoke

            scan fred

       to get a _\bs_\bc_\ba_\bn listing of those messages.  Note  that  by  default,  _\bp_\bi_\bc_\bk
       creates  the named sequences before it adds the selected messages to the
       sequence.  Hence, if the named sequence already existed, the sequence is

                                        -142-









                                        -143-


       destroyed  prior  to  being  re-defined (nothing happens to the messages
       that were a part of this sequence, they simply cease to  be  members  of
       that  sequence).   By  using  the `-nozero' switch, this behavior can be
       inhibited, as in

            pick -from frated -seq sgroup
            pick -from fear -seq sgroup -nozero
            pick -from freida -seq sgroup -nozero

       finds all those messages in the current folder which were from "frated",
       "fear", or "freida", and defines the sequence called "sgroup" as exactly
       those messages.  These operations amounted to an "inclusive-or" of three
       selection  criteria, using _\bp_\bi_\bc_\bk, one can also generate the "and" of some
       selection criteria as well:

            pick -from frated -seq fred
            pick -before friday -seq fred fred

       This example defines the sequence called "fred" as  exactly  those  mes-
       sages from "frated" that were dated prior to "friday".[1]

            _\bP_\bi_\bc_\bk is normally used as a back-quoted command, for example,

            scan `pick -from postmaster`

       Now suppose that the user decides that another command should be issued,
       using   exactly   those   messages.    Since,   _\bp_\bi_\bc_\bk   wasn't   given  a
       `-sequence name' argument in this example, the user would end-up  typing
       the entire back-quoted command again.  A simpler way is to add a default
       sequence name to the .mh_profile.  For example,

            pick: -seq select -list

       will tell _\bp_\bi_\bc_\bk to always define the sequence "select" whenever it's run.
       The  `-list'  is necessary since the `-sequence name' switch sets `-nol-
       ist' whenever the former is  encountered.   Hence,  this  profile  entry


\e9          [1]  Of  course, it is much easier to simply use the built-in boolean
       operation of _\bp_\bi_\bc_\bk to get the desired results:

            pick -from frated -or -from fear -or -from freida -seq sgroup

       and

            pick -from frated -and -before friday -seq fred

       do exactly the same thing as the five commands listed above.  Hence, the
       `-nozero'  option  to  _\bp_\bi_\bc_\bk  is  only  useful to manipulate existing se-
       quences.


\e9









                                        -144-


       makes _\bp_\bi_\bc_\bk define the "select" sequence and otherwise behave exactly  as
       if there was no profile entry at all.

       _\bM_\ba_\br_\bk _\ba_\bn_\bd _\bU_\bs_\be_\br-_\bD_\be_\bf_\bi_\bn_\be_\bd _\bS_\be_\bq_\bu_\be_\bn_\bc_\be_\bs

            The _\bm_\ba_\br_\bk command lets the user perform  low-level  manipulation  of
       sequences,  and  also  provides  a  well-needed  debug  facility  to the
       implementors/developers/maintainers  of  _\bM_\bH  (the  _\bM_\bH-hacks).   In   the
       future,  a user-friendly "front-end" for _\bm_\ba_\br_\bk will probably be developed
       to give the _\bM_\bH user a way to take better  advantage  of  the  underlying
       facilities.

       _\bP_\bu_\bb_\bl_\bi_\bc _\ba_\bn_\bd _\bP_\br_\bi_\bv_\ba_\bt_\be _\bU_\bs_\be_\br-_\bD_\be_\bf_\bi_\bn_\be_\bd _\bS_\be_\bq_\bu_\be_\bn_\bc_\be_\bs

            There are two kinds of sequences:  _\bp_\bu_\bb_\bl_\bi_\bc  sequences,  and  _\bp_\br_\bi_\bv_\ba_\bt_\be
       sequences.   _\bP_\bu_\bb_\bl_\bi_\bc  sequences of a folder are accessible to any _\bM_\bH user
       that can read that folder and are kept in the .mh_sequences file in  the
       folder.   _\bP_\br_\bi_\bv_\ba_\bt_\be  sequences  are  accessible  only  to the _\bM_\bH user that
       defined those sequences and are kept in the user's _\bM_\bH context file.   By
       default,  _\bp_\bi_\bc_\bk  (and  _\bm_\ba_\br_\bk )  create  _\bp_\bu_\bb_\bl_\bi_\bc sequences if the folder for
       which the sequences are being defined is writable by the _\bM_\bH user.   Oth-
       erwise,  _\bp_\br_\bi_\bv_\ba_\bt_\be sequences are created.  This can be overridden with the
       `-public' and `-private' switches.

       _\bS_\be_\bq_\bu_\be_\bn_\bc_\be _\bN_\be_\bg_\ba_\bt_\bi_\bo_\bn

            In addition to telling an _\bM_\bH command to use  the  messages  in  the
       sequence "seen", as in

            refile seen +old

       it would be useful to be easily able to tell an _\bM_\bH command  to  use  all
       messages  _\be_\bx_\bc_\be_\bp_\bt  those in the sequence.  One way of doing this would be
       to use _\bm_\ba_\br_\bk and define the sequence explicitly, as in

            mark -delete -zero seen -seq notseen

       which, owing to _\bm_\ba_\br_\bk 's cryptic interpretation of `-delete' and `-zero',
       defines  the  sequence  "notseen" to be all messages not in the sequence
       "seen".  Naturally, anytime the sequence "seen"  is  changed,  "notseen"
       will  have  to be updated.  Another way to achieve this is to define the
       entry "Sequence-Negation:" in the .mh_profile.  If the entry was

            Sequence-Negation: not

       then anytime an _\bM_\bH command was given "notseen"  as  a  `msg'  or  `msgs'
       argument,  it would substitute all messages that are not a member of the
       sequence "seen".  That is,

            refile notseen +new

       does just that.  The value of  the  "Sequence-Negation:"  entry  in  the











                                        -145-


       profile  can be any string.  Hence, experienced users of _\bM_\bH do not use a
       word, but rather a special character which their shell does  not  inter-
       pret  (users  of  the  _\bC_\bS_\bh_\be_\bl_\bl  use a single caret or circumflex (usually
       shift-6), while users of the  Bourne  shell  use  an  exclamation-mark).
       This is because there is nothing to prevent a user of _\bM_\bH from defining a
       sequence with this string as its prefix, if the  string  is  nothing  by
       letters and digits.  Obviously, this could lead to confusing behavior if
       the "Sequence-Negation:" entry leads _\bM_\bH to believe  that  two  sequences
       are opposites by virtue of their names differing by the prefix string.

       _\bT_\bh_\be _\bP_\br_\be_\bv_\bi_\bo_\bu_\bs _\bS_\be_\bq_\bu_\be_\bn_\bc_\be

            Many times users find themselves issuing a series  of  commands  on
       the  same  sequences  of messages.  If the user first defined these mes-
       sages as a sequence, then considerable typing may be saved.  If the user
       doesn't  have  this  foresight,  _\bM_\bH  provides  a  handy way of having _\bM_\bH
       remember the `msgs' or `msg' argument last given to an _\bM_\bH  command.   If
       the  entry "Previous-Sequence:" is defined in the .mh_profile, then when
       the command finishes, it will define the sequence(s) named in the  value
       of  this  entry  as  being  exactly  those messages that were specified.
       Hence, a profile entry of

            Previous-Sequence: pseq

       directs any _\bM_\bH command that accepts a `msg' or `msgs' argument to define
       the  sequence  "pseq" as those messages when it finishes.  More than one
       sequence name may be placed in this entry, separated with  spaces.   The
       one  disadvantage of this approach is that the _\bM_\bH progams have to update
       the sequence information for the folder each  time  they  run  (although
       most  programs read this information, usually only _\bp_\bi_\bc_\bk and _\bm_\ba_\br_\bk have to
       write this information out).

       _\bT_\bh_\be _\bU_\bn_\bs_\be_\be_\bn _\bS_\be_\bq_\bu_\be_\bn_\bc_\be

            Finally, some users like to distinguish between messages which have
       been  previously seen by them.  Both _\bi_\bn_\bc and _\bs_\bh_\bo_\bw honorthe profile entry
       "Unseen-Sequence" to support this activity.   Whenever  _\bi_\bn_\bc  places  new
       messages  in  a folder, if the entry "Unseen-Sequence" is defined in the
       .mh_profile, then when the command finishes, _\bi_\bn_\bc will add the  new  mes-
       sages  to  the  sequence(s)  named in the value of this entry.  Hence, a
       profile entry of

            Unseen-Sequence:  unseen

       directs _\bi_\bn_\bc to add new messages to the sequence  "unseen".   Unlike  the
       behavior  of  the  "Previous-Sequence" entry in the profile however, the
       sequence(s) will not be zero'd.

            Similarly, whenever _\bs_\bh_\bo_\bw (or _\bn_\be_\bx_\bt or  _\bp_\br_\be_\bv )  displays  a  message,
       they   remove   those   messages   from   any  sequences  named  by  the
       "Unseen-Sequence" entry in the profile.
\e9
\e9









                                        -146-


       _\bC_\bO_\bM_\bP_\bO_\bS_\bI_\bT_\bI_\bO_\bN _\bO_\bF _\bM_\bA_\bI_\bL

            There are a number of interesting advanced facilities for the  com-
       position of outgoing mail.


       _\bT_\bh_\be _\bD_\br_\ba_\bf_\bt _\bF_\bo_\bl_\bd_\be_\br

            The  _\bc_\bo_\bm_\bp,  _\bd_\bi_\bs_\bt,  _\bf_\bo_\br_\bw,  and  _\br_\be_\bp_\bl  commands  have  two  switches,
       `-draftfolder +folder'        and        `-draftmessage msg'.         If
       `-draftfolder +folder' is used, these commands are directed to construct
       a  draft  message in the indicated folder.  (The "Draft-Folder:" profile
       entry may be used to declare a default draft folder for use  with  _\bc_\bo_\bm_\bp,
       _\bd_\bi_\bs_\bt, _\bf_\bo_\br_\bw, and _\br_\be_\bp_\bl) If `-draftmessage msg' is not used, it defaults to
       `new' (unless the user invokes _\bc_\bo_\bm_\bp  with  `-use',  in  which  case  the
       default  is  `cur').   Hence, the user may have several message composi-
       tions in progress simultaneously.  Now, all of the _\bM_\bH tools  are  avail-
       able  on  each of the user's message drafts (e.g., _\bs_\bh_\bo_\bw, _\bs_\bc_\ba_\bn, _\bp_\bi_\bc_\bk, and
       so on).  If the folder does not exist, the user is asked if it should be
       created (just like with _\br_\be_\bf_\bi_\bl_\be ).  Also, the last draft message the user
       was composing is known as `cur' in the draft folder.

            Furthermore, the _\bs_\be_\bn_\bd command has these switches as  well.   Hence,
       from  the shell, the user can send off whatever drafts desired using the
       standard _\bM_\bH `msgs' convention with `-draftmessage msgs'.  If  no  `msgs'
       are given, it defaults to `cur'.

            In addition, all five  programs  have  a  `-nodraftfolder'  switch,
       which undoes the last occurrence of `-draftfolder folder' (useful if the
       latter occurs in the user's _\bM_\bH profile).

            If the user does not give the `-draftfolder +folder'  switch,  then
       all  these  commands act ``normally''.  Note that the `-draft' switch to
       _\bs_\be_\bn_\bd and _\bs_\bh_\bo_\bw still refers to the file called `draft' in the  user's  _\bM_\bH
       directory.   In  the interests of economy of expression, when using _\bc_\bo_\bm_\bp
       or _\bs_\be_\bn_\bd, the user needn't prefix the draft `msg' or `msgs' with `-draft-
       message'.   Both  of these commands accept a `file' or `files' argument,
       and they will, if given `-draftfolder +folder' treat these arguments  as
       `msg' or `msgs'.[2] Hence,

            send -draftf +drafts first

       is the same as

            send -draftf +drafts -draftm first



\e9          [2]  This may appear to be inconsistent, at first, but it saves a lot
       of typing.


\e9









                                        -147-


            To make all this a bit more clear, here are some  examples.   Let's
       assume that the following entries are in the _\bM_\bH profile:

            Draft-Folder: +drafts
            sendf: -draftfolder +drafts

       Furthermore, let's assume that the program _\bs_\be_\bn_\bd_\bf is a (symbolic) link in
       the user's $HOME/bin/ directory to _\bs_\be_\bn_\bd.  Then, any of the commands

            comp
            dist
            forw
            repl

       constructs the message draft in the `draft' folder using the `new'  mes-
       sage  number.   Furthermore, they each define `cur' in this folder to be
       that message draft.  If the user were to use the _\bq_\bu_\bi_\bt  option  at  `What
       now?'  level, then later on, if no other draft composition was done, the
       draft could be sent with simply

            sendf

       Or, if more editing was required, the draft could be edited with

            comp -use

       Instead, if other drafts had been composed in the meantime, so that this
       message  draft  was no longer known as `cur' in the `draft' folder, then
       the user could _\bs_\bc_\ba_\bn the folder to see which message draft in the  folder
       should be used for editing or sending.  Clever users could even employ a
       back-quoted _\bp_\bi_\bc_\bk to do the work:

            comp -use `pick +drafts -to bug-mh`

       or

            sendf `pick +drafts -to bug-mh`

       Note that in the _\bc_\bo_\bm_\bp example, the output from _\bp_\bi_\bc_\bk must  resolve  to  a
       single  message  draft (it makes no sense to talk about composing two or
       more drafts with one invocation of _\bc_\bo_\bm_\bp ).  In  contrast,  in  the  _\bs_\be_\bn_\bd
       example,  as  many  message  drafts  as  desired  can appear, since _\bs_\be_\bn_\bd
       doesn't mind sending more than one draft at a time.

            Note that the argument `-draftfolder +folder' is  not  included  in
       the  profile  entry  for  _\bs_\be_\bn_\bd,  since  when  _\bc_\bo_\bm_\bp, et. al., invoke _\bs_\be_\bn_\bd
       directly, they supply _\bs_\be_\bn_\bd with the UNIX pathname of the message  draft,
       and  not  a `draftmessage msg' argument.  As far as _\bs_\be_\bn_\bd is concerned, a
       _\bd_\br_\ba_\bf_\bt _\bf_\bo_\bl_\bd_\be_\br is not being used.

            It is important to realize that _\bM_\bH treats the draft folder  like  a
       standard  _\bM_\bH  folder  in nearly all respects.  There are two exceptions:











                                        -148-


       first\b\b\b\b\b_____, under no circumstancs will the `-draftfolder folder' switch cause
       the named folder to become the current folder.[3] Second\b\b\b\b\b\b______, although  con-
       ceptually _\bs_\be_\bn_\bd deletes the `msgs' named in the draft folder, it does not
       call `delete-prog' to perform the deletion.


       _\bW_\bh_\ba_\bt _\bH_\ba_\bp_\bp_\be_\bn_\bs _\bi_\bf _\bt_\bh_\be _\bD_\br_\ba_\bf_\bt _\bE_\bx_\bi_\bs_\bt_\bs

            When the _\bc_\bo_\bm_\bp, _\bd_\bi_\bs_\bt, _\bf_\bo_\br_\bw, and _\br_\be_\bp_\bl commands are  invoked  and  the
       draft  you indicated already exists, these programs will prompt the user
       for a reponse directing the program's action.  The prompt is

            Draft ``/usr/src/uci/mh/mhbox/draft'' exists (xx bytes).
            Disposition?

       The appropriate responses and their meanings are: replace\b\b\b\b\b\b\b_______:  deletes  the
       draft  and starts afresh; list\b\b\b\b____: lists the draft; refile\b\b\b\b\b\b______: files the draft
       into a folder and starts afresh; and, quit\b\b\b\b____: leaves the draft intact  and
       exits.   In addition, if you specified `-draftfolder folder' to the com-
       mand, then one other response will be accepted: new\b\b\b___: finds a new  draft,
       just  as  if `-draftmessage new' had been given.  Finally, the _\bc_\bo_\bm_\bp com-
       mand will accept one more response: use\b\b\b___: re-uses the draft, just  as  if
       `-use' had been given.


       _\bT_\bh_\be _\bP_\bu_\bs_\bh _\bO_\bp_\bt_\bi_\bo_\bn _\ba_\bt _\bW_\bh_\ba_\bt _\bn_\bo_\bw? _\bL_\be_\bv_\be_\bl

            The _\bp_\bu_\bs_\bh option to the "What now?" query in the _\bc_\bo_\bm_\bp,  _\bd_\bi_\bs_\bt,  _\bf_\bo_\br_\bw,
       and  _\br_\be_\bp_\bl  commands,  directs the command to _\bs_\be_\bn_\bd the draft in a special
       detached fashion, with all normal output discarded.  If _\bp_\bu_\bs_\bh is used and
       the  draft  can not be sent, then _\bM_\bH will send the user a message, indi-
       cating the name of the draft file, and an explanation of the failure.

            The user can also invoke _\bs_\be_\bn_\bd  from  the  shell  with  the  `-push'
       switch, which makes _\bs_\be_\bn_\bd act like it had been _\bp_\bu_\bs_\bh 'd by one of the com-
       position commands.

            By using _\bp_\bu_\bs_\bh, the user can free the  shell  to  do  other  things,
       because  it appears to the shell that the _\bM_\bH command has finished.  As a
       result the shell will immediately prompt for  another  command,  despite
       the  fact  that  the  command is really still running.  Note that if the


\e9          [3]  Obviously,  if  the folder appeared in the context of a standard
       `+folder' argument to an _\bM_\bH program, as in

            scan +drafts

       it might become the current folder, depending on the context changes  of
       the _\bM_\bH program in question.


\e9









                                        -149-


       user indicates that annotations are to be performed (with `-annotate' to
       _\bd_\bi_\bs_\bt,  _\bf_\bo_\br_\bw,  or _\br_\be_\bp_\bl), the annotations will be performed after the mes-
       sage has been successfully sent.  This action will appear to occur asyn-
       chronously.   Obviously,  if one of the messages that is to be annotated
       is removed before the draft has been successfully  sent,  then  when  _\bM_\bH
       tries  to  make the annotations, it won't be able to do so.  In previous
       versions of _\bM_\bH, this resulted in an error message mysteriously appearing
       on  the  user's  terminal.   In _\bm_\bh._\b5 and later versions, in this special
       circumstance, no error will be generated.

            If send is _\bp_\bu_\bs_\bh 'd, then the `-forward' switch  is  examined  if  a
       failure notice is generated.  If given, then the draft is forwarded with
       the failure notice sent to the user.  This allows  rapid  _\bb_\bu_\br_\bs_\bt 'ing  of
       the failure notice to retrieve the unsent draft.


       _\bO_\bp_\bt_\bi_\bo_\bn_\bs _\ba_\bt _\bW_\bh_\ba_\bt _\bn_\bo_\bw? _\bL_\be_\bv_\be_\bl

            By default, the message composition programs call a program  called
       _\bw_\bh_\ba_\bt_\bn_\bo_\bw  before  the initial draft composition.  The _\bM_\bH user can specify
       any program for this.  Following is some information about  the  default
       "What  now?" level.  More detailed information can be found in the _\bw_\bh_\ba_\bt_\b-
       _\bn_\bo_\bw (1) manual entry.

            When using the _\bc_\bo_\bm_\bp, _\bd_\bi_\bs_\bt, _\bf_\bo_\br_\bw, and _\br_\be_\bp_\bl commands at  "What  now?"
       level,  the _\be_\bd_\bi_\bt, _\bl_\bi_\bs_\bt, _\bh_\be_\ba_\bd_\be_\br_\bs, _\br_\be_\bf_\bi_\bl_\be, and (for the _\bd_\bi_\bs_\bt and _\br_\be_\bp_\bl com-
       mands) the _\bd_\bi_\bs_\bp_\bl_\ba_\by options will pass on any additional  arguments  given
       them to whatever program they invoke.

            In _\bm_\bh._\b1 (the original RAND _\bM_\bH ) and _\bm_\bh._\b2 (the first UCI version  of
       _\bM_\bH ),  _\bM_\bH  used a complicated heuristic to determine if the draft should
       be deleted or preserved after an unsuccessful edit.   In  _\bm_\bh._\b3,  _\bM_\bH  was
       changed to preserve the draft always, since _\bc_\bo_\bm_\bp, et. al., could usually
       look at a draft, apply another set of heuristics, and decide if  it  was
       important  or  not.   With the notion of a _\bd_\br_\ba_\bf_\bt _\bf_\bo_\bl_\bd_\be_\br, in which one by
       default gets a `new' message draft, the edit deletion/preservation algo-
       rithm  was re-implemented, to keep the draft folder from being cluttered
       with aborted edits.

            Also, note that by default, if the  draft  cannot  be  successfully
       sent,  these  commands  return  to "What now?" level.  But, when _\bp_\bu_\bs_\bh is
       used, this does not happen (obviously).  Hence, if these  commands  were
       expected  to  annotate  any messages, this will have to be done by hand,
       later on, with the _\ba_\bn_\bn_\bo command.

            Finally, if the `-delete' switch is not given to the  _\bq_\bu_\bi_\bt  option,
       then these commands will inform the user of the name of the unsent draft
       file.


       _\bD_\bi_\bg_\be_\bs_\bt_\bs
\e9
\e9









                                        -150-


            The _\bf_\bo_\br_\bw command has the beginnings  of  a  digestifying  facility,
       with the `-digest list', `-issue number', and `-volume number' switches.

       If _\bf_\bo_\br_\bw is given "list" to the `-digest' switch as the name of the  dis-
       cussion  group,  and  the `-issue number' switch is not given, then _\bf_\bo_\br_\bw
       looks for an entry in the user's _\bM_\bH context  called  "_\bd_\bi_\bg_\be_\bs_\bt-issue-list"
       and  increments its value to use as the issue number.  Similarly, if the
       `-volume number'  switch   is   not   given,   then   _\bf_\bo_\br_\bw   looks   for
       "_\bd_\bi_\bg_\be_\bs_\bt-volume-list"  (but  does  not increment its value) to use as the
       volume number.

       Having calculated the name of  the  digest  and  the  volume  and  issue
       numbers, _\bf_\bo_\br_\bw will now process the components file using the same format
       string mechanism used by _\br_\be_\bp_\bl.  The current `%'-escapes are:

       _\be_\bs_\bc_\ba_\bp_\be  _\bt_\by_\bp_\be     _\bs_\bu_\bb_\bs_\bt_\bi_\bt_\bu_\bt_\bi_\bo_\bn
       digest  string   digest name
       msg     integer  issue number
       cur     integer  volume number

       In addition, to capture the current date, any of the escapes  valid  for
       _\bd_\bp (8) are also valid for _\bf_\bo_\br_\bw.

       The default components file used by _\bf_\bo_\br_\bw when in digest mode is:

            From:     %{digest}-Request
            To:       %{digest} Distribution: dist-%{digest};
            Subject:  %{digest} Digest V%(cur) #%(msg)
            Reply-To: %{digest}
            --------
            %{digest} Digest        %(weekday{date}), %2(mday{date}) %(month{date}) 19%02(year{date})
                            Volume %(cur) : Issue %(msg)

            Today's Topics:

       Hence, when the `-digest' switch is present, the  first  step  taken  by
       _\bf_\bo_\br_\bw  is  to  expand the format strings in the component file.  The next
       step is to compose the draft using  the  standard  digest  encapsulation
       algorithm  (even  putting an "End of list Digest" trailer in the draft).
       Once the draft is composed by _\bf_\bo_\br_\bw, _\bf_\bo_\br_\bw writes out the volume and issue
       profile entries for the digest, and then invokes the editor.

       Naturally,   when   composing   the   draft,   _\bf_\bo_\br_\bw   will   honor   the
       `-filter filterfile'  switch,  which is given to _\bm_\bh_\bl to filter each mes-
       sage being forwarded prior to encapsulation in the draft.  A good filter
       file to use, which is called _\bm_\bh_\bl._\bd_\bi_\bg_\be_\bs_\bt, is:





\e9
\e9









                                        -151-


            width=80,overflowoffset=10
            leftadjust,compress,compwidth=9
            Date:formatfield="%<(nodate{text})%{text}%|%(tws{text})%>"
            From:
            Subject:
            :
            body:nocomponent,overflowoffset=0,noleftadjust,nocompress



\e9       _\bF_\bO_\bL_\bD_\bE_\bR _\bH_\bA_\bN_\bD_\bL_\bI_\bN_\bG

            There are two  interesting  facilities  for  manipulating  folders:
       relative folder addressing, which allows a user to shorten the typing of
       long folder names; and the folder-stack, which permits a user to keep  a
       stack of current folders.


       _\bR_\be_\bl_\ba_\bt_\bi_\bv_\be _\bF_\bo_\bl_\bd_\be_\br _\bA_\bd_\bd_\br_\be_\bs_\bs_\bi_\bn_\bg

            By default, when `+folder' is given, and the  folder  name  is  not
       absolute  (does not start with /, ./, or ../), then the UNIX pathname of
       the folder is interpreted relative to the user's _\bM_\bH directory.  Although
       this  mechanism  works  fine  for  top-level folders and their immediate
       sub-folders, once the depth of the sub-folder  tree  grows,  it  becomes
       rather unwieldly:

            scan +mh/mh.4/draft/flames

       is a lot of typing.  _\bM_\bH can't do anything  if  the  current  folder  was
       "+inbox", but if the current folder was, say, "+mh/mh.4/draft", _\bM_\bH has a
       short-hand notation to reference a sub-folder  of  the  current  folder.
       Using  the  `@folder'  notation,  the  _\bM_\bH user can direct any _\bM_\bH program
       which expects a `+folder' argument to look for the  folder  relative  to
       the  current  folder  instead of the user's _\bM_\bH directory.  Hence, if the
       current folder _\bw_\ba_\bs "+mh/mh.4/draft", then

            scan @flames

       would do the trick handily.  In addition,  if  the  current  folder  _\bw_\ba_\bs
       "+mh/mh.4/draft",

            scan @../pick

       would scan the folder "+mh/mh.4/pick", since, in the  UNIX  fashion,  it
       references the folder "pick" which is a sub-folder of the folder that is
       the parent of the current folder.  Since most advanced _\bM_\bH users seem  to
       exhibit a large degree of locality in referencing folders when they pro-
       cess mail, this convention should receive a wide range of uses.



\e9









                                        -152-


       _\bT_\bh_\be _\bF_\bo_\bl_\bd_\be_\br-_\bS_\bt_\ba_\bc_\bk

            The _\bf_\bo_\bl_\bd_\be_\br-_\bs_\bt_\ba_\bc_\bk mechanism in _\bM_\bH gives the _\bM_\bH user a facility simi-
       lar to the _\bC_\bS_\bh_\be_\bl_\bl 's directory-stack.  Simply put,

            folder -push +foo

       makes "foo" the current folder, saving the folder  that  was  previously
       the current folder on the _\bf_\bo_\bl_\bd_\be_\br-_\bs_\bt_\ba_\bc_\bk.  As expected,

            folder -pop

       takes the top of the _\bf_\bo_\bl_\bd_\be_\br-_\bs_\bt_\ba_\bc_\bk and makes it the current folder.  Each
       of  these switches lists the _\bf_\bo_\bl_\bd_\be_\br-_\bs_\bt_\ba_\bc_\bk when they execute.  It is sim-
       ple to write a _\bp_\bu_\bs_\bh_\bf command as a shell script.  It's one line:

            exec folder -push $@

       Probably a better way is to link  _\bf_\bo_\bl_\bd_\be_\br  to  the  $HOME/bin/  directory
       under the name of _\bp_\bu_\bs_\bh_\bf and then add the entry

            pushf: -push

       to the .mh_profile.

            The manual page for _\bf_\bo_\bl_\bd_\be_\br discusses the analogy between the _\bC_\bS_\bh_\be_\bl_\bl
       directory stack commands and the switches in _\bf_\bo_\bl_\bd_\be_\br which manipulate the
       _\bf_\bo_\bl_\bd_\be_\br-_\bs_\bt_\ba_\bc_\bk.  The _\bf_\bo_\bl_\bd_\be_\br command uses the context entry `Folder-Stack:'
       to keep track of the folders in the user's stack of folders.






















\e9
\e9












                                      Appendix A
                                   _\bC_\bO_\bM_\bM_\bA_\bN_\bD _\bS_\bU_\bM_\bM_\bA_\bR_\bY



\e9       ali [-alias aliasfile] [-list] [-nolist] [-normalize]
            [-nonormalize] [-user] [-nouser] aliases ...  [-help]

       anno [+folder] [msgs] [-component field] [-inplace] [-noinplace]
            [-date] [-nodate] [-text body] [-help]

       bbc [bboards ...] [-topics] [-check] [-read] [-quiet] [-verbose]
            [-archive] [-noarchive] [-protocol] [-noprotocol]
            [-mshproc program] [switches for _\bm_\bs_\bh_\bp_\br_\bo_\bc] [-rcfile rcfile]
            [-norcfile] [-file BBoardsfile] [-user BBoardsuser]
            [-host host] [-help]

       burst [+folder] [msgs] [-inplace] [-noinplace] [-quiet] [-noquiet]
            [-verbose] [-noverbose] [-help]

       comp [+folder] [msg] [-draftfolder +folder] [-draftmessage msg]
            [-nodraftfolder] [-editor editor] [-noedit] [-file file]
            [-form formfile] [-use] [-nouse] [-whatnowproc program]
            [-nowhatnowproc] [-help]

       dist [+folder] [msg] [-annotate] [-noannotate]
            [-draftfolder +folder] [-draftmessage msg] [-nodraftfolder]
            [-editor editor] [-noedit] [-form formfile] [-inplace]
            [-noinplace] [-whatnowproc program] [-nowhatnowproc] [-help]

       folder [+folder] [msg] [-all] [-fast] [-nofast] [-header]
            [-noheader] [-pack] [-nopack] [-recurse] [-norecurse] [-total]
            [-nototal] [-print] [-noprint] [-list] [-nolist] [-push]
            [-pop] [-help]

       folders

       forw [+folder] [msgs] [-annotate] [-noannotate]
            [-draftfolder +folder] [-draftmessage msg] [-nodraftfolder]
            [-editor editor] [-noedit] [-filter filterfile]
            [-form formfile] [-format] [-noformat] [-inplace] [-noinplace]
            [-whatnowproc program] [-nowhatnowproc] [-help]

       forw [+folder] [msgs] [-digest list] [-issue number]
            [-volume number] [other switches for _\bf_\bo_\br_\bw] [-help]







\e9                                   -153-












       inc [+folder] [-audit audit-file] [-noaudit] [-changecur]
            [-nochangecur] [-file name] [-form formatfile]
            [-format string] [-silent] [-nosilent] [-truncate]
            [-notruncate] [-width columns] [-host host] [-user user]
            [-pack file] [-nopack] [-rpop] [-norpop] [-help]

       mark [+folder] [msgs] [-sequence name ...] [-add] [-delete] [-list]
            [-public] [-nopublic] [-zero] [-nozero] [-help]

       /usr/local/lib/mh/mhl [-bell] [-nobell] [-clear] [-noclear]
            [-folder +folder] [-form formfile] [-length lines]
            [-width columns] [-moreproc program] [-nomoreproc] [files ...]
            [-help]

       mhmail [ addrs ... [-body text] [-cc addrs ...] [-from addr]
            [-subject subject]] [-help]

       mhpath [+folder] [msgs] [-help]

       msgchk [-date] [-nodate] [-notify all/mail/nomail]
            [-nonotify all/mail/nomail] [-host host] [-user user] [-rpop]
            [-norpop] [users ...] [-help]

       msh [-prompt string] [-scan] [-noscan] [-topcur] [-notopcur] [file]
            [-help]

       next [+folder] [-header] [-noheader] [-showproc program]
            [-noshowproc] [switches for _\bs_\bh_\bo_\bw_\bp_\br_\bo_\bc] [-help]

       packf [+folder] [msgs] [-file name] [-help]

       pick [+folder] [msgs] [-and ...] [-or ...] [-not ...]
            [-lbrace ... -rbrace] [--component pattern] [-after date]
            [-before date] [-datefield field] [-sequence name ...]
            [-public] [-nopublic] [-zero] [-nozero] [-list] [-nolist]
            [-help]

       prev [+folder] [-header] [-noheader] [-showproc program]
            [-noshowproc] [switches for _\bs_\bh_\bo_\bw_\bp_\br_\bo_\bc] [-help]

       prompter [-erase chr] [-kill chr] [-prepend] [-noprepend] [-rapid]
            [-norapid] [-doteof] [-nodoteof] file [-help]

       /usr/local/lib/mh/rcvstore [+folder] [-create] [-nocreate]
            [-sequence name ...] [-public] [-nopublic] [-zero] [-nozero]
            [-help]





\e9
\e9                                   -154-












       refile [msgs] [-draft] [-link] [-nolink] [-preserve] [-nopreserve]
            [-src +folder] [-file file] +folder ...  [-help]

       repl [+folder] [msg] [-annotate] [-noannotate] [-cc all/to/cc/me]
            [-nocc all/to/cc/me] [-draftfolder +folder]
            [-draftmessage msg] [-nodraftfolder] [-editor editor]
            [-noedit] [-fcc +folder] [-filter filterfile] [-form formfile]
            [-inplace] [-noinplace] [-query] [-noquery]
            [-whatnowproc program] [-nowhatnowproc] [-width columns]
            [-help]

       rmf [+folder] [-interactive] [-nointeractive] [-help]

       rmm [+folder] [msgs] [-help]

       scan [+folder] [msgs] [-clear] [-noclear] [-form formatfile]
            [-format string] [-header] [-noheader] [-width columns]
            [-reverse] [-noreverse] [-file filename] [-help]

       send [-alias aliasfile] [-draft] [-draftfolder +folder]
            [-draftmessage msg] [-nodraftfolder] [-filter filterfile]
            [-nofilter] [-format] [-noformat] [-forward] [-noforward]
            [-msgid] [-nomsgid] [-push] [-nopush] [-verbose] [-noverbose]
            [-watch] [-nowatch] [-width columns] [file ...] [-help]

       show [+folder] [msgs] [-draft] [-header] [-noheader]
            [-showproc program] [-noshowproc] [switches for _\bs_\bh_\bo_\bw_\bp_\br_\bo_\bc]
            [-help]

       sortm [+folder] [msgs] [-datefield field] [-textfield field]
            [-notextfield] [-limit days] [-nolimit] [-verbose]
            [-noverbose] [-help]

       vmh [-prompt string] [-vmhproc program] [-novmhproc]
            [switches for _\bv_\bm_\bh_\bp_\br_\bo_\bc] [-help]

       whatnow [-draftfolder +folder] [-draftmessage msg] [-nodraftfolder]
            [-editor editor] [-noedit] [-prompt string] [file] [-help]

       whom [-alias aliasfile] [-check] [-nocheck] [-draft]
            [-draftfolder +folder] [-draftmessage msg] [-nodraftfolder]
            [file] [-help]

       /usr/local/lib/mh/ap [-form formatfile] [-format string]
            [-normalize] [-nonormalize] [-width columns] addrs ...
            [-help]





\e9
\e9                                   -155-












       /usr/local/lib/mh/conflict [-mail name] [-search directory]
            [aliasfiles ...] [-help]

       /usr/local/lib/mh/dp [-form formatfile] [-format string]
            [-width columns] dates ...  [-help]

       /usr/local/lib/mh/install-mh [-auto] [-compat]

       /usr/local/lib/mh/post [-alias aliasfile] [-filter filterfile]
            [-nofilter] [-format] [-noformat] [-msgid] [-nomsgid]
            [-verbose] [-noverbose] [-watch] [-nowatch] [-width columns]
            file [-help]







































\e9
\e9                                        -156-












                                      Appendix B
                                   _\bM_\bE_\bS_\bS_\bA_\bG_\bE _\bN_\bA_\bM_\bE _\bB_\bN_\bF



\e9
                 msgs                  :=  msgspec                |
                                           msgs msgspec

                 msgspec               :=  msg                    |
                                           msg-range              |
                                           msg-sequence           |
                                           user-defined-sequence

                 msg                   :=  msg-name               |
                                           <number>

                 msg-name              :=  "first"                |
                                           "last"                 |
                                           "cur"                  |
                                           "."                    |
                                           "next"                 |
                                           "prev"

                 msg-range             :=  msg"-"msg              |
                                           "all"

                 msg-sequence          :=  msg":"signed-number

                 signed-number         :=  "+"<number>            |
                                           "-"<number>            |
                                           <number>

                 user-defined-sequence :=  <alpha>                |
                                           <alpha><alphanumeric>*


       Where <number> is a decimal number greater than zero.

       Msg-range specifies all of the messages in the given range and must  not
       be empty.

       Msg-sequence specifies up to <number> of messages, beginning with  "msg"
       (in the case of first, cur, next, or <number>), or ending with "msg" (in
       the case of prev or last).  +<number> forces "starting  with  msg",  and
       -<number> forces "ending with number".  In all cases, "msg" must exist.

       User-defined sequences are defined and manipulated  with  the  _\bp_\bi_\bc_\bk  and
       _\bm_\ba_\br_\bk commands.



\e9                                        -157-












                                      _\bR_\bE_\bF_\bE_\bR_\bE_\bN_\bC_\bE_\bS



       1.  Crocker, D. H., J. J. Vittal, K. T. Pogran,  and  D.  A.  Henderson,
           Jr.,  "Standard  for  the  Format  of  ARPA  Network Text Messages,"
           _\bR_\bF_\bC_\b7_\b3_\b3, November 1977.

       2.  Thompson, K., and D. M. Ritchie,  "The  UNIX  Time-sharing  System,"
           _\bC_\bo_\bm_\bm_\bu_\bn_\bi_\bc_\ba_\bt_\bi_\bo_\bn_\bs _\bo_\bf _\bt_\bh_\be _\bA_\bC_\bM, Vol. 17, July 1974, pp. 365-375.

       3.  McCauley, E. J., and P. J. Drongowski, "KSOS-The Design of a  Secure
           Operating  System,"  _\bA_\bF_\bI_\bP_\bS _\bC_\bo_\bn_\bf_\be_\br_\be_\bn_\bc_\be _\bP_\br_\bo_\bc_\be_\be_\bd_\bi_\bn_\bg_\bs, National Computer
           Conference, Vol. 48, 1979, pp. 345-353.

       4.  Crocker, David H., _\bF_\br_\ba_\bm_\be_\bw_\bo_\br_\bk _\ba_\bn_\bd _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\bs _\bo_\bf _\bt_\bh_\be "_\bM_\bS" _\bP_\be_\br_\bs_\bo_\bn_\ba_\bl _\bM_\be_\bs_\b-
           _\bs_\ba_\bg_\be _\bS_\by_\bs_\bt_\be_\bm, The RAND Corporation, R-2134-ARPA, December 1977.

       5.  Thompson, K., and D. M. Ritchie, _\bU_\bN_\bI_\bX _\bP_\br_\bo_\bg_\br_\ba_\bm_\bm_\be_\br'_\bs _\bM_\ba_\bn_\bu_\ba_\bl, 6th  ed.,
           Western  Electric  Company,  May 1975 (available only to UNIX licen-
           sees).

       6. Crocker, D. H., "Standard for the Format of ARPA Internet  Text  Mes-
           sages," _\bR_\bF_\bC_\b8_\b2_\b2, August 1982.



























\e9
\e9                                        -158-































































\e9
\e9                                         -i-












                                      _\bR_\bE_\bA_\bD _\bT_\bH_\bI_\bS




            Although the _\bM_\bH system was originally developed by  the  RAND  Cor-
       poration,  and is now in the public domain, the RAND Corporation assumes
       no responsibility for _\bM_\bH or this particular version of _\bM_\bH.

            In addition, the Regents of the University of California issue  the
       following disclaimer in regard to the UCI version of _\bM_\bH:

            "Although each program has been tested by its contributor, no  war-
            ranty,  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 distri-
            bution constitute any  such  warranty,  and  no  responsibility  is
            assumed  by the contributor or the University of California in con-
            nection herewith."

            This version of _\bM_\bH is in the public domain, and as such, there  are
       no  real  restrictions on its use.  The _\bM_\bH 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.

            _\bM_\bH is a software package that is supported neither by the RAND Cor-
       poration nor the University of California.  However, since we do use the
       software ourselves and plan to continue using (and  improving)  _\bM_\bH,  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   _\bM_\bH   is   Bug-MH@ICS.UCI.EDU   (in   the   ARPA   Internet),   and
       ...!ucbvax!ucivax!bug-mh (UUCP).  Presently, there are two Internet dis-
       cussion   groups,   MH-Users@ICS.UCI.EDU   and   MH-Workers@ICS.UCI.EDU.
       MH-Workers is for people discussing code changes to _\bM_\bH.  MH-Users is for
       general  discussion  about  how to use _\bM_\bH.  MH-Users is bi-directionally
       gatewayed into USENET as comp.mail.mh.

       _\bH_\bO_\bW _\bT_\bO _\bG_\bE_\bT _\bM_\bH

            Since you probably already have _\bM_\bH, you may not need to  read  this
       unless  you  suspect you have an old version.  There are two ways to get
       the latest release:

            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 README file in that
       directory which tells what the current release of _\bM_\bH is, and how to  get
       updates.

\e9
\e9                                         -i-









                                         -ii-


            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.

            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:

                 Regents of the University of California

       The distribution address is:

                 Computing Support Group
                 Attn: MH distribution
                 Department of Information and Computer Science
                 University of California, Irvine
                 Irvine, CA  92717

                 714/856-7554

            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.























\e9
\e9












                                       _\bF_\bO_\bR_\bE_\bW_\bO_\bR_\bD




            This document describes the RAND _\bM_\bH Message Handling  System.   Its
       primary  purpose  is  to  serve as a user's manual.  It has been heavily
       based on a previous version of the manual,  prepared  by  Bruce  Borden,
       Stockton Gaines, and Norman Shapiro.

            _\bM_\bH is a particularly novel system, and thus it is often more  prone
       to  change  than  other  pieces  of  production software.  As such, some
       specific points in this manual may not be correct in the future.  In all
       cases,  the  on-line  sections  of  this  manual,  available through the
       UNIX[1] _\bm_\ba_\bn command, should present the most current information.

            When reading this document as a user's manual, certain sections are
       more  interesting than others.  The Preface and Summary are not particu-
       larly interesting to those interested in learning _\bM_\bH.  The  Introduction
       is slightly more interesting, as it touches upon the organization of the
       remainder of this document.  The most useful sections are the  Overview,
       Tutorial,  and Detailed Description.  The Overview should be read by all
       _\bM_\bH users, regardless of their expertise (beginning, novice, advanced, or
       hacker).   The  Tutorial  should  be read by all beginning and novice _\bM_\bH
       users, as it presents a nice description of the _\bM_\bH system.  The Detailed
       Description  should  be  read by the day-to-day user of _\bM_\bH, as it spells
       out all of the realities of the _\bM_\bH system.  The Advanced  Features  sec-
       tion discusses some powerful _\bM_\bH capabilities for advanced users.  Appen-
       dix A is particularly useful for novices, as it summarizes  the  invoca-
       tion syntax of all the _\bM_\bH commands.

            There are also several other documents which may be useful to  you:
       _\bT_\bh_\be  _\bR_\bA_\bN_\bD  _\bM_\bH _\bM_\be_\bs_\bs_\ba_\bg_\be _\bH_\ba_\bn_\bd_\bl_\bi_\bn_\bg _\bS_\by_\bs_\bt_\be_\bm: _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl, which is a tutorial for
       _\bM_\bH; _\bT_\bh_\be _\bR_\bA_\bN_\bD _\bM_\bH _\bM_\be_\bs_\bs_\ba_\bg_\be _\bH_\ba_\bn_\bd_\bl_\bi_\bn_\bg _\bS_\by_\bs_\bt_\be_\bm: _\bT_\bh_\be _\bU_\bC_\bI _\bB_\bB_\bo_\ba_\br_\bd_\bs _\bF_\ba_\bc_\bi_\bl_\bi_\bt_\by, which
       describes  the  BBoards handling under _\bM_\bH; _\bM_\bH._\b5: _\bH_\bo_\bw _\bt_\bo _\bp_\br_\bo_\bc_\be_\bs_\bs _\b2_\b0_\b0 _\bm_\be_\bs_\b-
       _\bs_\ba_\bg_\be_\bs _\ba _\bd_\ba_\by _\ba_\bn_\bd _\bs_\bt_\bi_\bl_\bl _\bg_\be_\bt _\bs_\bo_\bm_\be _\br_\be_\ba_\bl _\bw_\bo_\br_\bk _\bd_\bo_\bn_\be, which  was  presented  at
       the  1985  Summer  Usenix Conference and Exhibition in Portland, Oregon;
       _\bM_\bH: _\bA _\bM_\bu_\bl_\bt_\bi_\bf_\ba_\br_\bi_\bo_\bu_\bs _\bU_\bs_\be_\br _\bA_\bg_\be_\bn_\bt, which has been accepted  for  publication
       by  Computer  Networks;  _\bM_\bZ_\bn_\be_\bt: _\bM_\ba_\bi_\bl _\bS_\be_\br_\bv_\bi_\bc_\be _\bf_\bo_\br _\bP_\be_\br_\bs_\bo_\bn_\ba_\bl _\bM_\bi_\bc_\br_\bo-_\bC_\bo_\bm_\bp_\bu_\bt_\be_\br
       _\bS_\by_\bs_\bt_\be_\bm_\bs, which was presented at the  First  International  Symposium  on
       Computer  Message  Systems  in  Nottingham, U.K.; and, _\bD_\be_\bs_\bi_\bg_\bn _\bo_\bf _\bt_\bh_\be _\bT_\bT_\bI
       _\bP_\br_\bo_\bt_\bo_\bt_\by_\bp_\be _\bT_\br_\bu_\bs_\bt_\be_\bd _\bM_\ba_\bi_\bl _\bA_\bg_\be_\bn_\bt, which describes  a  proprietary  "trusted"
       mail  system  built on _\bM_\bH.  There are also documents, mostly specific to
       U.C. Irvine which you may find interesting: _\bM_\bH _\bf_\bo_\br _\bB_\be_\bg_\bi_\bn_\bn_\be_\br_\bs, and _\bM_\bH _\bf_\bo_\br
       _\bM_\bM _\bU_\bs_\be_\br_\bs.  All of these documents exist in the _\bm_\bh._\b6 distribution sent to
       your site.  There's also a document, _\bC_\bh_\ba_\bn_\bg_\be_\bs _\bt_\bo _\bt_\bh_\be _\bR_\bA_\bN_\bD _\bM_\bH _\bM_\be_\bs_\bs_\ba_\bg_\be _\bH_\ba_\bn_\b-
       _\bd_\bl_\bi_\bn_\bg  _\bS_\by_\bs_\bt_\be_\bm:  _\bM_\bH._\b6,  which  describes  user-visible changes made to _\bM_\bH


\e9          [1] UNIX is a trademark of AT&T Bell Laboratories.


\e9                                        -iii-









                                         -iv-


       since the last major release.

            This manual is very large, as it describes a large, powerful system
       in gruesome detail.  The important thing to remember is:


                                    _\bD_\bO_\bN'_\bT _\bP_\bA_\bN_\bI_\bC[_\b2]


       As explained in the tutorial, you really need to know only 5 commands to
       handle most of your mail.

            Very advanced users may wish to consult _\bT_\bh_\be _\bR_\bA_\bN_\bD  _\bM_\bH  _\bM_\be_\bs_\bs_\ba_\bg_\be  _\bH_\ba_\bn_\b-
       _\bd_\bl_\bi_\bn_\bg  _\bS_\by_\bs_\bt_\be_\bm:  _\bA_\bd_\bm_\bi_\bn_\bi_\bs_\bt_\br_\ba_\bt_\bo_\br'_\bs _\bG_\bu_\bi_\bd_\be, which is also present in the _\bm_\bh._\b6
       distribution sent to your site.


































\e9          [2] Note the large, _\bf_\br_\bi_\be_\bn_\bd_\bl_\by letters.


\e9












                                   _\bA_\bC_\bK_\bN_\bO_\bW_\bL_\bE_\bD_\bG_\bM_\bE_\bN_\bT_\bS




            The _\bM_\bH system described herein is based on  the  original  RAND  _\bM_\bH
       system.   It  has  been  extensively  developed (perhaps too much so) by
       Marshall T. Rose and John L. Romine at  the  University  of  California,
       Irvine.  Einar A. Stefferud, Jerry N. Sweet, and Terry P. Domae provided
       numerous suggestions to improve the UCI version of  _\bM_\bH.   Of  course,  a
       large  number  of  people have helped _\bM_\bH along.  The list of ``_\bM_\bH immor-
       tals'' is too long to list here.  However, Van Jacobson deserves a  spe-
       cial  acknowledgement for his tireless work in improving the performance
       of _\bM_\bH.  Some programs have been speeded-up by a factor of 10 or 20.  All
       of  users  of  _\bM_\bH,  everywhere,  owe  a special thanks to Van.  For this
       release, numerous _\bM_\bH-_\bW_\bo_\br_\bk_\be_\br_\bs sent in fixes and other changes.  A handful
       of  courageous  _\bM_\bH-_\bW_\bo_\br_\bk_\be_\br_\bs volunteered to beta-test these changes; their
       help is particularly appreciated.

            This manual is based on the original _\bM_\bH manual written at  RAND  by
       Bruce Borden, Stockton Gaines, and Norman Shapiro.






























\e9
\e9                                         -v-












                                       _\bP_\bR_\bE_\bF_\bA_\bC_\bE




            This report describes a system for dealing with messages  transmit-
       ted  on  a  computer.  Such messages might originate with other users of
       the same computer or might come from an outside source through a network
       to  which the user's computer is connected.  Such computer-based message
       systems are becoming increasingly widely used, both within  and  outside
       the Department of Defense.

            The message handling system _\bM_\bH was developed for two reasons.   One
       was  to  investigate some research ideas concerning how a message system
       might take advantage  of  the  architecture  of  the  UNIX  time-sharing
       operating  system  for Digital Equipment Corporation PDP-11 and VAX com-
       puters, and the special features of UNIX's command-level interface  with
       the  user  (the  "shell").  The other reason was to provide a better and
       more adaptable base than that of conventional designs on which to  build
       a  command and control message system.  The effort has succeeded in both
       regards, although this report mainly describes the message system itself
       and how it fits in with UNIX.

            The present report  should  be  of  interest  to  three  groups  of
       readers.   First, it is a complete reference manual for the users of _\bM_\bH.
       Second, it should be of interest to those who have a  general  knowledge
       of  computer-based message systems, both in civilian and military appli-
       cations.  Finally, it should be of interest to  those  who  build  large
       subsystems  that  interface  with  users,  since  it  illustrates  a new
       approach to such interfaces.

            The original _\bM_\bH system was developed  by  Bruce  Borden,  using  an
       approach  suggested  by  Stockton  Gaines  and Norman Shapiro.  Valuable
       assistance was provided by Phyllis Kantar in the  later  stages  of  the
       system's  implementation.   Several  colleagues contributed to the ideas
       included in this system, particularly Robert Anderson and David Crocker.
       In  addition,  valuable  experience  in  message systems, and a valuable
       source of ideas, was available to us in the form of a  previous  message
       system for UNIX called MS, designed at RAND by David Crocker.

            This report was originally prepared as part  of  the  RAND  project
       entitled "Data Automation Research", sponsored by Project AIR FORCE.









\e9
\e9                                         -vi-












                                       _\bS_\bU_\bM_\bM_\bA_\bR_\bY




            Electronic communication of text messages is becoming  commonplace.
       Computer-based  message systems-software packages that provide tools for
       dealing with messages-are used in many contexts.  In particular, message
       systems  are  becoming increasingly important in command and control and
       intelligence applications.

            This report describes a message handling system  called  _\bM_\bH.   This
       system  provides  the  user with tools to compose, send, receive, store,
       retrieve, forward, and reply to messages.  _\bM_\bH has been built on the UNIX
       time-sharing  system,  a  popular operating system developed for the DEC
       PDP-11 and VAX classes of computers.

            A complete description of _\bM_\bH is given for users of the system.  For
       those who do not intend to use the system, this description gives a gen-
       eral idea of what a message system is like.  The  system  involves  some
       new ideas about how large subsystems can be constructed.

            The interesting and unusual features of _\bM_\bH include  the  following:
       The  user command interface to _\bM_\bH is the UNIX "shell" (the standard UNIX
       command interpreter).  Each separable  component  of  message  handling,
       such  as  message composition or message display, is a separate command.
       Each program is driven from and  updates  a  private  user  environment,
       which  is  stored  as  a file between program invocations.  This private
       environment also contains information  to  "custom  tailor"  _\bM_\bH  to  the
       individual's  tastes.   _\bM_\bH  stores each message as a separate file under
       UNIX, and it utilizes the tree-structured UNIX file system  to  organize
       groups  of  files  within separate directories or "folders".  All of the
       UNIX facilities for dealing with files and directories, such  as  renam-
       ing,  copying, deleting, cataloging, off-line printing, etc., are appli-
       cable to messages and directories of messages (folders).   Thus,  impor-
       tant capabilities needed in a message system are available in _\bM_\bH without
       the need (often seen in other message systems) for code that  duplicates
       the facilities of the supporting operating system.  It also allows users
       familiar with the shell to use _\bM_\bH with minimal effort.












\e9
\e9                                        -vii-












                                       _\bC_\bO_\bN_\bT_\bE_\bN_\bT_\bS




       READ THIS .........................................................    i

       FOREWORD ..........................................................  iii

       ACKNOWLEDGMENTS ...................................................    v

       PREFACE ...........................................................   vi

       SUMMARY ...........................................................  vii

       Section

          1.  INTRODUCTION ...............................................    1

          2.  OVERVIEW ...................................................    4

          3.  TUTORIAL ...................................................    7

          4.  DETAILED DESCRIPTION .......................................   10
\e9            THE USER PROFILE .............................................   10
\e9            MESSAGE NAMING ...............................................   13
\e9            OTHER MH CONVENTIONS .........................................   14
\e9            MH COMMANDS ..................................................   16
               ALI .......................................................   17
               ANNO ......................................................   19
               BBC .......................................................   21
               BBOARDS ...................................................   24
               BURST .....................................................   26
               COMP ......................................................   28
               DIST ......................................................   30
               FOLDER ....................................................   33
               FORW ......................................................   36
               INC .......................................................   40
               MARK ......................................................   43
               MHL .......................................................   45
               MHMAIL ....................................................   50
               MHOOK .....................................................   52
               MHPATH ....................................................   54
               MSGCHK ....................................................   57
               MSH .......................................................   59
               NEXT ......................................................   63
               PACKF .....................................................   64
               PICK ......................................................   65
               PREV ......................................................   69
               PROMPTER ..................................................   70














               RCVSTORE ..................................................   73
               REFILE ....................................................   75
               REPL ......................................................   77
               RMF .......................................................   81
               RMM .......................................................   83
               SCAN ......................................................   85
               SEND ......................................................   88
               SHOW ......................................................   91
               SORTM .....................................................   94
               VMH .......................................................   96
               WHATNOW ...................................................   98
               WHOM ......................................................  100
\e9            MORE DETAILS .................................................  102
               MH-ALIAS ..................................................  103
               MH-FORMAT .................................................  107
               MH-MAIL ...................................................  116
               MH-PROFILE ................................................  120
               MH-SEQUENCE ...............................................  128
               AP ........................................................  132
               CONFLICT ..................................................  134
               DP ........................................................  136
               INSTALL-MH ................................................  138
               POST ......................................................  139

          5.  REPORTING PROBLEMS .........................................  141

          6.  ADVANCED FEATURES ..........................................  142
\e9            USER-DEFINED SEQUENCES .......................................  142
               Pick and User-Defined Sequences ...........................  142
               Mark and User-Defined Sequences ...........................  144
               Public and Private User-Defined Sequences .................  144
               Sequence Negation .........................................  144
               The Previous Sequence .....................................  145
               The Unseen Sequence .......................................  145
\e9            COMPOSITION OF MAIL ..........................................  146
               The Draft Folder ..........................................  146
               What Happens if the Draft Exists ..........................  148
               The Push Option at What now? Level ........................  148
               Options at What now? Level ................................  149
               Digests ...................................................  150
\e9            FOLDER HANDLING ..............................................  151
               Relative Folder Addressing ................................  151
               The Folder-Stack ..........................................  152

       Appendix
          A.  Command Summary ............................................  153
          B.  Message Name BNF ...........................................  157

       REFERENCES ........................................................  158
\e9
\e9























\e9                               THE RAND MH

\e9                            MESSAGE HANDLING

\e9                                 SYSTEM:

\e9                              USER'S MANUAL






                               UCI Version





                            Marshall T. Rose

                             John L. Romine




                     Based on the original manual by

                       Borden, Gaines, and Shapiro







                            February 1, 1991

                             6.7.1a #6[UCI]

































































\e9
\e9