At sites that have a central mail hub machine,
where client machines forward all mail to the hub, you can solve this problem by
redefining Message-ID: in conf.c on the clients, to delete the bogus Message-ID:, so
that a good one can be generated on the hub:
"message-id", 0,
"message-id", H_ACHECK, ?†? change to this
Here, we changed the 0 flag for the Message-ID: header into an H_ACHECK flag. We
do this only on the client machine versions of sendmail but not on the hub. The
Message-ID: header will then be stripped from every outgoing message on every client
machine and a new one will be created (if missing) on the hub.
By default, only the Full-Name:, Return-Path:, and Content-Length: headers have this
flag defined. The Message-ID: header does not have this flag defined by default
because the Message-ID: values are logged. By removing and regenerating Message-ID:
headers, you lose the ability to track any given message on the local machine and the
hub using a common Message-ID: value.*
H_TRACE ?§25.6.17 on page 1142 V5 and later Count these to get the hop count.
H_USER ?§25.6.18 on page 1142 V8.11 and later Came from a local user via SMTP.
H_VALID ?§25.6.19 on page 1142 V5 and later Has a validated field value.
* Some mail-sending programs also use Message-ID: headers of their own design to track messages.
Table 25-4. Header flags in conf.
Pages:
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055