Bug 236734 - Make storing the unencrypted message work
Summary: Make storing the unencrypted message work
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdepim
Classification: Applications
Component: messageviewer (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: VLO normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: akonadi-ports-regression
Depends on:
Blocks:
 
Reported: 2010-05-07 19:00 UTC by Thomas McGuire
Modified: 2017-01-07 22:50 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas McGuire 2010-05-07 19:00:57 UTC
If GlobalSettings::self()->storeDisplayedMessagesUnencrypted() is enabled, KMail should replace the original encrypted message with the unencrypted version in the store.
This code for that is currently not ported, see ViewerPrivate::parseMsg(): //FIXME(Andras) actually connect and do the replacement on the server
Comment 1 Thomas McGuire 2010-05-07 19:01:30 UTC
Hidden config option, so setting this to low priority.
Our customer might want this, though.
Comment 2 András Manţia 2010-05-20 17:47:45 UTC
SVN commit 1128899 by amantia:

Saving encrypted messages as decrypted on viewing is partially done (for PGP messages). It uses a simple approach, so might fail in certain cases, but unless I have messages showing the failure, it remains as it is. It also has a flicker that I have to debug later.
Also fix a signal/slot connection.

CCBUG: 236734

 M  +61 -20    viewer_p.cpp  
 M  +3 -0      viewer_p.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1128899
Comment 3 mooniac 2011-01-01 16:40:35 UTC
Instead of storing messages unencrypted, would it be better to store them encrypted, but have KMail decrypt automatically "on the fly" when the message is clicked? What bothers me is the fact that I have to type my passphrase for each and every message that I click on, so I end up typing it a hundred times when I go through my email. The problem is not the fact that it's stored encrypted in the messages store. The problem is the user interaction. Also from a security perspective it may be better to store them encrypted, because the maildir folders could get hacked/stolen/etc. The *storing* in maildir folders should always be encrypted, but the user should never have to type in the passphrase repeatedly, for each and every message. gmail and yahoo mail decrypt automatically, without requiring the user to type the passphrase.
Comment 4 m.eik michalke 2011-10-24 16:53:27 UTC
this worked well in kmail1 in the past, and i was very happy about that -- since my home is already encrypted, i don't see the need to encrypt messages locally stored there a second time. i don't glue envelopes back together after reading a letter either, and i really miss this feature in kmail2.

i would like to be able to decide this for individual messages, though.
Comment 5 mau 2014-11-17 10:23:45 UTC
I'd like to have this feature as well - more precisely I propose and ask for the following:
- show config option to store messages that have been decrypted once unencrypted (via global kmail settings or by always asking the user when an encrypted message is shown)
- make it work for PGP and S/MIME
- as it can introduce a security hole, do this only if the message is local (maildir, mbox), not on IMAP or POP.

Having implemented that would be very very useful, thanks if someone actually takes on the job!
Comment 6 Denis Kurz 2016-09-24 21:00:35 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 kdepim (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 7 Denis Kurz 2017-01-07 22:50:13 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.