Bug 321063

Summary:	Deleting an attachment deletes ALL email contents
Product:	[Applications] kmail2	Reporter:	Antonio Rojas <arojas>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	critical	CC:	axel.braun, montel, nico.kruber
Priority:	NOR
Version:	4.10.4
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:

Description Antonio Rojas 2013-06-12 12:06:40 UTC

I don't know how to consistently reproduce it, but it has happened a few times in the last few days. Deleting an attachment deletes all email contents, and replaces it with the text

 "You deleted an attachment from this message. The original MIME headers for the attachment were:
Content-Type: application/pdf"

The account is IMAP disconnected, and the email contents are also deleted from the server, leading to serious data loss

Reproducible: Sometimes

Comment 1 Laurent Montel 2013-06-13 05:51:11 UTC

Without testcase it will hard to fix it :(

Comment 2 Antonio Rojas 2013-07-04 10:24:57 UTC

I've sent you an email in private that shows this issue.

Comment 3 Laurent Montel 2013-07-04 11:35:03 UTC

Thanks
will look at.
Regards

Comment 4 Laurent Montel 2013-07-05 07:06:56 UTC

I can confirm it.
Will continue to investigate

Comment 5 Axel Braun 2013-10-06 21:28:46 UTC

+1 - just had the problem as well!

Comment 6 Nico Kruber 2013-10-22 17:17:42 UTC

+1 on KDE 4.11.2

However, I found a (reliable?) way to reproduce it:

1) login to gmail (the web frontend) and send e.g. yourself an email with an attachment (I used a pdf file) and some text as content
2) then receive it in the (disconnected) IMAP resource and delete the attachment
3) the email content is gone and replaced by
You deleted an attachment from this message. The original MIME headers for the attachment were:
Content-Type: application/pdf
name="test.pdf"
filename="test.pdf"

Comment 7 Axel Braun 2014-12-08 11:33:19 UTC

Still a problem in 4.13.3 :-(

Comment 8 Nico Kruber 2015-03-19 12:37:04 UTC

seems fixed now (kdepim 4.14.6)

*** This bug has been marked as a duplicate of bug 312276 ***