5 .TH MH-MAIL %manext5% "%nmhdate%" MH.6.8 [%nmhversion%]
7 mh-mail \- message format for nmh message system
14 processes messages in a particular format. It should be noted
15 that although neither Bell nor Berkeley mailers produce message files
20 can read message files in that antiquated format.
22 Each user possesses a mail drop box which initially receives all messages
26 will read from that drop
27 box and incorporate the new messages found there into the user's own
28 mail folders (typically
29 .RI \*(lq +inbox \*(rq).
30 The mail drop box consists of one or more messages.
32 Messages are expected to consist of lines of text. Graphics and binary
33 data are not handled. No data compression is accepted. All text is
34 clear ASCII 7-bit data.
36 The general \*(lqmemo\*(rq framework of RFC\-822 is used. A message
37 consists of a block of information in a rigid format, followed by
38 general text with no specified format. The rigidly formatted first
39 part of a message is called the header, and the free-format portion is
40 called the body. The header must always exist, but the body is optional.
41 These parts are separated by an empty line, i.e., two consecutive newline
44 the header and body may be separated by a line consisting of dashes:
52 The header is composed of one or more header items. Each header item can
53 be viewed as a single logical line of ASCII characters. If the text of
54 a header item extends across several real lines, the continuation lines
55 are indicated by leading spaces or tabs.
57 Each header item is called a component and is composed of a keyword or
58 name, along with associated text. The keyword begins at the left margin,
59 may NOT contain spaces or tabs, may not exceed 63 characters (as specified
60 by RFC\-822), and is terminated by a colon (`:'). Certain components
61 (as identified by their keywords) must follow rigidly defined formats
62 in their text portions.
64 The text for most formatted components (e.g., \*(lqDate:\*(rq and
65 \*(lqMessage\-Id:\*(rq) is produced automatically. The only ones entered
66 by the user are address fields such as \*(lqTo:\*(rq, \*(lqcc:\*(rq,
67 etc. Internet addresses are assigned mailbox names and host computer
68 specifications. The rough format is \*(lqlocal@domain\*(rq, such as
69 \*(lqMH@UCI\*(rq, or \*(lqMH@UCI\-ICSA.ARPA\*(rq. Multiple addresses
70 are separated by commas. A missing host/domain is assumed to be the
73 As mentioned above, a blank line (or a line of dashes) signals that all
74 following text up to the end of the file is the body. No formatting is
75 expected or enforced within the body.
77 Following is a list of header components that are considered
86 contains date and time of the message's entry
87 into the mail transport system.
94 contains the address of the author or authors
95 (may be more than one if a \*(lqSender:\*(rq field is present). For a
98 the reply address is constructed by
99 checking the following headers (in this order): \*(lqMail-Reply\-To:\*(rq,
100 \*(lqReply\-To:\*(rq, \*(lqFrom:\*(rq, \*(lqSender:\*(rq.
103 .BR Mail\-Reply\-To :
105 For a standard reply (using
108 constructed by checking the following headers (in this order):
109 \*(lqMail-Reply\-To:\*(rq, \*(lqReply\-To:\*(rq, \*(lqFrom:\*(rq,
113 .BR Mail\-Followup\-To :
115 When making a \*(lqgroup\*(rq reply (using
118 any addresses in this field will take precedence, and no other reply address
119 will be added to the draft. If this header is not available, then the
120 return addresses will be constructed from the \*(lqMail-Reply\-To:\*(rq,
121 or \*(lqReply\-To:\*(rq, or \*(lqFrom:\*(rq, along with adding the
122 addresses from the headers \*(lqTo:\*(rq, \*(lqcc:\*(rq, as well as
123 adding your personal address.
128 For a standard reply (using
131 constructed by checking the following headers (in this order):
132 \*(lqMail-Reply\-To:\*(rq, \*(lqReply\-To:\*(rq, \*(lqFrom:\*(rq,
140 in the event that the message already has a
141 \*(lqFrom:\*(rq line. This line contains the address of the actual
147 Contains addresses of primary recipients.
152 Contains addresses of secondary recipients.
157 Still more recipients. However, the \*(lqBcc:\*(rq line is not
158 copied onto the message as delivered, so these recipients are not
161 uses an encapsulation method for blind copies, see
169 to copy the message into the specified folder for the sender,
170 if the message was successfully given to the transport system.
175 A unique message identifier added by
184 Sender's commentary. It is displayed by
190 A commentary line added by
192 when replying to a message.
197 Added when redistributing a message by
203 Added when redistributing a message by
209 New recipients for a message resent by
215 Still more recipients. See \*(lqcc:\*(rq and \*(lqResent\-To:\*(rq.
220 Even more recipients. See \*(lqBcc:\*(rq and \*(lqResent\-To:\*(rq.
225 Copy resent message into a folder.
226 See \*(lqFcc:\*(rq and \*(lqResent\-To:\*(rq.
229 .BR Resent\-Message\-Id :
231 A unique identifier glued on by
236 See \*(lqMessage\-Id:\*(rq and \*(lqResent\-To:\*(rq.
269 .ta \w'/usr/local/nmh/etc/ExtraBigFileName 'u
270 ^%mailspool%/$USER~^Location of mail drop
274 .I "Standard for the Format of ARPA Internet Text Messages