Summary: | KMail fails to parse emails properly in some cases | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Moritz <m.o> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | andreas, frederic.coiffier, fresh.road1272, jemand, m.o, m4rkusxxl, marcinkocur, montel, quazgar, sknauss |
Priority: | NOR | ||
Version: | 4.8 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Sample email in the format KMail stored it. |
Description
Moritz
2012-02-01 12:19:58 UTC
please attach to bug report your email (as mbox if possible) pastbin will remove soon Hm, it says "Expires: Never" on pastebin? Created attachment 68399 [details]
Sample email in the format KMail stored it.
Do you have any filters? Some filters sometimes mangle the message so that the mime header in the main header is converted into text/plain. The attached mail is of text/plain type and should be rendered as shown. The embedded mime parts should only be interpreted as mime parts when the parent says so and in this case it doesn't. Yes, I'm using bogofilter (and have been for at least 2-3 years. Last update was on 12th of January and I haven't had this problem before 4.8, so it'd be strange if it was bogofilter's fault). Besides that I'm using some custom filters using only standard KMail rules like "Subject contains 'orange' -> move to 'fruit'", but that shouldn't be a problem, right? I'll turn off bogofilter to see if that changes anything. By the way, in the meantime I've received multi-part emails and they were parsed correctly. Maybe they got a different handling by bogofilter. We'll see. I just sent myself a test email containing a PGP signature and this time it was parsed correctly. If it turns out that there are no mis-parsed emails anymore: is this a bogofilter bug now even though this is only happening since the 4.8 update? Not sure where this bug is from only that it is related to filters. In my case, the first problem appeared 2 days ago. The same day, I have enabled Bogofilter (but I haven't changed any other filter). I confirm that I had 2 problems on emails which embeds plain text and HTML version : the content of one of this mail is displayed in Kmail just after this line (in the source) : X-Bogosity: Ham, tests=bogofilter, spamicity=0.000003, version=1.2.2 Seems to be exactly the same problem I am having. See bug: 292767 i have experienced the same behaviour, and I could narrow it down to the "Bogofilter Check" mail filter. I've sent myself a multi part message from my web mail client, and with the filter turned off, the mail looked as expected, with the filter turned on, it showed the behaviour as above. Looking at the raw mail content, the primary difference was that in the bogo-filtered message, the Content-Type in the mail header was: Content-Type: text/plain; charset="US-ASCII" whereas in unfiltered message it looked like Content-Type: multipart/mixed; boundary="========GMX112281328289219935858" I checked bogofilter standalone as well, running a "bogofilter -p -e" against an mbox file of the "unfiltered" test mail - the output here shows the correct header Content-Type . So it looks that somewhere during the bogofilter run the Content-Type is being changed by kmail (or akonadi?). If needed, I can as well attach the mbox files, or run additional tests. *** Bug 293359 has been marked as a duplicate of this bug. *** *** This bug has been confirmed by popular vote. *** I added a manual rule to pipe everything through a script: #!/bin/sh TEMPFILE=$(mktemp --tmpdir=/tmp/ kmail.test.XXXXXX) cat > $TEMPFILE cat $TEMPFILE You can see, the first time the script gets the original message. The second time every "options" get put in one line each. And somehow the message has doubled the size. (seems to just be copies of the body) And option may have a different spelling (some letters became upper case). So kmail seems to parse a mail from a pipe differently than a mail directly from the server. I couldnt reproduce the missing/wrong "Content-Type" but I do have the same problem with spamassassin. kmail is still crunching my mails... anybody?! Is it fixed in trunk? In upcoming 4.8.1? Perhaps dup of Bug#291171 and fixed in 4.8.1? On http://cgbdx.wordpress.com/2012/03/01/kdepim-bug-fixes-in-kde-4-8-1-8/, a bug fix for bug 291171 is mentioned which seems to be this problem, so I'd say: yes, this is fixed. Kontact 4.8.1 I just got a notification from facebook. Before I had set up bogofilter back. It came as 2 e-mails, one broken, kmail's browser shows it as: --b1_2c23527440a52140ce850074979b0adb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable and the second one which is ok. Here's a source fragment: X-Bogosity: Unsure, tests=bogofilter, spamicity=0.491833, version=1.2.2 --b1_2c23527440a52140ce850074979b0adb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D http://www.facebook.com/n/?permalink.php&story_fbid=3D199129653525996&id= The broken one source fragment: X-Bogosity: Ham, tests=bogofilter, spamicity=0.042048, version=1.2.2 --b1_2c23527440a52140ce850074979b0adb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D http://www.facebook.com/n/?permalink.php&story_fbid=3D199129653525996&id= I confirm that the problem still exists in kmail 4.8.1 (Gentoo) : As soon as I enable "Bogofilter" filters, my newly received emails are corrupted. Just thought I'd add that on my machine it works just fine with Bogofilter enabled. It does even actually filter spam (which it had stopped doing some time ago). Only it doesn't mark new spam as unread even though the settings are correct and it crashes twice a day but that's a different story… Maybe you have to completely remove its filters and run the spam wizard? At least that's what I did. I can't reproduce the problem with kmail 4.8.2. So, it seems to be fixed. Maybe it's because spam filter doesn't work ;) Duplicate of bug #292767? *** This bug has been marked as a duplicate of bug 292767 *** |