In my tests it does work nicely now. We detect the "Send Again" state and correctly handle it. Sign / Encrypt is preselected depending on the state of the original mail. Even works with attachments.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 12 2018
Never seen the crash again.
New version of GnuPG is now packaged.
Apr 11 2018
Accidentally mixed up the ticket number. The correct commits for this ticket are:
Oops. I confused the ticket numbers rO34f6bb73882e: Implement send again for crypto mails. Would be the correct commit for this ticket.
Right, outlook.com is often problematic, although it might be a generic Exchange 2016 problem. Outlook.com and Exchange 2016 behave much the same.
Apr 10 2018
I've got an example mail. The problem is that the mail itself is "Content-Type: multipart/mixed; boundary="_003_DB4PR08MB01092D175DE8C1861B5D0BC197BF0DB4PR08MB0109eurp_"
"
I'll go for a warning / error for now and see if I can fix the renumbering.
Apr 9 2018
Have you tried it multiple times? If it's unintialized memory access maybe you got lucky?
Thanks for the report and the spelling fixes :-)
Thanks for the report.
Apr 5 2018
This problem should be gone with Gpg4win-3.1.0-beta48. While I could not reproduce it I've tried to fix it and changed the hard error to a debug log in case something is unexpected here. I believe that this is safe.
I tried to reproduce this again, using S/MIME Mails, installing gpg4win 2.x etc. It did not crash for me :-/
Can you please provide the version of the tool "pinentry"
Apr 4 2018
In T3864#112250, @aheinecke wrote:
- Resetting the GnuPG Profile back to default in Kleopatra does not work.
I doubt that I will be able to fix this. The problem is that for Outlook we build the signed mail structure, which is a multipart MIME message. If you receive such a mail with a non crypto client you see the plain text and a pgp-signature attachment. That is why Outlook shows it as "attachment".
Normal prio as I don't think that this is a regression.
Thanks for trying out the beta. I was about to open an issue about this as someone in the forum reported the same thing. https://wald.intevation.org/forum/message.php?msg_id=5759
- Aborting the keyresolver results in error code 5 in GpgOL
- Resetting the GnuPG Profile back to default in Kleopatra does not work.
- Add uid in Kleopatra results in General Error.
Apr 3 2018
Mar 29 2018
fixed with rev. 4fbbd134b865b1203b1914eb1623fa65aab8cb75
I might have changed the caller (GpgME++) but what convinced me that the change in core is better is that op_keylist_next sets the return value to NULL on error.
Mar 28 2018
Apologies for not replying to your mail directly. I've marked it in my INBOX to do the test with 3.0.3 first but have not gotten around to it.