[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Re: kmail: bugreport+bugfix (nested multipart messages)
From:       George Staikos <staikos () 0wned ! org>
Date:       2000-09-27 1:45:34
[Download RAW message or body]

On Tue, 26 Sep 2000, Daniel F Moisset wrote:

   I think this is what is needed to start getting mime digest decoding in
place too..  Mime digests are essentially big trees of messages.  It's too
bad we can send them but not receive them :)

  
> > The current development version of KMail still is not able to display the 
> > test messages you sent correctely.
> 
> The result with the patch is the following:
>   The first message is displayed when "Prefer HTML to text" is
> enabled; both parts are displayed (text/plain and text/html). When "Prefer
> HTML" is disabled, both parts are shown, but the text/html is not
> rendered; the HTML source is displayed instead. (That is with View|Inline 
> attachments selected).
> I don't know if that's the desired behavior, but at least parts are
> separated, and decoded according to Content-Transfer-Encoding.
>   The second message is still rendered incorrectly; apparently mimelib
> fails to recognize it as a multipart message. Perhaps the format is
> incorrect (it was artificially composed), but PINE shows the parts as I
> think they should be.
> 
> > If you want to have your improvements in KMail, then please send us a diff 
> > against a current beta or CVS version of KMail.
> I made it against a CVS version 
> 
> Anyway, it will be ugly. KMMessage::getBodyPart() makes the message look
> like a list of parts, when it's actually a tree. I changed it so it now
> reads all the leaf nodes (attachments) instead of only the top level, but
> a clean fix should involve changing the interfaec of kmmesage (ie,
> kmmessage, and all its client classes).
> 
> Without the patch, kmail takes each top-level *tree*, and it renders it
> correctly when it's a common message part (text, html, images,
> attached-files), but shows an undecoded list of parts when it's
> not; that's quite usual with mails sent with Outlook. I think it's the
> cause of several reports I've seen frequently in this list (or for
> example, bugs #7077 and #6710)


-- 

George Staikos 

_______________________________________________
Kmail Developers mailing list
Kmail@master.kde.org
http://master.kde.org/mailman/listinfo/kmail

[prev in list] [next in list] [prev in thread] [next in thread]