1 .\" This file is automatically generated. Do not edit!
2 .\" @(#)$Id: mh-mail.rf,v 1.6 1992/05/12 22:23:34 jromine Exp $
5 mh-mail \- message format for MH message system
9 \fIMH\fR processes messages in a particular format.
10 It should be noted that although neither Bell nor Berkeley mailers produce
11 message files in the format that \fIMH\fR prefers,
12 \fIMH\fR can read message files in that antiquated format.
14 Each user possesses a mail drop box which initially receives
15 all messages processed by \fIpost\fR\0(8).
16 \fIInc\fR\0(1) will read from that drop box and incorporate the new messages
17 found there into the user's own mail folders (typically `+inbox').
19 box consists of one or more messages.
22 are expected to consist of lines of text.
23 Graphics and binary data are not handled.
24 No data compression is accepted.
28 The general \*(lqmemo\*(rq framework of RFC\-822 is used.
29 A message consists of a block of information in a rigid format,
30 followed by general text with no specified format.
31 The rigidly formatted first part of a message is called the header,
32 and the free-format portion is called the body.
33 The header must always exist, but the body is optional.
34 These parts are separated by an empty line,
35 i.e., two consecutive newline characters.
37 the header and body may be separated by a line consisting of dashes:
43 .so /opt/mh-6.8.5/lib/components
48 The header is composed of one or more header items.
49 Each header item can be viewed as a single logical line of ASCII
51 If the text of a header item extends across several
52 real lines, the continuation lines are indicated by leading
55 Each header item is called a component and is composed of a
56 keyword or name, along with associated text.
57 The keyword begins at the
58 left margin, may NOT contain spaces or tabs, may not exceed 63
59 characters (as specified by RFC\-822), and is terminated by a colon (`:').
61 components (as identified by their keywords) must follow rigidly
62 defined formats in their text portions.
64 The text for most formatted components
65 (e.g., \*(lqDate:\*(rq and \*(lqMessage\-Id:\*(rq)
66 is produced automatically.
67 The only ones entered by the
68 user are address fields such as \*(lqTo:\*(rq, \*(lqcc:\*(rq, etc.
70 are assigned mailbox names and host computer specifications.
72 rough format is \*(lqlocal@domain\*(rq, such as \*(lqMH@UCI\*(rq,
73 or \*(lqMH@UCI\-ICSA.ARPA\*(rq.
74 Multiple addresses are separated by commas.
75 A missing host/domain is assumed to be the local host/domain.
78 a blank line (or a line of dashes)
79 signals that all following text up to the end of the file is the body.
80 No formatting is expected or enforced within the body.
82 Following is a list of header components that are considered
83 meaningful to various MH programs.
88 Added by \fIpost\fR\0(8),
89 contains date and time of the message's entry into the transport system.
94 Added by \fIpost\fR\0(8),
95 contains the address of the author or authors (may be more than one if a
96 \*(lqSender:\*(rq field is present).
97 Replies are typically directed to addresses in the \*(lqReply\-To:\*(rq or
98 \*(lqFrom:\*(rq field (the former has precedence if present).
103 Added by \fIpost\fR\0(8)
104 in the event that the message already has a \*(lqFrom:\*(rq line.
105 This line contains the address of the actual sender.
106 Replies are never sent to addresses in the \*(lqSender:\*(rq field.
111 Contains addresses of primary recipients.
116 Contains addresses of secondary recipients.
121 Still more recipients.
122 However, the \*(lqBcc:\*(rq line is not copied onto the message as delivered,
123 so these recipients are not listed.
124 \fIMH\fR uses an encapsulation method for blind copies, see \fIsend\fR\0(1).
129 Causes \fIpost\fR\0(8) to copy the message into the specified folder for the
131 if the message was successfully given to the transport system.
136 A unique message identifier added by \fIpost\fR\0(8) if the `\-msgid' flag
142 Sender's commentary. It is displayed by \fIscan\fR\0(1).
147 A commentary line added by \fIrepl\fR\0(1) when replying to a message.
152 Added when redistributing a message by \fIpost\fR\0(8).
157 Added when redistributing a message by \fIpost\fR\0(8).
162 New recipients for a message resent by \fIdist\fR\0(1).
167 Still more recipients.
168 See \*(lqcc:\*(rq and \*(lqResent\-To:\*(rq.
173 Even more recipients.
174 See \*(lqBcc:\*(rq and \*(lqResent\-To:\*(rq.
179 Copy resent message into a folder.
180 See \*(lqFcc:\*(rq and \*(lqResent\-To:\*(rq.
185 A unique identifier glued on by \fIpost\fR\0(8) if the `\-msgid' flag
187 See \*(lqMessage\-Id:\*(rq and \*(lqResent\-To:\*(rq.
192 Annotation for \fIdist\fR\0(1) under the `\-annotate' option.
197 Annotation for \fIforw\fR\0(1) under the `\-annotate' option.
202 Annotation for \fIrepl\fR\0(1) under the `\-annotate' option.
206 ^/var/spool/mail/$USER~^Location of mail drop
210 \fIStandard for the Format of ARPA Internet Text Messages\fR (aka RFC\-822)
projects / mmh / blob