H_STRIPCOMM ?§25.6.16 on page 1142 V8.10 and later Strip comments for header checks.
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 | 1139
Note that there is no flag that always causes a particular header to be removed, nor is
there a flag that always causes a particular header to be replaced (but see ?§25.6.1.1
for one way around this limitation).
25.6.1 H_ACHECK Header Flag (V5 and Later)
The H_ACHECK flag marks a header that should normally be discarded unless a
delivery agent??™s F= flag calls for its inclusion. It is usually set for the Bcc: header,
which is discarded for the privacy of a blind carbon copy list, and the Full-Name:
header, which is intended as a way for a user to add a full name (see the $x macro,
?§21.9.103 on page 851) when there is no full name defined in the passwd(5) file.
Note that H_ACHECK, when combined with bogus ?flags? of a header configuration
file declaration, can cause appropriate headers to always be deleted or replaced.
Also note that under V8 sendmail, the H_ACHECK flag alone always causes a header
to be replaced.
25.6.1.1 Replace headers with H_ACHECK
Some MUAs tend to insert their own Message-ID: header (?§25.12.24 on page 1159).
This can cause difficulty when tracing email problems because those MUA headers
lack the sendmail queue identifier.
Pages:
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054