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