3 qmail-header \- format of a mail message
5 At the top of every mail message is a
8 Many programs expect the header to carry certain information,
12 is to make sure that each outgoing message has an appropriate header.
14 For more detailed information, see RFC 822 and RFC 1123.
15 .SH "MESSAGE STRUCTURE"
16 A message contains a series of
23 Received: (qmail-queue invoked by uid 666);
25 30 Jul 1996 11:54:54 -0000
27 From: djb@silverton.berkeley.edu (D. J. Bernstein)
29 To: fred@silverton.berkeley.edu
31 Date: 30 Jul 1996 11:54:54 -0000
37 I've got money on this one. How about you?
41 ---Dan (this is the third line of the body)
44 Each header field has a
55 The field contents may be folded across several lines.
56 Each line past the first must begin with a space or tab:
59 Received: (qmail-queue invoked by uid 666);
61 30 Jul 1996 11:54:54 -0000
64 The field name must not contain spaces, tabs, or colons.
65 Also, an empty field name is illegal.
67 does not allow field names with unprintable characters.
69 Case is irrelevant in field names:
75 have the same meaning.
77 Certain fields, such as
82 An address list contains some number of
89 a@b, c@d (Somebody), A Person <e@f>,
91 random group: g@h, i@j;, k@l
96 has some text, a colon, a list of addresses,
100 random group: g@h, i@j;
103 An address can appear in several forms.
104 The most common form is
107 Every address must include a host name.
112 .I default host name\fR.
114 All host names should be fully qualified.
117 .I default domain name
118 to any name without dots:
121 djb@silverton -> djb@silverton.berkeley.edu
127 that ends with a plus sign:
130 eric@mammoth.cs+ -> eric@mammoth.cs.berkeley.edu
133 A host name may be a dotted-decimal address:
139 RFC 822 allows mailbox names inside angle brackets
144 strips all source routes out of addresses.
145 .SH "SENDER ADDRESSES"
147 looks for sender address lists in the following fields:
152 .BR Return-Receipt-To ,
156 .BR Resent-Reply-To .
164 field with the name of the user invoking
167 RFC 822 requires that certain sender fields contain
168 only a single address, but
170 does not enforce this restriction.
171 .SH "RECIPIENT ADDRESSES"
173 looks for recipient address lists in the following fields:
182 Every message must contain at least one
201 Cc: recipient list not shown: ;
204 This complies with RFC 822;
205 it also works around some strange
207 behavior, in case the message is passed through
211 Every message must contain a
213 field, with the date in a strict format defined by RFC 822.
218 field with the current date (in GMT).
220 Every message should contain a
223 The field contents are a unique worldwide identifier for this message.
230 Another important field is
232 Every time the message is sent from one system to another,
235 field is added to the top of the message.
240 .SH "RESENT MESSAGES"
243 if it contains any of the following fields:
246 .BR Resent-Reply-To ,
251 .BR Resent-Message-ID .
253 If a message is forwarded,
255 changes its behavior as follows.
259 field (as well as any
298 if one is not already present;
300 .BR Resent-Message-Id .
309 Addresses are separated by commas, not spaces.
312 sees an illegal space,
316 djb fred -> djb, fred