Version: (using KDE KDE 3.1.3) Installed from: Mandrake RPMs KMail appears not to support enriched text as described in RFC 1563. http://www.faqs.org/rfcs/rfc1563.html Some e-mail clients (eg Mulberry) do use this instead of HTML mail.
At the same time, could I thank you all for your work - KMail is a fantastic program and better than any other e-mail program I've ever tried. Shortly after I started to use Linux, I nearly went back to Windows, but couldn't find a satisfactory e-mail client in Windows which matched KMail, hence I stuck in Linux. And here I still am, a year later :)
Just a comment: I thought that text/enriched is very dead and one of causalties of HTML-mail, but apparently it is used by Mail.app in Apple OS X, which probably just reads HTML-mail (http://www2.skidmore.edu/cits/selfhelp/email/osx_mail.cfm, or for example http://discussions.info.apple.com/WebX?13@46.xzy1adBMnMw.0@.599d15d4/4 ). Oh well.
RFC 1896 obsoletes 1563 http://www.faqs.org/rfcs/rfc1896.html
This RFC also has an enriched -> HTML converter in C at the end, so perhaps it could be simply implemented (once the feature freeze is over) by transforming the part into HTML and then displaying it as an HTML part?
As comment #2 noted, Apple Mail can only send messages in text/enriched or text/plain format (it doesn't have HTML as an option). I don't care that KMail can't display text/enriched but I find it slightly annoying that KMail actually displays both parts of such an e-mail: the text/plain part _and_ the text/enriched part (with all the markup code). At least this should be easily fixable.
*** This bug has been confirmed by popular vote. ***
Still an issue in KMail 1.7.1 / KDE 3.3.1. Annoying when you have mixed platforms (Linux/Apple) at work.
Created attachment 15453 [details] additional code to read MIME text/enriched messages This patch contains additional code for KMail to enable the displaying of RFC 1896 style text/enriched MIME messages. Using the code from http://rfc.net/rfc1896.html as a basis the text/enriched parts are either converted to HTML for display or to ASCII text for e.g. replies. It works fine with any text/enriched mails I tried (from Openstep Mail.app, the predcessor of Apple Mac OS X Mail.app). I'm not too lucky with this code, but my time is too limited to make it smoother. The patch is for kmail-3.4.2 but applies to 3.5.2 as well (with some minor line offsets), though I couldn't test it with 3.5.2. However, KMail fails to properly quote multipart mails when generating replies. Only the first part is quoted, while all text/* parts with Content-Disposition: inline in a multipart/mixed mail should be included. I didn't dare to patch that too, as I'm not sure where the best place to do so would be (processMultiPartMixedSubtype()?) Anyway, it basically works OK as far as I can see. If desired a can attach some test messages to this bug.
Uups - I goofed the version numbers in my previous comment/patch. Read "KMail 1.8.2 in KDE 3.4.2" and "KMail 1.9.1 in KDE 3.5.2" respectively, please.
I have two problems with this patch: 1. It uses code that is not GPL'ed. Others need to decide whether the RFC license is GPL compatible, but I'd much rather prefer a clean-room implementation. Shouldn't be too difficult. 2. The HtmlWriter is already buffering, so another layer isn't needed. Please fix those two problems and re-submit the patch. BTW: Do you know that KMail has a plugin interface for this kind of thing? The feature would be a lot easier to integrate in all the different version if you implemented it as a plugin. There are sample plugins in kdepim/plugins/kmail/bodypartformatter (or similar) to get inspiration and a build system template. Thanks for the patch. I miss this feature, too :) Marc
OK, her my comments to Marcs remarks: 1. I will write own code for parsing to avoid any legal problems. 2. I wasn't aware that there is another buffering layer. I'm happy about it so I can throw out that ugly buffering code of mine. I disliked it anyway. on writing a plugin: I'd love to do so, but the plugins (at least those three currently present) are pure disply plugins. The displayed content is not quoted in a reply. However, this is highly desired for text/enriched messages, they are essential content as text/plain parts are, so I need to make text/enriched a first class citizen by weaving it into objecttreeparser.cpp. The hooks were already in there anyway (in bodypartformatter.cpp), apparently for this reason.
Is this bug going anywhere? There is a discussion of Enriched Text vs. HTML at: http://www.kde-forum.org/thread.php?postid=65402#post65402 Apparently some people would prefer that messages written in Kmail be in Enriched Text instead of HTML. Of course, this will not happen until Kmail actually _reads_ the stuff.
Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented. Thank you for your understanding.
Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.
The only references to enriched in the source code show that this is not handled. Reopening...