This is
useful for separating RFC2822-compliant header lines from headers created by a
noncompliant network.
25.6.10 H_ERRORSTO (Was H_ERRSTO) (V8.7 and Later)
The H_ERRSTO (V6 and earlier) and H_ERRORSTO (V7 and later) flags specify
which headers can be used for returning error notification mail. Those headers take
priority over all others for that notification if the UseErrorsTo option is true
(?§24.9.126 on page 1115).
25.6.11 H_FORCE Header Flag (V5 and Later)
The H_FORCE flag causes sendmail to always insert a header. It is used in the conf.c
file withselected trace and X-Authentication-Warning: headers. It can be thought of
as allowing duplicates. That is, the header will be inserted even if one like it is
already present.
25.6.12 H_FROM Header Flag (V5 and Later)
Headers that are marked with the H_FROM flag are assumed to contain a valid
sender address. This flag is intended for use in the conf.c file.
25.6.13 H_RCPT Header Flag (V5 and Later)
Headers that are marked with the H_RCPT flag are assumed to contain valid recipient
addresses in their fields. Only headers with this flag can lead to message delivery.
These addresses will be rewritten. These headers are used to determine the recipient
address only if the -t command-line switch (?§6.7.44 on page 248) is used.
25.6.14 H_RECEIPTTO Header Flag (V8.7 and Later)
Some headers contain information about to whom a return receipt should be sent.
Pages:
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058