Oleg,
On second thought, no need to file a bug. I've reproduced this by
setting up a proper test-case for multipart/alternative. It looks easy
enough to fix so sit tight.
Paul J Stevens wrote:
>Oleg Lapshin wrote:
>
>
>>Hello.
>>
>>I have message in my INBOX with attach
>>When I try to open it in kmail, this happens:
>>
>>with dbmail-2.0-current (from svn):
>>
>>kmail send:
>>95 UID FETCH 48111 (BODYSTRUCTURE)
>>and get this:
>>(("text" "plain" ("charset" "US-ASCII") NIL NIL "7BIT" 4 2 NIL NIL
>>NIL)("text"
>>"html" ("charset" "US-ASCII") NIL NIL "7BIT" 4 2 NIL NIL NIL)
>>"alternative" ("boundary" "=_alternative 002B88F7C325710A_=") NIL NIL)
>>("image" "jpeg" ("name" "IMG_5898.JPG") NIL NIL "base64" 2715854 NIL
>>("attachment" ("filename" "IMG_5898.JPG")) NIL) "mixed" ("boundary" "=_mixed
>>002B88F7C325710A_=") NIL NIL) UID 48111)
>>95 OK UID FETCH completed
>>
>>
>>But when I run dbmail-2.1-current (from svn):
>>
>>kmail send:
>>13 UID FETCH 48111 (BODYSTRUCTURE)
>>an get this:
>>UID 48111 BODYSTRUCTURE (("text" "plain" ("charset" "US-ASCII") NIL NIL NIL 0
>>1 NIL NIL NIL NIL)("text" "html" ("charset" "US-ASCII") NIL NIL NIL 0 1 NIL
>>NIL NIL NIL) "alternative" ("boundary" "=_alternative 002B88F7C325710A_=")
>>NIL NIL NIL ("image" "jpeg" ("name" "IMG_5898.JPG") NIL NIL "base64" 2681472
>>NIL ("attachment" ("filename" "IMG_5898.JPG")) NIL NIL) "mixed" ("boundary"
>>"=_mixed 002B88F7C325710A_=") NIL NIL NIL))
>>13 OK UID FETCH completed
>>
>>So, kmail interpret message as plain text, but not as mime
>>
>>
>
>That is not indicated by the bodystructure response. I'm not saying
>there's no problem with bodystructure in 2.1, but the 2.1 code has been
>tested extensively on thunderbird, outlook express, evolution, mutt, and
>squirrelmail, and has held up much better than the 2.0 codebase so far.
>
>As far as I can tell there might be a problem with the nesting. Please
>file a bug, but could you please first confirm this problem happens in
>other clients as well?
>
>
>
>>Message header and begining of body:
>>
>>Delivery-date: Sat, 04 Feb 2006 01:36:20 +0300
>>Received: from mail by x.x.ru
>> with virus-scanned (Exim 4.60) (envelope-from )
>> id 1F58Ia-0000pg-PY for [EMAIL PROTECTED]; Sat, 04 Feb 2006
>> 00:16:57 +0300
>>Received: from [x.x.x.x] (helo=xxxxxx)
>> by xxx.xxxx.ru
>> with esmtp (Exim 4.60) (envelope-from )
>> id 1F58IR-0000pJ-J5 for [EMAIL PROTECTED]; Sat, 04 Feb 2006
>> 00:16:54 +0300
>>From: [EMAIL PROTECTED]
>>To: xxx!xxxxx.ru
>>Subject: Foro
>>Message-ID:
>>Sender: [EMAIL PROTECTED]
>>Date: Fri, 3 Feb 2006 10:55:31 +0300
>>X-DBMail-PhysMessage-ID: 22826
>>MIME-Version: 1.0
>>Content-Type: multipart/mixed;
>> boundary="=_mixed 002B88F7C325710A_="
>>X-Length: 2683213
>>X-UID: 48111
>>
>>--=_mixed 002B88F7C325710A_=
>>Content-Type: multipart/alternative; boundary="=_alternative
>>002B88F7C325710A_="
>>
>>
>>--=_alternative 002B88F7C325710A_=
>>Content-Type: text/plain; charset="US-ASCII"
>>
>>
>>--=_alternative 002B88F7C325710A_=
>>Content-Type: text/html; charset="US-ASCII"
>>
>>
>>--=_alternative 002B88F7C325710A_=--
>>
>>--=_mixed 002B88F7C325710A_=
>>Content-Type: image/jpeg; name="IMG_5898.JPG"
>>Content-Disposition: attachment; filename="IMG_5898.JPG"
>>Content-Transfer-Encoding: base64
>>
>>/9j/4AAQSkZJRgABAQAAAQABAAD/4TIxRXhpZgAASUkqAAgAAAAJAA8BAgAGAAAAegAAABABAgAO
>><skip other mime lines>
>>
>>--=_mixed 002B88F7C325710A_=--
>>
>>
>>What else must I give you to help solve this problem?
>>
>>
>>
>
>
>
--
________________________________________________________________
Paul Stevens mailto:[EMAIL PROTECTED]
NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED]
The Netherlands________________________________http://www.nfg.nl
