7 and Later)
The H_CTE flag specifies that a header is the MIME RFC2045 content transfer
encoding header (?§25.12.11 on page 1154).
25.6.6 H_CTYPE Header Flag (V8.7 and Later)
The H_CTYPE flag specifies that a header is a MIME RFC2045 content-type header
(?§25.12.12 on page 1154).
25.6.7 H_DEFAULT Header Flag (V5 and Later)
The sendmail program automatically sets the H_DEFAULT flag for all headers
declared in the configuration file. This flag tells sendmail to macro-expand the header
just before it is used. Only one of each header that is marked with this flag is allowed
to exist in the headers portion of a mail message. If such a header already exists,
sendmail does not add another. The H_FORCE and H_TRACE flags override this
flag in that regard. This flag must never be specified in conf.c??”it is set automatically
by the H configuration command (?§25.1 on page 1120).
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc. All rights reserved.
25.6 Header Behavior in conf.c | 1141
25.6.8 H_ENCODABLE Header Flag (V8.8 and Later)
The H_ENCODABLE flag tells sendmail that the field part can be encoded in the
way described in RFC2047. As of V8.10, this flag is defined for the Comment: and
Subject: headers. Prior to that, it was defined for no headers.
25.6.9 H_EOH Header Flag (V5 and Later)
Headers that are marked with the H_EOH flag cause sendmail to immediately stop
all header processing and treat the rest of the header lines as message body.
Pages:
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057