[Tickets #12062] Re: Mime parser fails to parse multipart message

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12062
------------------------------------------------------------------------------
  Ticket             | 12062
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Mime parser fails to parse multipart message
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2013-02-20 12:39) wrote:

> Hi,
>
> I had a Kolab calendar entry (created by another Kolab client)
> that loaded just fine. When I tried to modify the object,
> an exception about a missing mime part was thrown:
>
> "Missing expected mime type (application/x-vnd.kolab.event)
> in object "123" in folder "INBOX/Calendar"!
>
>
> Digging through the code I found out the parse code
> for Kolab messages uses
>
> "Horde_Imap_Client_Fetch_Query()->structure()"
> and then "Horde_Imap_Client->getStructure()".
>
> -> This properly finds the Kolab XML attachment part.
>
>
> The save() function re-reads the message.
> It uses "Horde_Imap_Client_Fetch_Query()->fullText()"
> and then "Horde_Mime_Part::parseMessage()".
>
> -> The resulting body structure is one "text/plain" part.
>
>
> Further debugging showed the Kolab object / email
> in question is missing the
>
> "MIME-Version: 1.0"
>
> header field. Should the MIME parser be less strict about this?

NO.  Without a MIME-Version header, it is NOT a MIME message.

And it is not something we should ignore.  For example, IMAP servers  
will treat a message as non-MIME in BODYSTRUCTURE (i.e. single  
tex/plain ASCII part) without MIME-Version.