mhn.man

早期freebsd实现

MHN(1)                 BSD Reference Manual                MHN(1)


       934 is being used.  If given, then RFC 934-compliant user-
       agents  should  be  able   to   burst   the   message   on
       reception -- providing  that  the  messages being encapsu-
       lated do not  contain  encapsulated  messages  themselves.
       The  drawback  of this approach is that the encapsulations
       are generated by placing an extra newline at  the  end  of
       the body of each message.

       For  the  begin  directive, the user must specify at least
       one content between the begin and end pairs.

       For all of these directives, the user may include a  brief
       description  of  the content between the "[" character and
       the "]" character.  By default, _m_h_n will generate a unique
       "Content-ID:"  for  each  directive; however, the user may
       override this by defining the ID using  the  "<"  and  ">"
       characters.   Putting  this  all together, here is a brief
       example of what a user's components file might look like:

            To:
            cc:
            Subject:
            --------
            #audio/basic [Flint phone]  \
                |raw2audio -F < /home/mrose/lib/multi-media/flint.au
            #image/gif   [MTR's photo] \
                                /home/mrose/lib/multi-media/mrose.gif

       For a later example, we'll call this components file  _m_h_n_-
       _c_o_m_p_s.

       As noted earlier, in addition to directives, plaintext can
       be present.  Plaintext is gathered, until a  directive  is
       found  or the draft is exhausted, and this is made to form
       a text content.  If the plaintext must contain  a  "#"  at
       the beginning of a line, simply double it, e.g.,

            ##when sent, this line will start with only one #

       If  you  want  to  end the plaintext prior to a directive,
       e.g., to have  two  plaintext  contents  adjacent,  simply
       insert a line containing a single "#" character, e.g.,

            this is the first content
            #
            and this is the second

       Finally, if the plaintext starts with a line of the form:

            Content-Description: text




[mh.6]                        MH.6.8                           13








MHN(1)                 BSD Reference Manual                MHN(1)


       then  this will be used to describe the plaintext content.
       NNOOTTEE WWEELLLL:: you must follow this line  with  a  blank  line
       before starting your text.

       By default, plaintext is captured as a text/plain content.
       You can override this by starting the plaintext with  "#<"
       followed by a content-type specification, e.g.,

            #<text/richtext
            this content will be tagged as text/richtext
            #
            and this content will be tagged as text/plain

       Note  that  if  you  use the "#<" plaintext-form, then the
       content-description must be on the same line which identi-
       fies the content type of the plaintext.

       If  _m_h_n  is  successful,  it renames the original draft to
       start with the ","  character  and  end  with  the  string
       ".orig",  e.g.,  if  you  are editing the file "draft", it
       will be renamed to ",draft.orig".  This allows you to eas-
       ily recover the _m_h_n composition file.

       If  the  `-check'  switch  is given, _m_h_n will associate an
       integrity check with each content.


   AAuuttoommaattiicc CCoommppoossiittiioonn
       Note that MH will not invoke _m_h_n automatically, unless you
       add this line to your .mh_profile file:

            automhnproc: mhn

       Otherwise, you must specifically give the command

            What now? edit mhn

       prior to sending the draft.

       You  can easily tailor MH to help you remember to do this.
       Suppose you have these lines in your profile:

            mcomp:          -editor mprompter -form mhncomps
            mprompter:      -noprepend -norapid
            mprompter-next: mhn

       where _m_c_o_m_p is a link to _c_o_m_p (1), and _m_p_r_o_m_p_t_e_r is a link
       to  _p_r_o_m_p_t_e_r (1).   Then  to send a message using the _m_h_n_-






[mh.6]                        MH.6.8                           14








MHN(1)                 BSD Reference Manual                MHN(1)


       _c_o_m_p_s components file above, the sequence is:

            % mmccoommpp
            To: uusseerr@@hhoosstt
            cc:
            Subject: mmuullttii--mmeeddiiaa mmeessssaaggee
            --------
            #audio/basic [Flint phone]  \
                |raw2audio -F < /home/mrose/lib/multi-media/flint.au
            #image/gif   [MTR's photo] \
                                /home/mrose/lib/multi-media/mrose.gif

            --------Enter additional text

            TThhiiss mmeessssaaggee ccoonnttaaiinnss tthhrreeee ccoonntteennttss..
            <<CCTTRRLL--DD>>
            --------

            What now? eeddiitt (this invokes _m_h_n)

            What now? sseenndd

       You have to remember to type the additional edit  command,
       but it should be fairly obvious from the interaction.

       Finally, you should consider adding this line to your pro-
       file:

            lproc: show

       This way, if you decide to lliisstt after invoking _m_h_n as your
       editor, the command

            What now? list

       will work as you expect.


   SSeennddiinngg FFiilleess vviiaa MMaaiill
       When you want to send a bunch of files to someone, you can
       run the _v_i_a_m_a_i_l shell script, which is similar the tarmail
       command:

            /usr/contrib/mh-6.8/lib/viamail   mailpath  "subject"
            files ...

       _v_i_a_m_a_i_l will archive the directories/files you  name  with
       _t_a_r (1),  and  then  mail  the  compressed  archive to the
       `mailpath' with the given `subject'.  The archive will  be
       automatically  split up into as many messages as necessary
       in order to get past most mailers.



[mh.6]                        MH.6.8                           15








