[Dovecot] Possible header parsing problem

[Timo Sirainen]

On Wed, 2008-10-22 at 20:59 -0600, Eric Stadtherr wrote:
>     Content-Type: multipart/alternative; boundary="=_alternative
>       006F3A73872574E8_="

Is there one space, two spaces or a TAB at the beginning of the second
line?

> I did a little bit of tracing through the parsing code 
> (message-header-parser.c:message_parse_header_next()) and it appeared 
> that the boundary in the Content-Type header was not parsed correctly, 
> evidently because the header line was folded in the middle of the 
> boundary string. RFC 822 appears to allow folding in a quoted string 
> like this (§3.3 "quoted-string"), so I'm curious whether the parsing is 
> working correctly.

Fixed: http://hg.dovecot.org/dovecot-1.1/rev/25b0cf7c62d3

But I'm not sure if I should convert the following TAB to a space.
UW-IMAP seems to do that, but RFC just says that the CRLF should be
dropped.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://dovecot.org/pipermail/dovecot/attachments/20081023/e9b66ed7/attachment.bin