5 .\" include the -mh macro file
8 .TH MH-MAIL %manext5% MH.6.8 [%nmhversion%]
10 mh-mail \- message format for nmh message system
17 \fInmh\fR processes messages in a particular format. It should be noted
18 that although neither Bell nor Berkeley mailers produce message files
19 in the format that \fInmh\fR prefers, \fInmh\fR can read message files in
20 that antiquated format.
22 Each user possesses a mail drop box which initially receives all messages
23 processed by \fIpost\fR\0(8). \fIInc\fR\0(1) will read from that drop
24 box and incorporate the new messages found there into the user's own
25 mail folders (typically `+inbox'). The mail drop box consists of one
28 Messages are expected to consist of lines of text. Graphics and binary
29 data are not handled. No data compression is accepted. All text is
30 clear ASCII 7-bit data.
32 The general \*(lqmemo\*(rq framework of RFC\-822 is used. A message
33 consists of a block of information in a rigid format, followed by
34 general text with no specified format. The rigidly formatted first
35 part of a message is called the header, and the free-format portion is
36 called the body. The header must always exist, but the body is optional.
37 These parts are separated by an empty line, i.e., two consecutive newline
38 characters. Within \fInmh\fR, the header and body may be separated by
39 a line consisting of dashes:
45 .so %etcdir%/components
50 The header is composed of one or more header items. Each header item can
51 be viewed as a single logical line of ASCII characters. If the text of
52 a header item extends across several real lines, the continuation lines
53 are indicated by leading spaces or tabs.
55 Each header item is called a component and is composed of a keyword or
56 name, along with associated text. The keyword begins at the left margin,
57 may NOT contain spaces or tabs, may not exceed 63 characters (as specified
58 by RFC\-822), and is terminated by a colon (`:'). Certain components
59 (as identified by their keywords) must follow rigidly defined formats
60 in their text portions.
62 The text for most formatted components (e.g., \*(lqDate:\*(rq and
63 \*(lqMessage\-Id:\*(rq) is produced automatically. The only ones entered
64 by the user are address fields such as \*(lqTo:\*(rq, \*(lqcc:\*(rq,
65 etc. Internet addresses are assigned mailbox names and host computer
66 specifications. The rough format is \*(lqlocal@domain\*(rq, such as
67 \*(lqMH@UCI\*(rq, or \*(lqMH@UCI\-ICSA.ARPA\*(rq. Multiple addresses
68 are separated by commas. A missing host/domain is assumed to be the
71 As mentioned above, a blank line (or a line of dashes) signals that all
72 following text up to the end of the file is the body. No formatting is
73 expected or enforced within the body.
75 Following is a list of header components that are considered
76 meaningful to various nmh programs.
82 Added by \fIpost\fR\0(8), contains date and time of the message's entry
83 into the mail transport system.
88 Added by \fIpost\fR\0(8), contains the address of the author or authors
89 (may be more than one if a \*(lqSender:\*(rq field is present). For a
90 standard reply (using \fIrepl\fR), the reply address is constructed by
91 checking the following headers (in this order): \*(lqMail-Reply\-To:\*(rq,
92 \*(lqReply\-To:\*(rq, \*(lqFrom:\*(rq, \*(lqSender:\*(rq.
97 For a standard reply (using \fIrepl\fR), the reply address is
98 constructed by checking the following headers (in this order):
99 \*(lqMail-Reply\-To:\*(rq, \*(lqReply\-To:\*(rq, \*(lqFrom:\*(rq,
105 When making a \*(lqgroup\*(rq reply (using \fIrepl\fR -group), any
106 addresses in this field will take precedence, and no other reply address
107 will be added to the draft. If this header is not available, then the
108 return addresses will be constructed from the \*(lqMail-Reply\-To:\*(rq,
109 or \*(lqReply\-To:\*(rq, or \*(lqFrom:\*(rq, along with adding the
110 addresses from the headers \*(lqTo:\*(rq, \*(lqcc:\*(rq, as well as
111 adding your personal address.
116 For a standard reply (using \fIrepl\fR), the reply address is
117 constructed by checking the following headers (in this order):
118 \*(lqMail-Reply\-To:\*(rq, \*(lqReply\-To:\*(rq, \*(lqFrom:\*(rq,
124 Added by \fIpost\fR\0(8) in the event that the message already has a
125 \*(lqFrom:\*(rq line. This line contains the address of the actual
131 Contains addresses of primary recipients.
136 Contains addresses of secondary recipients.
141 Still more recipients. However, the \*(lqBcc:\*(rq line is not
142 copied onto the message as delivered, so these recipients are not
143 listed. \fInmh\fR uses an encapsulation method for blind copies, see
149 Causes \fIpost\fR\0(8) to copy the message into the specified folder for the
151 if the message was successfully given to the transport system.
156 A unique message identifier added by \fIpost\fR\0(8) if the `\-msgid' flag
162 Sender's commentary. It is displayed by \fIscan\fR\0(1).
167 A commentary line added by \fIrepl\fR\0(1) when replying to a message.
172 Added when redistributing a message by \fIpost\fR\0(8).
177 Added when redistributing a message by \fIpost\fR\0(8).
182 New recipients for a message resent by \fIdist\fR\0(1).
187 Still more recipients.
188 See \*(lqcc:\*(rq and \*(lqResent\-To:\*(rq.
193 Even more recipients.
194 See \*(lqBcc:\*(rq and \*(lqResent\-To:\*(rq.
199 Copy resent message into a folder.
200 See \*(lqFcc:\*(rq and \*(lqResent\-To:\*(rq.
205 A unique identifier glued on by \fIpost\fR\0(8) if the `\-msgid' flag
207 See \*(lqMessage\-Id:\*(rq and \*(lqResent\-To:\*(rq.
212 Annotation for \fIdist\fR\0(1) under the `\-annotate' option.
217 Annotation for \fIforw\fR\0(1) under the `\-annotate' option.
222 Annotation for \fIrepl\fR\0(1) under the `\-annotate' option.
226 ^%mailspool%/$USER~^Location of mail drop
230 RFC\-822:\fIStandard for the Format of ARPA Internet Text Messages\fR
projects / mmh / blob