I'm not really sure if "No Key" is a better string for "Ignore Recipient". But most other things are either unclear (ignore recipient) or can be misunderstood like (Do not encrypt to this recipient) as this could also mean that the recipient gets an unencrypted mail.
Thu, Jul 25
It now looks like this:
Tue, Jul 23
I installed microsoft office 2016 on a brand new laptop and got the same problem described in the post listed above.
My solution was to uninstall the pre-configured app : "Microsoft Office Desktop Apps" and voila!!
Jul 17 2019
Jul 15 2019
Jul 14 2019
I also tested it with Outlook 2010 and there this did not happen. So it's probably save to assume that this was a behavioral change in some more recent Outlook Version.
Has been released and confirmed to be working.
Fix is in, will be released with 3.1.10
Fix is in. Will be released with 3.1.10
This is resolved
It turned out to be a downstream issue and the change in message class was enough from our side.
This is fixed.
This was fixed with 3.1.9
This should be fixed.
Testing with the DGN certificate showed that GPGSM returns a signature verification error (invalid digest algorithm) in this case. So the signature summary is not even checked.
Jul 4 2019
Jul 2 2019
This issues is not really about the CRL's. GpgOL should not activate the EFail protection if a CRL check fails. That is the issue here.
We need to know the issuers of the CRLs under question.
See also T4538 which we can only fix in 2.2 after we have checked that this does not break the VS-NfD approval.
Jul 1 2019
Sorry for the delay, I was on my summer vacation ;-)
@joaociocca Can you please try to update to Gpg4win-3.1.9 and try again.
Jun 24 2019
I just received answer that this is still a problem in the current release.
Jun 19 2019
I'm so sorry. It was a problem with mail server, not a GpgOL bug.
Jun 18 2019
Jun 11 2019
as usual, thanks for your help.
Jun 8 2019
I'm having a very similar problem in 3.1.5! Randomly, when I try to view a PGP-signed e-mail, nothing shows, both on preview panel and when I open the message.
Jun 7 2019
File->Save As now works for crypto mails. It saves the encrypted message.
This works now, the hidden BeforePrint Event enabled us to detect when a print happens and the old code to do blocking decrypts enabled the actual printing.
We also do not print "our categories" (encrypted message, level x trust),... anymore, even in quick print.
Jun 4 2019
The change in message class did not help.
Works for me
Jun 3 2019
May 28 2019
My understanding of this issue and the fix for it is that Outlook with exchange detects that our mails are S/MIME mails. As the attachments are modified by us outlook wants to save the changes on move. This fails because it can't do the crypto. Leading to the error. This also happens when such a mail is closed.
We did not remove the "<>" from the content id. This worked for the first display but when forwarding they got doubled and it broke.
The code had the assumption that a content-id
could only exist on an attachment for HTML mails as it otherwise
does not make sense.
May 27 2019
I was able to reproduce this when I forwarded the mail after opening it in a new window. Somehow that appears to influence it.
May 24 2019
May 20 2019
Closing this as the moving problem was fixed.
May 16 2019
That was obvious. rG6fc5df1e10129f3171d80cf731f310b9e8d97c26 fixes this.
When doing a "gpgsm --with-validation -k foo" (assuming you have a cert foo) gpgsm now goes into a loop and prints the certficates that match "foo" over and over again. I have not tested if it was caused by this change but I think it is likely.