Version: 1.12.2 (using 4.3.2 (KDE 4.3.2), Gentoo) Compiler: x86_64-pc-linux-gnu-gcc OS: Linux (x86_64) release 2.6.31-thinkpad I received a mail, which the sender encrypted with my public key. It appears as follows when I open it: In the mail body, I do not see text, but just two attachments: ATT00001 (with a "keyhole" icon) ATT00002.bin (with a "binary" icon) The detailed list of attachments looks as follows: Complete mail: type multipart/mixed, encoding 7bit. Body part: plain text document, quoted-printable (0 byte) ATT00001: PGP/MIME-encrypted message header, base64 ATT00002.bin: unspecified binary data, base64 When I click on ATT00002.bin to open it, KMail tries to open it in kgpg, but no kgpg window appears. Note that kgpg is running properly. I was able to send an encrypted mail myself, and to decrypt that mail when viewing it in the sent folder. I am also able to open ATT00002.bin in the quick viewer (context menu option "view"). It displays as: [KMail: Attachment contains binary data. Trying to show first 1,448 characters.] -----BEGIN PGP MESSAGE----- Version: GnuPG v1.4.9 (GNU/Linux) ... -----END PGP MESSAGE----- (Strange, that warning on top). Nevertheless, when I copy the PGP message (without the warning on top), I can read it via kgpg's tray icon and "decrypt clipboard".
Hello Christoph, can you check if this problem persists with KDE/Kmail 4.10? I believe that many old encryption bugs should be fixed in this version. Also could you give an example how to produce such emails?
Hi Daniel, (In reply to comment #1) > can you check if this problem persists with KDE/Kmail 4.10? I'm sorry to disappoint you, but I'm no longer actively using Kmail and therefore it would take me too much time to try to reproduce this bug. > I believe that > many old encryption bugs should be fixed in this version. I'm sure you are right, but I'm not sure what's the best way to deal with this bug. Maybe close it, and wait whether someone else experiences such a problem in future? (Let's hope not.) > Also could you > give an example how to produce such emails? I don't recall the details, but I think I was referring to a real email that someone else had sent to me, using my public key, and most likely using a (possibly buggy?) mail client other than Kmail.
(In reply to comment #2) > > Also could you give an example how to produce such emails? > I don't recall the details, but I think I was referring to a real email that > someone else had sent to me, using my public key, and most likely using a > (possibly buggy?) mail client other than Kmail. Hi, knowing the client might help, maybe you can look into that email's header if you still have it. This information may also help other users with the same problem to find this bug report. Thanks, Daniel
(In reply to comment #3) > knowing the client might help, maybe you can look into that email's header > if you still have it. I tried hard to find the email that triggered this bug report, but I'm afraid I couldn't find it any more :-(
OK, maybe someone deeper involved into the encryption matters than me can still decide how to proceed now. Setting the status back to unconfirmed.
Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.