On Mon, 22 Nov 2004, Philip Chambers wrote:
> I have started to see messages arriving with blank Message-ID: headers and there
> appears to be a bug in exim's handling of them.
>
> exim is adding its own Message-ID: header as one would expect, but it is not
> removing the original blank one, so we end up with two Message-ID: headers, which
> results in an invalid header.
>
> Is there a quick fix I can put in my configuration or do I need a fix for the code?
Exim should add a Message-ID: header only if there is NO such header in
the message. It won't disturb an existing header, even if it is blank.
Furthermore, it only adds a Message-ID: header if the message is locally
submitted or if "submission mode" has been selected. (I'm talking about
the latest release, of course.)
I have just run a test, submitting a local message with an empty
Message-ID: header. Exim did nothing to it.
So, the question is, what is happening in your case? Which release of
Exim? Is your configuration trying to do things with Message-ID
manually? Note that if you have something like
${if eq{Message-ID:}{}{....
it won't distinguish between an empty Message-ID: and a non-existent
one. You need to use ${if def:h_message-ID: to check for existence.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book: http://www.uit.co.uk/exim-book
