8 date 92.05.12.22.23.34; author jromine; state Exp;
13 date 90.04.05.15.13.12; author sources; state Exp;
18 date 90.03.22.11.31.18; author sources; state Exp;
23 date 90.03.20.19.41.56; author sources; state Exp;
28 date 90.03.20.17.36.12; author sources; state Exp;
33 date 90.03.20.17.20.56; author sources; state Exp;
44 @fixup for nroff problems
48 .\" @@(#)$Id: mh-mail.rf,v 1.5 1990/04/05 15:13:12 sources Exp jromine $
51 mh-mail \- message format for MH message system
55 \fIMH\fR processes messages in a particular format.
56 It should be noted that although neither Bell nor Berkeley mailers produce
57 message files in the format that \fIMH\fR prefers,
58 \fIMH\fR can read message files in that antiquated format.
60 Each user possesses a mail drop box which initially receives
61 all messages processed by \fIpost\fR\0(8).
62 \fIInc\fR\0(1) will read from that drop box and incorporate the new messages
63 found there into the user's own mail folders (typically `+inbox').
65 box consists of one or more messages.
68 separation of messages, each message begins and ends with
69 a line consisting of nothing but four CTRL\-A (octal 001)
74 separation of messages, each message begins and ends with
75 a line consisting of nothing but four CTRL\-A (octal 001)
80 are expected to consist of lines of text.
81 Graphics and binary data are not handled.
82 No data compression is accepted.
86 The general \*(lqmemo\*(rq framework of RFC\-822 is used.
87 A message consists of a block of information in a rigid format,
88 followed by general text with no specified format.
89 The rigidly formatted first part of a message is called the header,
90 and the free-format portion is called the body.
91 The header must always exist, but the body is optional.
92 These parts are separated by an empty line,
93 i.e., two consecutive newline characters.
95 the header and body may be separated by a line consisting of dashes:
101 .so @@(MHETCPATH)/components
106 The header is composed of one or more header items.
107 Each header item can be viewed as a single logical line of ASCII
109 If the text of a header item extends across several
110 real lines, the continuation lines are indicated by leading
113 Each header item is called a component and is composed of a
114 keyword or name, along with associated text.
115 The keyword begins at the
116 left margin, may NOT contain spaces or tabs, may not exceed 63
117 characters (as specified by RFC\-822), and is terminated by a colon (`:').
119 components (as identified by their keywords) must follow rigidly
120 defined formats in their text portions.
122 The text for most formatted components
123 (e.g., \*(lqDate:\*(rq and \*(lqMessage\-Id:\*(rq)
124 is produced automatically.
125 The only ones entered by the
126 user are address fields such as \*(lqTo:\*(rq, \*(lqcc:\*(rq, etc.
128 are assigned mailbox names and host computer specifications.
130 rough format is \*(lqlocal@@domain\*(rq, such as \*(lqMH@@UCI\*(rq,
131 or \*(lqMH@@UCI\-ICSA.ARPA\*(rq.
132 Multiple addresses are separated by commas.
133 A missing host/domain is assumed to be the local host/domain.
136 a blank line (or a line of dashes)
137 signals that all following text up to the end of the file is the body.
138 No formatting is expected or enforced within the body.
140 Following is a list of header components that are considered
141 meaningful to various MH programs.
146 Added by \fIpost\fR\0(8),
147 contains date and time of the message's entry into the transport system.
152 Added by \fIpost\fR\0(8),
153 contains the address of the author or authors (may be more than one if a
154 \*(lqSender:\*(rq field is present).
155 Replies are typically directed to addresses in the \*(lqReply\-To:\*(rq or
156 \*(lqFrom:\*(rq field (the former has precedence if present).
161 Added by \fIpost\fR\0(8)
162 in the event that the message already has a \*(lqFrom:\*(rq line.
163 This line contains the address of the actual sender.
164 Replies are never sent to addresses in the \*(lqSender:\*(rq field.
169 Contains addresses of primary recipients.
174 Contains addresses of secondary recipients.
179 Still more recipients.
180 However, the \*(lqBcc:\*(rq line is not copied onto the message as delivered,
181 so these recipients are not listed.
182 \fIMH\fR uses an encapsulation method for blind copies, see \fIsend\fR\0(1).
187 Causes \fIpost\fR\0(8) to copy the message into the specified folder for the
189 if the message was successfully given to the transport system.
194 A unique message identifier added by \fIpost\fR\0(8) if the `\-msgid' flag
200 Sender's commentary. It is displayed by \fIscan\fR\0(1).
205 A commentary line added by \fIrepl\fR\0(1) when replying to a message.
210 Added when redistributing a message by \fIpost\fR\0(8).
215 Added when redistributing a message by \fIpost\fR\0(8).
220 New recipients for a message resent by \fIdist\fR\0(1).
225 Still more recipients.
226 See \*(lqcc:\*(rq and \*(lqResent\-To:\*(rq.
231 Even more recipients.
232 See \*(lqBcc:\*(rq and \*(lqResent\-To:\*(rq.
237 Copy resent message into a folder.
238 See \*(lqFcc:\*(rq and \*(lqResent\-To:\*(rq.
243 A unique identifier glued on by \fIpost\fR\0(8) if the `\-msgid' flag
245 See \*(lqMessage\-Id:\*(rq and \*(lqResent\-To:\*(rq.
250 Annotation for \fIdist\fR\0(1) under the `\-annotate' option.
255 Annotation for \fIforw\fR\0(1) under the `\-annotate' option.
260 Annotation for \fIrepl\fR\0(1) under the `\-annotate' option.
264 ^@@(MHDROPLOC)~^Location of mail drop
268 \fIStandard for the Format of ARPA Internet Text Messages\fR (aka RFC\-822)
288 mh\-mail \- message format for MH message system
294 @put things back, do .NA stuff another way
308 .TH MH\-MAIL 5 @@(MHCENTERFOOT) @@(MHLEFTFOOT)
318 @fixup for makewhatis
323 .TH MH\-MAIL 5 [mh.6] MH
projects / mmh / blob