mh-mail.man

早期freebsd实现

MH-MAIL(5)           BSD Programmer's Manual           MH-MAIL(5)


NNAAMMEE
       mh-mail - message format for MH message system

SSYYNNOOPPSSIISS
       any _M_H command

DDEESSCCRRIIPPTTIIOONN
       _M_H  processes  messages in a particular format.  It should
       be noted that although neither Bell nor  Berkeley  mailers
       produce  message  files  in the format that _M_H prefers, _M_H
       can read message files in that antiquated format.

       Each user  possesses  a  mail  drop  box  which  initially
       receives all messages processed by _p_o_s_t (8).  _I_n_c (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 mes-
       sages.

       Messages are expected to consist of lines of text.  Graph-
       ics 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 mes-
       sage consists of a block of information in a rigid format,
       followed  by  general  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 con-
       secutive newline characters.  Within _M_H,  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  key-
       word  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.



[mh.6]                        MH.6.8                            1








MH-MAIL(5)           BSD Programmer's Manual           MH-MAIL(5)


       The  text for most formatted components (e.g., "Date:" and
       "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  specifications.   The rough format is
       "local@domain", such as "MH@UCI",  or  "[e-mail]".
       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 formatting is expected or enforced within
       the body.

       Following  is a list of header components that are consid-
       ered meaningful to various MH programs.
       Date:
            Added by _p_o_s_t (8), contains date and time of the mes-
            sage's entry into the transport system.

       From:
            Added by _p_o_s_t (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  _p_o_s_t (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.  _M_H uses an  encapsulation
            method for blind copies, see _s_e_n_d (1).

       Fcc:
            Causes  _p_o_s_t (8)  to copy the message into the speci-
            fied folder for the sender, if the message  was  suc-
            cessfully given to the transport system.

       Message-ID:



[mh.6]                        MH.6.8                            2








MH-MAIL(5)           BSD Programmer's Manual           MH-MAIL(5)


            A  unique message identifier added by _p_o_s_t (8) if the
            `-msgid' flag is set.

       Subject:
            Sender's commentary.  It is displayed by _s_c_a_n (1).

       In-Reply-To:
            A commentary line added by _r_e_p_l (1) when replying  to
            a message.

       Resent-Date:
            Added when redistributing a message by _p_o_s_t (8).

       Resent-From:
            Added when redistributing a message by _p_o_s_t (8).

       Resent-To:
            New recipients for a message resent by _d_i_s_t (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  _p_o_s_t (8)  if  the
            `-msgid'   flag   is   set.   See  "Message-Id:"  and
            "Resent-To:".

       Resent:
            Annotation for _d_i_s_t (1) under the `-annotate' option.

       Forwarded:
            Annotation for _f_o_r_w (1) under the `-annotate' option.

       Replied:
            Annotation for _r_e_p_l (1) under the `-annotate' option.


FFIILLEESS
       /var/mail/$USER                           Location of mail drop

PPRROOFFIILLEE CCOOMMPPOONNEENNTTSS
       None





[mh.6]                        MH.6.8                            3








MH-MAIL(5)           BSD Programmer's Manual           MH-MAIL(5)


SSEEEE AALLSSOO
       _S_t_a_n_d_a_r_d  _f_o_r  _t_h_e  _F_o_r_m_a_t  _o_f _A_R_P_A _I_n_t_e_r_n_e_t _T_e_x_t _M_e_s_s_a_g_e_s
       (aka RFC-822)

DDEEFFAAUULLTTSS
       None

CCOONNTTEEXXTT
       None













































[mh.6]                        MH.6.8                            4