- User Since
- Mar 27 2017, 4:49 PM (146 w, 6 d)
Fri, Jan 17
An updated build is available here: https://files.gpg4win.org/Beta/gpgol/2.4.6-beta3/
Thu, Jan 16
Yes that is fine with me.
thanks for the report. This is definitely a sore spot and we need to look at it again. I did some experiments a while a go trying to fix this issue but so far I was unable to get to stable results so for now this is a known issue.
I'm a bit suprised that the workaround with not having the mail open does not work for you.
Is this about any special version of Symantec? As far as I knew Symantec Endpoint Security Desktop (or whatever they call it nowadays) supports reading PGP/MIME and even sending it if forced.
That error always occurs when the Exchange Server is unhappy with the structure of our PGP/MIME Mails. It has nothing to do with S/MIME, that is only because Exchange only knows about S/MIME, so our PGP/MIME Mails also claim to be S/MIME mails.
Display now looks good to me in all cases. We still keep the subject when a reply / forward is done, but that is the same as before. To do this properly I would have to actually do the protected headers sending,.. as then I could automatically flag such a message to be sent with protected headers. But that would be a new feature and I rather work on properly doing BCC sending as the next privacy enhancing feature.
Mon, Jan 13
Fri, Jan 10
Thu, Jan 9
I'll keep this on needs triage because I don't know what the issue could be. I have a yubikey 5 at hand and just tested it with Gpg4win 3.1.11. It works without problems.
Wed, Jan 8
note that it *does* sometimes hide the legacy display part, for some messages, including unfortunately-complex -- that's good! -- but maybe this points to some internal inconsistency:
Tue, Jan 7
Mon, Jan 6
Mon, Dec 23
there is no way to handle this correctly with such messages. The PGP Standard says that PGP Messages may have every encoding. This is a reason why we always talk about "you should use PGP/MIME" as this is basically PGP with added handling for content meta information like the text encoding.
Dec 20 2019
This is fixed now.
Dec 19 2019
This is fixed in Gpg4win-3.1.11
Related task: About subkeys is T4028
Prio raised and assigned to werner as he asked for it.
Dec 18 2019
Dec 17 2019
As a note: They can still be saved when doing file->save as from the message list or by using drag & drop.
We currently do not have the resources to work on it as our focus is more on GpgOL.
Dec 16 2019
Thank you for the good report.
Thanks for the report.
Thanks for the report but I cannot reproduce the issue :-/. In multipart alternative mails GpgOL takes the text part if text mode is set in Outlook.
Will be released with 3.1.11
This is done in 3.1.11
Will be greatly improved with 3.1.11