Bug 122099

Summary: launch application on encrypted attachment after decryption
Product: [Applications] kmail2 Reporter: Andrew Bird <ajb>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: korossy, luigi.toscano, sknauss
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Andrew Bird 2006-02-16 14:36:04 UTC 
Version:            (using KDE KDE 3.5.1)
Installed from:    Fedora RPMs
OS:                Linux

mails received from PGP/Windows have this structure;

body part - encrypted / signed message body
attachment.pdf.asc
attachment.html.asc

As you can see the attachments are outside of the encrypted body and are separately encrypted. This means when you left click on the attachment they try to open it in kgpg, but the resulting decrypted file is never opened in an application. So in order to read each attachment, the use must save each file encrypted, decrypt it, and launch application to read.
Comment 1 Myriam Schweingruber 2012-08-18 08:06:03 UTC 
Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented.
Thank you for your understanding.
Comment 2 Luigi Toscano 2012-08-19 00:36:46 UTC 
Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.
Comment 3 Andrew Bird 2012-08-19 10:06:57 UTC 
This would still be a very useful feature in Kmail2. Consider the case where a gpg'd zipfile has been attached; clicking on the attachment in kmail2 offers the choices 'Save as', 'Open with kgpg', 'Open with ...' and Cancel. An additional choice would be nice, 'Decrypt and open with ...', which in that case could be used to decrypt the file and then open in Ark to see the contents.

Thanks for considering
Comment 4 Sandro Knauß 2014-03-30 23:03:42 UTC 

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