12.8 on page 1153); the Content-Id:
header (?§25.12.9 on page 1153); the Content-Transfer-Encoding: header (?§25.12.11 on
page 1154); the Content-Type: header (?§25.12.12 on page 1154); and the MIME-Version:
header (?§25.12.26 on page 1160). You can add more headers with the C or F configuration
file command.
If any of these headers are found to be too long, they are truncated to the length specified
by the MaxMimeHeaderLength option (?§24.9.69 on page 1047). Note that this truncation is
done carefully so as to maintain the appearance of an RFC2822-legal header.
22.6.4 $={checkMIMETextHeaders}
MIME headers for maximum arbitrary length checking V8.10 and later
Beginning withV8.10 sendmail, th eMaxMimeHeaderLength option (?§24.9.69 on page 1047)
can be used to define the maximum length for selected MIME headers that present text
descriptions. Before making that check, sendmail looks to see whether a particular header is
in the class $={checkMIMETextHeaders}. If it isn??™t, sendmail skips this length check.
When V8.10 sendmail starts up, it predefines the $={checkMIMETextHeaders} class to contain
the single MIME header Content-Description: header (?§25.12.7 on page 1153). You can
add more headers with the C or F configuration file command.
If this header??™s value is found to be too long, it is truncated to the length specified by the
MaxMimeHeaderLength option.
Pages:
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538