4 .TH MH-MAIL %manext5% "%nmhdate%" MH.6.8 [%nmhversion%]
6 mh-mail \- message format for nmh message system
9 processes messages in a particular format. It should be noted
10 that although neither Bell nor Berkeley mailers produce message files
15 can read message files in that antiquated format.
17 Each user possesses a system maildrop box which initially receives all
18 messages delivered by the MTA.
20 will read from that maildrop
21 and incorporate the new messages found there into the user's own
22 mail folders (typically
25 Messages are expected to consist of lines of text. Graphics and binary
26 data are not directly handled. No data compression is accepted. All text is
27 clear ASCII 7-bit data.
29 The general `memo' framework of RFC\-822 is used. A message
30 consists of a block of information in a rigid format, followed by
31 general text with no specified format. The rigidly formatted first
32 part of a message is called the header, and the free-format portion is
33 called the body. The header must always exist, but the body is optional.
34 These parts are separated by an empty line, i.e., two consecutive newline
37 the header and body may be separated by a line consisting of dashes:
45 The header is composed of one or more header items. Each header item can
46 be viewed as a single logical line of ASCII characters. If the text of
47 a header item extends across several real lines, the continuation lines
48 are indicated by leading spaces or tabs.
50 Each header item is called a component and is composed of a keyword or
51 name, along with associated text. The keyword begins at the left margin,
52 may NOT contain spaces or tabs, may not exceed 63 characters (as specified
53 by RFC\-822), and is terminated by a colon (`:'). Certain components
54 (as identified by their keywords) must follow rigidly defined formats
55 in their text portions.
57 The text for most formatted components (e.g., `Date:' and
58 `Message\-Id:') is produced automatically. The only ones entered
59 by the user are address fields such as `To:', `Cc:',
60 etc. Internet addresses are assigned mailbox names and host computer
61 specifications. The rough format is `local@domain', such as
62 `bob@example.org'. Multiple addresses
63 are separated by commas. A missing host/domain is assumed to be the
66 As mentioned above, a blank line (or a line of dashes) signals that all
67 following text up to the end of the file is the body. No formatting is
68 expected or enforced within the body.
70 Following is a list of header components that are considered
79 Contains date and time of the message's entry
80 into the mail transport system.
87 Contains the address of the author or authors
88 (may be more than one if a `Sender:' field is present). For a
91 the reply address is constructed by
92 checking the following headers (in this order): `Mail-Reply\-To:',
93 `Reply\-To:', `From:', `Sender:'.
98 For a standard reply (using
101 constructed by checking the following headers (in this order):
102 `Mail-Reply\-To:', `Reply\-To:', `From:',
106 .BR Mail\-Followup\-To :
108 When making a `group' reply (using
111 any addresses in this field will take precedence, and no other reply address
112 will be added to the draft. If this header is not available, then the
113 return addresses will be constructed from the `Mail-Reply\-To:',
114 or `Reply\-To:', or `From:', along with adding the
115 addresses from the headers `To:', `Cc:', as well as
116 adding your personal address.
121 For a standard reply (using
124 constructed by checking the following headers (in this order):
125 `Mail-Reply\-To:', `Reply\-To:', `From:',
133 in the event that the message already has a
134 `From:' line. This line contains the address of the actual
140 Contains addresses of primary recipients.
145 Contains addresses of secondary recipients.
150 Still more recipients. However, the `Bcc:' line is not
151 copied onto the message as delivered, so these recipients are not
154 uses an encapsulation method for blind copies, see
164 to copy the message into the specified folder for the sender,
165 if the message was successfully given to the transport system.
170 A unique message identifier added by the MTA.
175 Sender's commentary. It is displayed by
181 A commentary line added by
183 when replying to a message.
188 Added when redistributing a message by
194 Added when redistributing a message by
200 New recipients for a message resent by
206 Still more recipients. See `Cc:' and `Resent\-To:'.
211 Even more recipients. See `Bcc:' and `Resent\-To:'.
216 Copy resent message into a folder.
217 See `Fcc:' and `Resent\-To:'.
220 .BR Resent\-Message\-Id :
222 A unique identifier glued on by the MTA.
223 See `Message\-Id:' and `Resent\-To:'.
226 The following non-standard header components are also meaningful to
234 to attach the given file to the message being sent.
267 .ta \w'%etcdir%/ExtraBigFileName 'u
268 ^%mailspool%/$USER~^Location of mail drop
272 .I "Standard for the Format of ARPA Internet Text Messages