The In-Reply-To:
header (?§25.12.21 on page 1158), for example, used to be a comma-separated
list of addresses under RFC733 and can cause problems. Note also that RFC733
date and time syntax differs from that of RFC2822 and RFC1123.
??? When generating an Apparently-To: header, sendmail checks for the absence of
only the To:, Cc:, Bcc:, and Apparently-To: headers. The H_RCPT flag (?§25.6.13
on page 1141) in conf.c is ignored. V8.7 and later sendmail will produce an
Apparently-To: header only if the NoRecipientAction option is set to addapparently-
to.
??? Precedence values are stored in integer variables, so care should be exercised on
2-byte integer machines to avoid having priorities wrap unexpectedly.
??? Macros are not expanded in the P command. That is, expressions such as $U do
not have the desired effect. The literal text $U is wrongly listed as the name or the
value.
??? Th e$={persistentMacros} class should not be used without first researching the
macros to be included in that class. The sendmail program can be harmed by
including an improper macro in that class because that macro??™s value will survive
queue runs. This creates a danger in the use of the H?${macro}? header
expression. The only way to use a sendmail program??™s internal macro in that
expression is by also including that macro in the $={persistentMacros} class.
Pages:
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072