Version: 1.4.3. (using KDE KDE 3.1KDE 1.2) Installed from: SuSE RPMsSuSE RPMs OS: Linux I've search in the database and another bug concerning this problem appeared (#47354). When I read it, it shown the following: Your report is a duplicate of Bug #33556. Unfortunately, Bug #33556 doesn't exist in the database... and the Incredimail made mail still appears broken :-( Any Incredimail message and their replies (even if not created with Incredimail) appears as attachments only. When you try to open these, the images are properly displayed, but the texts are messy: notably the quoted-printable encoding isn't recognized. I think the origin is to find in the recursive MIME-format (for example, a text/plain and an image/gif are embedded into a multipart/alternative - I'm asking myself wether it should't be multipart/mixed, but I'm not a MIME-expert at all). Test message for example: ----- Return-Path: <choppy@imaginet.fr> Delivered-To: choppy@localhost Received: from localhost (localhost [127.0.0.1]) by athena (Postfix) with ESMTP id 7BB9B70EA for <choppy@localhost>; Thu, 4 Sep 2003 19:26:05 +0200 (CEST) Received: from pop.imaginet.fr [213.41.78.20] by localhost with POP3 (fetchmail-5.9.11) for choppy@localhost (single-drop); Thu, 04 Sep 2003 19:26:05 +0200 (CEST) Received: from mwinf0402.wanadoo.fr (smtp5.wanadoo.fr [193.252.22.27]) by mx0.fr.colt.net with ESMTP id h84HT5E20774 for <choppy@imaginet.fr>; Thu, 4 Sep 2003 19:29:05 +0200 (MET DST) Received: from winxpert-qp9my0 (Mix-Ste-Genev-Bois-106-4-120.w193-248.abo.wanadoo.fr [193.248.254.120]) by mwinf0402.wanadoo.fr (SMTP Server) with SMTP id A765A8001A7 for <choppy@imaginet.fr>; Thu, 4 Sep 2003 19:21:21 +0200 (CEST) MIME-Version: 1.0 Message-Id: <3F57743E.000008.00424@winxpert-qp9my0> Date: Thu, 4 Sep 2003 19:19:58 +0200 (Paris, Madrid (heure d'
Subject: Re: New: Messages from Incredimail not properly analyzed I think this is a multipart/related issue, I'm working on implementing support for that. Can you forward me as attachments some examples of mails that KMail currently doesn't render properly? Don.
*** This bug has been marked as a duplicate of 6710 ***