Bug 187138

Summary:	do not delete mail on editing (major, data loss)
Product:	[Unmaintained] kmail	Reporter:	Maciej Pilichowski <bluedzins>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	mail
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Maciej Pilichowski 2009-03-14 14:42:23 UTC

Version:            (using KDE 4.2.1)
Installed from:    SuSE RPMs

Because I don't see any backup mechanism it is fairly easy to loose mail while composing it, and what's more KMail actually misleads user about the security -- saving as draft, is to any similar to save-often while editing in kate, because each time you continue editing the mail the mail is deleted by KMail.

This is serious issue.

How to reproduce.
1) start KMail, new message
2) type something in Composer
3) save as draft
4) go to drafts folder
5) edit the saved mail
6) you see composer? Ok, kill Kmail (not quit, kill)
7) run KMail again
8) all you typed before (6) is lost

Once again -- saved data in Kate, are saved. Saved data in KMail are _not_ saved.

Comment 1 George Kiagiadakis 2009-03-14 15:13:40 UTC

I can't reproduce this. I kill kmail and after I reopen it, composer appears together with the main window and shows everything I had typed.

Comment 2 Maciej Pilichowski 2009-03-14 15:28:07 UTC

I can reproduce it using KDE3.5.10 and KDE4.2.1 -- I only once was unable to reproduce it (i.e. the composer restored the mail). Btw. I killed Kmail using KDE kill.

However I encountered data loss (for real) when the whole system crashed.

The current design for me is too risky -- the original mail should stay in place, and further saving should alter it. Pretty much as it happens with editor.

Or if it is impossible, keep the original content, until the new mail could be replaced, and only after that the old one would be deleted.

Comment 3 Jaime Torres 2009-03-14 22:36:08 UTC

It is about the same consecuencies...

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