dovecot - May 2012 - BODYSTRUCTURE bug?

Hi! I've found a bug in Content-Type parsing. It's old instance of
dovecot 1.1. Maybe fixed in newer versions.

I have a mail with header:

Content-Type: multipart/signed;
 boundary="------------080705010808010608030700";
 protocol="application/x-pkcs7-signature";micalg="SHA1"

and it works, but when the boundary is in different order

Content-Type: multipart/signed;
 protocol="application/x-pkcs7-signature";micalg="SHA1";
 boundary="------------080705010808010608030700"

dovecot returns wrong BODYSTRUCTURE:

("text" "plain" ("charset" "us-ascii")
NIL NIL "7bit" 226233 2955 NIL
NIL NIL NIL)

If this has been fixed, in which version?

-- 
Aleksander 'A.L.E.C' Machniak
LAN Management System Developer [http://lms.org.pl]
Roundcube Webmail Developer  [http://roundcube.net]
---------------------------------------------------
PGP: 19359DC1 @@ GG: 2275252 @@ WWW: http://alec.pl

On 10.5.2012, at 11.54, A.L.E.C wrote:
> Hi! I've found a bug in Content-Type parsing. It's old instance of
> dovecot 1.1. Maybe fixed in newer versions.
> 
> I have a mail with header:
> 
> Content-Type: multipart/signed;
> boundary="------------080705010808010608030700";
> protocol="application/x-pkcs7-signature";micalg="SHA1"
> 
> and it works, but when the boundary is in different order
> 
> Content-Type: multipart/signed;
> protocol="application/x-pkcs7-signature";micalg="SHA1";
> boundary="------------080705010808010608030700"
> 
> dovecot returns wrong BODYSTRUCTURE:
> 
> ("text" "plain" ("charset"
"us-ascii") NIL NIL "7bit" 226233 2955 NIL
> NIL NIL NIL)
> 
> If this has been fixed, in which version?
This works fine in v1.0.15 and v1.1.20. Are you sure the problem is the order of
the parameters, and not that the second one is broken in some other way? Or I
guess it might be that in your specific version this is broken, but I don't
remember such bug.