Re: [Dovecot] Possible header parsing problem

2008-10-27 Thread Eric Stadtherr
On Tue, 28 Oct 2008 03:31:13 +0200, Timo Sirainen <[EMAIL PROTECTED]> wrote: > On Oct 28, 2008, at 3:23 AM, Eric Stadtherr wrote: > >>> 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,

Re: [Dovecot] Possible header parsing problem

2008-10-27 Thread Timo Sirainen
On Oct 28, 2008, at 3:23 AM, Eric Stadtherr wrote: 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. I grabbed a snapshot of the CM baseline

Re: [Dovecot] Possible header parsing problem

2008-10-27 Thread Eric Stadtherr
On Thu, 23 Oct 2008 19:06:19 +0300, Timo Sirainen <[EMAIL PROTECTED]> wrote: > 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 t

Re: [Dovecot] Possible header parsing problem

2008-10-24 Thread Timo Sirainen
On Fri, 2008-10-24 at 14:37 +0200, Jakob Hirsch wrote: > Timo Sirainen wrote: > > >> lead to strange behaviour. So I'd vote for replacing the folding tab > >> to a space. > > Actually Dovecot already replaces all tabs to spaces when sending > > ENVELOPE, BODY and BODYSTRUCTURE replies. The only

Re: [Dovecot] Possible header parsing problem

2008-10-24 Thread Jakob Hirsch
Timo Sirainen wrote: lead to strange behaviour. So I'd vote for replacing the folding tab to a space. Actually Dovecot already replaces all tabs to spaces when sending ENVELOPE, BODY and BODYSTRUCTURE replies. The only issue here is about the internal parsing where I think it's better to be st

Re: [Dovecot] Possible header parsing problem

2008-10-24 Thread Timo Sirainen
On Oct 24, 2008, at 12:35 PM, Jakob Hirsch wrote: Timo Sirainen wrote: 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. As pointed out in https://bugzilla.mozilla.org/show_bug.cgi? id=240924#c7, t

Re: [Dovecot] Possible header parsing problem

2008-10-24 Thread Jakob Hirsch
Timo Sirainen wrote: 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. As pointed out in https://bugzilla.mozilla.org/show_bug.cgi?id=240924#c7, this could lead to strange behaviour. So I'd vote for

Re: [Dovecot] Possible header parsing problem

2008-10-23 Thread Eric Stadtherr
On Thu, 23 Oct 2008 19:06:19 +0300, Timo Sirainen <[EMAIL PROTECTED]> wrote: > 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 t

Re: [Dovecot] Possible header parsing problem

2008-10-23 Thread 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

[Dovecot] Possible header parsing problem

2008-10-22 Thread Eric Stadtherr
Hi, I ran into a problem wherein my mail client (RoundCube) would not display a message from a Dovecot IMAP server (claiming that the message had no content). The raw source of the message looked fine, but the body structure returned by Dovecot only had the first text/plain part and not the a