Version: 4.7 (using KDE 4.7.2) OS: Linux When I receive a pgp-encrypted message with an attachment, I am unable to open the attachment. The attached file is displayed, but clicking on it does not have any effect. Right-clicking on the mail and selecting "save attachments" results in kmail2 to save the whole mail as an .asc-file. Reproducible: Always Steps to Reproduce: Open any pgp-encrypted e-mail with an attachment in it. Click on the attachment. Actual Results: Nothing happens. Expected Results: Open a dialog to save the file.
Will look at it in master.
Question: How we create an email pgp encrypted email .?
no infos ?
Hello... what info do you need exactly? How to create an encrypted message is easy: just create a key-pair (f.e. with kleopatra), link the keys to your identity in kmail-settings, create a mail, select "encrypt" and send it to yourself.
I can't reproduce in master. But I fixed a lot of bug. (backported to 4.7.3/4.7.4) So perhaps you can test on new version. Regards.
Ok, i'll try that, thanks.
The bug still exists in kde 4.7.4.
The bug still exists in kde 4.8.4.
Reopening based on comments #7 and #8
I can confirm this or a similar bug, at least for some mails. The attachment is only shown as a link, e.g. "attachment:0:2?place=body", and can ony be saved as a link to this location. I cannot give a recipe how to reproduce this kind of problematic email, it only happens sometimes to me. A workaround: Save the encrypted email to disk, decrypt manually, save result as foo.mbox, open that in Kmail and save the attachment from the unencrypted email.
The bug still exists in KDE SC 4.10.4. Problematic E-mails sent from Windows using Thunderbird with Enigmail extension.
Can you tell me more about the structure of the mail, where the link doesn't work: * Is this a openpgp/MIME or inlnie message * Are the hole message is encrypted at once or the attachments sperately?
(In reply to comment #12) > Can you tell me more about the structure of the mail, where the link doesn't > work: > * Is this a openpgp/MIME or inlnie message > * Are the hole message is encrypted at once or the attachments sperately? I can send a sample to you personally for the full headers, but this looks like the relevant information: .... User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 .... X-Enigmail-Version: 1.3.3 Content-Type: multipart/encrypted; protocol="application/pgp-encrypted"; boundary="------------enigXXXXXX" .... This is an OpenPGP/MIME encrypted message (RFC 2440 and 3156) --------------enigXXXXXX Content-Type: application/pgp-encrypted Content-Description: PGP/MIME version identification Version: 1 --------------enigXXXXXX Content-Type: application/octet-stream; name="encrypted.asc" Content-Description: OpenPGP encrypted message Content-Disposition: inline; filename="encrypted.asc" -----BEGIN PGP MESSAGE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
Have now one message, to play with and can confirm this bug with KDE 4.11 branch. As I can tell till now, the structure, that objectparser creates looks correct (also the links to the attachments). I think the error is located in the funtion, that resolves the links. It is an PGP Mime Message with folloing structure inside: Content-Type: multipart/mixed; boundary="------------030502030301040002020205" This is a multi-part message in MIME format. --------------030502030301040002020205 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable blabla... --------------030502030301040002020205 Content-Type: text/plain; charset=windows-1252; name="testfile" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="testfile" Some testfile --------------030502030301040002020205--
*** Bug 294272 has been marked as a duplicate of this bug. ***
*** Bug 324365 has been marked as a duplicate of this bug. ***
Git commit bbbdbc2180036040cac2b66492e6f0fd01c2b28c by Sandro Knauß. Committed on 21/10/2013 at 00:47. Pushed by knauss into branch 'KDE/4.11'. Fix 286481 - Unable to open attachments in encrypted messages The node has to get a correct extra content and the filename must be correctly point to the attachments inside the encrypted message. Related: bug 300937 FIXED-IN: 4.11.3 REVIEW: 113361 M +2 -3 messageviewer/viewer/nodehelper.cpp M +1 -1 messageviewer/viewer/objecttreeparser.cpp http://commits.kde.org/kdepim/bbbdbc2180036040cac2b66492e6f0fd01c2b28c
this bug is NOT solved for me. i have a pgp/mime mail which is signed and encrypted and still has the problem that the file is not savable. if i right click on the file, the normal context menu is shown, that i can see if i click anywhere in a mail. Content-Type: multipart/encrypted; protocol="application/pgp-encrypted"; micalg="pgp-sha1"; boundary="===============8454854918288420383==" MIME-Version: 1.0 From: XXXXXXXX To: till2.schaefer@tu-dortmund.de Date: Thu, 24 Oct 2013 17:03:34 -0400 Subject: Your signed PGP key 0xD84DED79 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============8454854918288420383== Content-Type: application/pgp-encrypted Content-Description: PGP/MIME version identification Version: 1 --===============8454854918288420383== Content-Type: application/octet-stream; name="encrypted.asc" Content-Description: OpenPGP encrypted message Content-Disposition: inline; filename="encrypted.asc" -----BEGIN PGP MESSAGE----- Version: GnuPG v1.4.15 (GNU/Linux) ...encrypted stuff... -----END PGP MESSAGE----- --===============8454854918288420383==--
Created attachment 83102 [details] mail with not clickable link
Forget to mention, that iam using the latest gentoo ebuild (kde-base/kmail-4.11.2-r1). The changelog states, that this patch was backported.
Hey Till, yes I did indeed add this commit. Please make sure that you re-started everything relevant... it would be best if you log out and log back in again!
Hi Andreas, i already did a reboot. Still not working.
Just a note: to get some changes to the KMail sources to take effect in Gentoo, you also need to rebuild kdepimlibs.
rebuilding kdepimlibs did not change the behavior. should i file a gentoo bug for this or is this? I don't know if it is gentoo specific.
i have noticed that the bug only occurs, when the mail is signed AND encrypted. All mails that are only encrypted are working. When i have a signed and encrypted mail, the attachement name shown on the top of the mail is called encrypted.asc and not <attached file name>. for encrypted mails (not signed) this line states the attached file name. so maybe this obversations are somewhat connected?
(In reply to comment #25) > i have noticed that the bug only occurs, when the mail is signed AND > encrypted. All mails that are only encrypted are working. When i have a > signed and encrypted mail, the attachement name shown on the top of the mail > is called encrypted.asc and not <attached file name>. for encrypted mails > (not signed) this line states the attached file name. so maybe this > obversations are somewhat connected? Actually this is exactly the bug that was solved. It sounds for me, that the patch was NOT included in the version you have used. Plaese look into your code, that you compile, to make sure that the pach is added (only three lines patch).
(In reply to comment #26) > (In reply to comment #25) > > i have noticed that the bug only occurs, when the mail is signed AND > > encrypted. All mails that are only encrypted are working. When i have a > > signed and encrypted mail, the attachement name shown on the top of the mail > > is called encrypted.asc and not <attached file name>. for encrypted mails > > (not signed) this line states the attached file name. so maybe this > > obversations are somewhat connected? > > Actually this is exactly the bug that was solved. It sounds for me, that the > patch was NOT included in the version you have used. Plaese look into your > code, that you compile, to make sure that the pach is added (only three > lines patch). My fault. Till please also upgrade to kdepim-common-libs-4.11.2-r1. I applied the patch in the wrong part of our split kdepim; it got happily applied but never compiled. (side note, if you need help in splitting kdepim into different repositories, have a look at our ebuilds :)
Now it is working for me. Therefore this was a gentoo bug.