The field for this
header can be arbitrary text but is usually the value in the $x macro (?§21.9.103 on page
851):
H?x?Full-Name: $x
H?x?Full-Name: (User names hidden for security)
The Full-Name: header should be prefixed with the ?x? flag so that selected delivery agents
can require inclusion of that header. This heade0 Early versions of UUCP could not accept
full names in From: header lines:
From: host!user ( full name ) ?†? did not work for early UUCP
The Full-Name: header can be specified in the configuration file. If this header is already in
the mail message, sendmail does not replace it.
25.12.21 In-Reply-To:
Identify previous correspondence RFC2822
The In-Reply-To: header is used to identify previous correspondence that the current
message is in reply to. This header is generated by MUAs, not by sendmail. Prior to
RFC2822, the field for this header was arbitrary text with one restriction. If that text
included the message identifier, that identifier had to be enclosed in angle brackets (< and >)
and had to adhere to the format for all message identifiers.
Beginning withRFC2822, the In-Reply-To: header can contain only message identifiers,
each surrounded by angle braces, and each separated from the next by a comma.
A typical use of the In-Reply-To: header might look like the following:
In-Reply-To: <847.193925.
Pages:
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087