Re: [exim] Handling malformed header fields

Top Page
Delete this message
Reply to this message
Author: Ian Eiloart
Date:  
To: Murray S. Kucherawy, exim-users
Subject: Re: [exim] Handling malformed header fields


--On 24 October 2010 22:21:26 -0700 "Murray S. Kucherawy"
<msk@???> wrote:

>> -----Original Message-----
>> From: exim-users-bounces@??? [mailto:exim-users-bounces@exim.org]
>> On Behalf Of Andreas Metzler Sent: Saturday, October 23, 2010 1:57 AM
>> To: exim-users@???
>> Subject: Re: [exim] Handling malformed header fields
>
> Hi Andreas,
>
>> In both cases the broken header is interpreted as the first body
>> line. (In case somebody is wondering: verify = header_syntax does not
>> make a difference.)
>
> Thanks, that's useful information. In terms of the data collected so
> far, exim does the same as all the other respondents in the first case,
> but they're the only one that does that in the second case; everyone else
> eats the errant space, as it has no semantic value according to RFC5322,
> and sends it on thus modified.
>
> Cheers,
> -MSK


Actually, my Exim installation treats the errors differently. We add
headers to all messages, at the end of the header list.

In the first case, the line "This is not a header field", and all
subsequent headers are actually forced into the message body by inserting
the additional headers, and an empty line, before that line. Also, some fix
ups may be required if late headers include Date: Message-Id:, etc. I get
this result:

    Date: Mon, 25 Oct 2010 11:34:16 +0100
    Message-Id: <ELAUDCY-000CE7-OY@???>
    From: foo@bar
    To: baz@blivit
    X-Sussex: true
    X-Sussex-transport: remote_lmtp


    This is not a header field
    Subject: ha ha I fooled you
    Date: Fri, 22 Oct 2010 11:08:22 -0700


    This is where the body is



In the second case, that doesn't happen, I get this result:

    Message-Id: <ELAUDC1-000CE7-EO@???>
    From: foo@bar
    To: baz@blivit
    MIME-Version : 1.0
    Subject: did you notice that extra space?
    Date: Fri, 22 Oct 2010 11:08:22 -0700
    X-Sussex: true
    X-Sussex-transport: remote_lmtp


    This is where the body is


In both cases, I pasted the example text into the DATA phase of a telnet
session, with no additional headers.

--
Ian Eiloart
IT Services, University of Sussex
01273-873148 x3148
For new support requests, see http://www.sussex.ac.uk/its/help/