Bug 294119 - cant read mail with attachmants
Summary: cant read mail with attachmants
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 1.99.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-15 00:28 UTC by Daniel Moyne
Modified: 2017-01-07 21:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Moyne 2012-02-15 00:28:52 UTC
Version:           1.99.0 (using KDE 4.8.0) 
OS:                Linux

I cannot read a mail with JPG files attached ; I do collect something like :Ce message est composé et au format MIME.

------=_NextPart_000_004A_01CCEB5D.98E82BA0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_001_004B_01CCEB5D.98E82BA0"


------=_NextPart_001_004B_01CCEB5D.98E82BA0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

CM n=B0 11
JPS
------=_NextPart_001_004B_01CCEB5D.98E82BA0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD>
<BODY dir=3Dltr>
<DIV dir=3Dltr>
<DIV style=3D"FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: 12pt">
<DIV>CM n=B0 11</DIV>
<DIV>JPS</DIV></DIV></DIV></BODY></HTML>

------=_NextPart_001_004B_01CCEB5D.98E82BA0--

------=_NextPart_000_004A_01CCEB5D.98E82BA0
Content-Type: image/jpeg;
        name="DSCG2243.jpg"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
        filename="DSCG2243.jpg"

/9j/4AAQSkZJRgABAQEASABIAAD/4RTzRXhpZgAASUkqAAgAAAALAA4BAgAgAAAAkgAAAA8BAgAF
AAAAsgAAABABAgAIAAAAuAAAABIBAwABAAAAAQAAABoBBQABAAAAwAAAABsBBQABAAAAyAAAACgB
AwABAAAAAgAAADIBAgAUAAAA0AAAABMCAwABAAAAAgAAAGmHBAABAAAAAAEAAKXEBwAcAAAA5AAA
AKAIAAAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgAFNPTlkAAERTQy1QOTIASAAAAAEA
AABIAAAAAQAAADIwMDY6MDI6MTYgMTE6NDg6MzEAUHJpbnRJTQAwMjUwAAACAAIAAQAAAAEBAAAA
ABsAmoIFAAEAAABKAgAAnYIFAAEAAABSAgAAIogDAAEAAAACAAAAJ4gDAAEAAABkAAAAAJAHAAQA
AAAwMjIwA5ACABQAAABaAgAABJACABQAAABuAgAAAZEHAAQAAAABAgMAApEFAAEAAACCAgAABJIK
................................
................................
UyOpArOumZQiqSAZRwKKKuKEi9cIsYRlGD09exqrOSDwSOP6Ciis2UNvUVbdJFGJFfAb0FYmlSyT
yuszs4EhAyewoopS+EaOqNrCu0rGAQuRXKeOL64sorZ7WTy2BBBCg4Ofeiinh0mNHFX+q32o20UV
5cvLHudypwATnrxWQ0jKxAPAoop1V7xtE//Z

------=_NextPart_000_004A_01CCEB5D.98E82BA0--

I have not included everything.

What is the problem

Reproducible: Sometimes

Steps to Reproduce:
someone has to send me a series of messages with attached JPG files ; first time I received unreadable files ; I asked him to try again just with one messge ; it was ok (as expected) ; I assked to send all other messages and those were unreadables

Actual Results:  
as showed in report but specimen available

Expected Results:  
icons swoing each file attached to be able to recover them

OS: Linux (x86_64) release 3.2.0-15-generic
Compiler: gcc
Comment 1 Laurent Montel 2012-02-15 10:20:54 UTC
please save this mail as mailbox format and attach to this bug report
Thanks
Comment 2 Daniel Moyne 2012-02-15 13:01:43 UTC
I wish I knew how to do that with Kmail that apparently does not propose anything to save a particular mail with a menu ; alternatively I could send directly a copy of this bad mail to you ?
Thanks
Comment 3 Laurent Montel 2012-02-15 14:55:03 UTC
kmail->file->save as
Comment 4 Daniel Moyne 2012-02-15 23:37:25 UTC
Sorry to big to be attached there after being saved !
Comment 5 Laurent Montel 2012-02-16 08:16:27 UTC
Ah ?!
So send me directly
Comment 6 Denis Kurz 2016-09-24 18:01:49 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 7 Denis Kurz 2017-01-07 21:36:49 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.