On Wed, 2004-08-04 at 13:33, J.D. (Jack) Bitters wrote:
> Thought that there had to be a way that Exim, like Postfix, would
> automatically add a Message-ID to outgoing messages in those instances
> where (a) there was no original Message-ID, or (b) where the original
> Message-ID header was intentionally removed.
In your DATA acl, you could:
# Add Message-ID if missing in messages received from our own hosts.
warn
condition = ${if !def:h_Message-ID: {1}}
hosts = +relay_from_hosts
message = Message-ID: <E$message_id@$primary_hostname>
> Here are the two settings that I finally added at the end of the dnslookup
> router (before "no_more") to accomplish my goal:
>
> headers_remove = Message-ID
As others pointed out, this will break threading features in users'
MUAs.
> headers_add = Message-ID: <E$message_id@$primary_hostname>
>
> (Thank you Tor Slettnes http://slett.net/spam-filtering-for-mx/index.html
> for the last setting [although not exactly related to what I was looking
> for it did furnish half the answer].)
I think in its original context (that is, a "warn" statement in the DATA
acl), it would behave more closely to what you are looking for.
BTW, don't insert Message-ID: into mails received from other sites.
SpamAssassin works better if it is able to correctly identify that these
messages are missing this header.
> Anyways, now it works like a champ -- all Message-IDs are uniform.
> Will these two settings result in buggy behavior, burn up the
> motherboard, melt the polar ice caps, or am I safe?
Buggy behaviour: Yes
Burn up the motherboard: No
Melt the polar ice caps: Perhaps, if you receive lots of flames
Are you safe: Hm. Ambiguous question.
-tor
