- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jul 7 2020
Jul 3 2020
Jul 2 2020
Hi,
could you please change the edit policy back to all users so that I can change the status of this task?
Jul 1 2020
I think this might be the issue with High DPI support problems. T4819 which is not yet released.
Jun 9 2020
Jun 8 2020
Argh, I had overlooked that you even mention a pull request.
So Apologies that I did not attribute the fix directly to you.
Thanks for the nice report. The fix was completely straightforward, I just didn't think about rich text when I implemented it.
Jun 5 2020
MAPI Namespace has a pickFolder method which can be used here.
Jun 4 2020
This was the underlying reason behind the data loss described in the wald issue.
Jun 3 2020
Jun 2 2020
The problem is with the code for T3656
Thanks for the report. I can reproduce this by replying to S/MIME enc & sign mails.
While triaging issues this looks to me more like a support case. And not an issue of the software itself. So I'm closing this issue.
Uh, I just noticed that this issue is from dec. 2019 I am unsure why I overlooked this and only noticed it in my regular tracker check today.
@JJworx Thanks for the suggestion / feature request.
May 27 2020
May 26 2020
May 25 2020
May 19 2020
This was implemented 0d2db8b81ab24e2ab02d7ba6832cabd07b72f852 in Gpg4win-3.1.11 but does not work reliably.
Closing with Info Needed.
I'm moving this from testing to open again. Especially the deletion is an issue. I had a report that even for a sent mail Outlook.com also stores an unencrypted variant in the "Trash Bin".
Works nicely
This was released in December 2019
May 18 2020
May 15 2020
Thanks for the logs. I can see the crashes, but I can't make heads or tails of them. We crash in completely valid code. I really don't want to play the blame game here but to me this would be explainable if there is an issue with refcounting in the GFI plugin that would release the IMessage or ISecureMessage MAPI Object from the ItemLoad event once to many. In that case the object we work with might be deleted at random times and that would explain it.
Thought of a way to at least mitigate it. When a mail is closed we know it's not printing.
After looking at this for 4h I could not see a way to detect it better when a print job is done. So we now treat every ItemLoad of a mail after we have seen the BeforePrint event as a print.
Outlook is a bit nasty here:
May 14 2020
May 12 2020
could you please go into the GpgOL setting and under "Debug" turn on logging on the highest level (+code trace) and then reproduce the crash and add the log here?
Including Data should not be needed so you can keep that checkbox unchecked to avoid having mail data in the logs.
This might help us to see where and why the crash occurs.
May 8 2020
I'm not sure what to do here. The problem is that all users in clients without PGP/MIME Support will see the attachment names. That is why we use the names as they are.
There was a similar Problem in the past reported on our mailing list: