All rights reserved.
25.12 Alphabetized Header Reference | 1153
The Comments: header should rarely be declared in the configuration file. If it is, it should
be prefixed with appropriate ?flags?. For example:
H?B?Comments: Local delivery is experimentally being handled
by a new program. Complaints to root.
This comment is included only in headers that are delivered via the local delivery agent
because that delivery agent is the only one to include the F=B flag:
Mlocal, P=/bin/mail, F=rlsDFMmnPB, S=10, R=20, A=mail -d $u
This declaration causes the new Comment: header to be added to the mail message.
25.12.7 Content-Description:
Description of MIME message or part RFC2145
The MIME Content-Description: header describes the content of the MIME message, or in
a multipart MIME message the content of a part. The value portion of this header is
unstructured text. For example, a MIME-encapsulated image might contain this header:
Content-Description: Your cousin's new son's picture taken at the hospital.
25.12.8 Content-Disposition:
How MIME contents should be disposed RFC2183
The MIME Content-Disposition: header specifies how a MIME attached file should be
handled. The form of the Content-Disposition: header looks like this:
Content-Disposition: type; parameter=value ...
Here, the value for this header is a sequence of one or more equates, each separated from
the others by a semicolon and one or more space or tab characters.
Pages:
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077