MHN(1)                 BSD Reference Manual                MHN(1)


       Sometimes you want _v_i_a_m_a_i_l to pause after posting  a  par-
       tial  message.  This is usually the case when you are run-
       ning _s_e_n_d_m_a_i_l and expect to generate a lot of partial mes-
       sages.  If the first argument given to _v_i_a_m_a_i_l starts with
       a dash, then it is interpreted as the number of seconds to
       pause in between postings, e.g.,

            /usr/contrib/mh-6.8/lib/viamail  -300  mailpath "sub-
            ject" files ...

       will pause 5 minutes in between each posting.

       When these messages are received, invoke  _m_h_n  once,  with
       the  list  of messages, and the `-store' command.  The _m_h_n
       program will then store exactly one message containing the
       archive.   You  can  then  use  `-show' to find out what's
       inside;  possibly   followed  by  `-store'  to  write  the
       archive  to  a  file where you can subsequently uncompress
       and untar it, e.g.,

            % mhn -list all
             msg part  type/subtype             size description
               1       message/partial           47K part 1 of 4
               2       message/partial           47K part 2 of 4
               3       message/partial           47K part 3 of 4
               4       message/partial           18K part 4 of 4
            % mhn -store all
            % mhn -list -verbose last
             msg part  type/subtype             size description
               5       application/octet-stream 118K
                         (extract with uncompress | tar xvpf -)
                         type=tar
                         x-conversions=compress
            % mhn -show last
             msg part  type/subtype             size description
               5       application/octet-stream 118K
            -- headers of message, followed by _t_a_r listing appears here
            % mhn -store last
            % uncompress < 5.tar.Z | tar xvpf -

       Alternately, by using the `-auto' switch, _m_h_n  will  auto-













[mh.6]                        MH.6.8                           16








MHN(1)                 BSD Reference Manual                MHN(1)


       matically do the extraction for you, e.g.,

            % mhn -list all
             msg part  type/subtype             size description
               1       message/partial           47K part 1 of 4
               2       message/partial           47K part 2 of 4
               3       message/partial           47K part 3 of 4
               4       message/partial           18K part 4 of 4
            % mhn -store all
            % mhn -list -verbose last
             msg part  type/subtype             size description
               5       application/octet-stream 118K
                         (extract with uncompress | tar xvpf -)
                         type=tar
                         x-conversions=compress
            % mhn -show last
             msg part  type/subtype             size description
               5       application/octet-stream 118K
            -- headers of message, followed by _t_a_r listing appears here
            % mhn -store -auto last
            -- _t_a_r listing appears here as files are extracted

       As  the  second  _t_a_r  listing  is generated, the files are
       extracted.  A prudent user will never put `-auto'  in  the
       .mh_profile  file.   The correct procedure is to first use
       `-show', to find out what will be extracted.  Then _m_h_n can
       be  invoked  with   `-store'  and  `-auto'  to perform the
       extraction.


   UUsseerr EEnnvviirroonnmmeenntt
       Because the display environment in which _m_h_n operates  may
       vary  for  a user, _m_h_n will look for the environment vari-
       able $$MMHHNN.  If present, this  specifies  the  name  of  an
       additional user profile which should be read.  Hence, when
       a user logs in on a particular display device, this  envi-
       ronment variable should be set to refer to a file contain-
       ing definitions useful for the display device.   Normally,
       only entries of the form

            mhn-show-<type>/<subtype>
            mhn-show-<type>

       need be present.  Finally, _m_h_n will attempt to consult one
       other additional user profile, e.g.,

            /usr/contrib/mh-6.8/lib/mhn_defaults

       which is created automatically during MH installation.





[mh.6]                        MH.6.8                           17








MHN(1)                 BSD Reference Manual                MHN(1)


FFIILLEESS
       $HOME/.mh_profile                         The user profile
       $MHN                                      Additional profile entries
       /usr/contrib/mh-6.8/lib/mhn_defaults      System-default profile entries
       /usr/contrib/mh-6.8/lib/mhl.headers       The headers template

PPRROOFFIILLEE CCOOMMPPOONNEENNTTSS
       Path:                To determine the user's MH directory
       Current-Folder:      To find the default current folder
       mhlproc:             Default program to display message headers
       mhn-access-ftp:      Program to retrieve contents via FTP
       mhn-cache            Public directory to store cached external contents
       mhn-charset-<charset>Template for environment to render character sets
       mhn-compose-<type>*  Template for composing contents
       mhn-private-cache    Personal directory to store cached external contents
       mhn-show-<type>*     Template for displaying contents
       mhn-storage          Directory to store contents
       mhn-store-<type>*    Template for storing contents
       moreproc:            Default program to display text/plain content

SSEEEE AALLSSOO
       mhl(1)
       _M_I_M_E_: _M_e_c_h_a_n_i_s_m_s _f_o_r _S_p_e_c_i_f_y_i_n_g _a_n_d _D_e_s_c_r_i_b_i_n_g _t_h_e  _F_o_r_m_a_t
       _o_f _I_n_t_e_r_n_e_t _M_e_s_s_a_g_e _B_o_d_i_e_s (RFC 1521),
       _P_r_o_p_o_s_e_d _S_t_a_n_d_a_r_d _f_o_r _M_e_s_s_a_g_e _E_n_c_a_p_s_u_l_a_t_i_o_n (RFC 934).

DDEEFFAAUULLTTSS
       `+folder' defaults to the current folder
       `msgs' defaults to cur
       `-noauto'
       `-nocache'
       `-nocheck'
       `-noebcdicsafe'
       `-form mhl.headers'
       `-headers'
       `-pause'
       `-rcache ask'
       `-realsize'
       `-rfc934mode'
       `-noserialonly'
       `-show'
       `-noverbose'
       `-wcache ask'

CCOONNTTEEXXTT
       If  a  folder is given, it will become the current folder.
       The last message selected will become the current message.

BBUUGGSS
       Partial  messages contained within a multipart content are
       not reassembled with the `-store' switch.



[mh.6]                        MH.6.8                           18