tested and this works.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Sep 14 2022
Sep 7 2022
Sep 5 2022
This is now in
Sep 1 2022
Sorry for the confusion ...
There was no single gpgol-File for deletion.
There were 100.000 other files from other programs.
No idea, why this has interferred with gpgol, but it obviously has.
Ok. So I never assumed that you had actually 100 gpgol_enc_number.dat files lying around.
Aug 31 2022
I had a look into my \AppData\Local\Temp and found some 10,000 Files/Folders (nearly 100,000 files in total) with over 10 GB.
After deleting most of them, GPG4WIN 4.0.3 is working!
It's strange that the problem only occurs locally on one machine. I set up a test bench and did not experience the same errors as before.
Thanks a lot. Due to your log I have tried with a long username and umlauts and a dot in my username. My test name was Längül!ödiföäada.dad which is the longest that Windows allows. But It still works for me. Even if I create one or two gpgol_enc.dat files in %TEMP% It still works:
... Logging active, standard, with email content and meta information
I have produced a log using 4.0.3.
See attached.
Aug 30 2022
strange, I have not received one. Did it bounce somewhere maybe because of size? Encryption should compress this though.
Ok, email sent
Aug 29 2022
Please, Last chance to add a log with Included file names (Include data checkbox) before the next release. Me and a colleague reviewed the function and don't find an issue with it. Otherwise I will only add a MessageBox error in that case for the next release.
Aug 26 2022
@SPYazdani But your log is also without the Data information. The issue is that I see the Problem that it tries to aquire a temporary file name and fails to get one. Then it runs into an unexpected state. But gpgol_string_107 is the pseudonomized debug output of the filename. Because the filename would include your username. And I need to see what GpgOL tries there and why this would fail.
@aheinecke I posted a link to the logs in T6158
This was reported again in T6158. The problem is still that I have not seen a log with Data debugging enabled. @SPYazdani could you maybe create one? Please enable logging and check the box below the logging filename where it says "Include Mail contents (decrypted!) and meta information." and then you might afterward look into the log file and post here the lines above "Could not get a name out of 100 tries" I am interested in the candidate names and also please then check if those files really exist and if so try to remove them.
Ah right, forgot about this issue. I merge it with the other one and answer there. I need a log with data debugging enabled of this issue.
Aug 24 2022
Aug 23 2022
Aug 22 2022
Aug 13 2022
As mentioned in T6134. The overlayer encoding is still broken and only as a workaround uses verschlusseln instead of verschlüsseln in german. Should be fixed once and for all.
Aug 12 2022
Aug 5 2022
Jul 29 2022
Jul 14 2022
Jul 13 2022
As discussed with Markus I'm changing the assignee
Jul 12 2022
Jun 30 2022
Please find the requested log attached.
I don't know, where to look for such a file (candidate).
Jun 29 2022
I think it's worth noting that this is not restricted to encrypted e-mails but signed-only e-mails also.
Thanks for the log and the analysis so far. In the log it is visible that the problem is that gpgol cannot create a temporary file to store the mails contents. Due to this it fails later as it has no data to encrypt. The storage as a temporary file was added in 3.1.16 to allow more embedded outlook objects since we now ask Outlook to first serialize the file. I wonder why this only occurs to very few people. Obviously it works for most people, including me.
Jun 28 2022
Thank's Diedrichs for this hint.
Here it works again using Gpg4win V.3.1.15.
Jun 26 2022
I've tried a few things now. Reinstalled Office, reinstalled GPG4win, reset Windows 11 with recovery when still worked. Nothing helped.
Jun 25 2022
Jun 24 2022
oh no
Jun 23 2022
No, unfortunatelly problem is still existing.
Jun 22 2022
Hat sich das Problem gelöst? Bei mir tritt das seit gestern auf auf. Ich kann nichts mehr signieren oder verschlüsseln. andere Plugins habe ich deaktiviert, es beliebt trotzdem.
Jun 7 2022
May 24 2022
May 23 2022
Curious as to whether there's been any update on this. GPG4Win is the only approved whole email + attachment encryption solution on this end, and we're having trouble with inline images showing up as attachments only in Outlook 2016 (using GPG4Win 4.0.2). Of course, as you said, at least the attachment isn't being lost; however it does make reading rich emails more difficult.
May 19 2022
May 13 2022
Please disable all other Add-Ins as well as extra security tools running on that machine to see whether there is some interference with them.
May 9 2022
I am closing this as the group support for gpgol is now in T5967
Still needs testing as this is a default off feature.
This needs to be tested with group configuration even for non mixed mode. There is an important wish to have the kleopatra group configuration be used in the keyresolver from outlook.
Apr 28 2022
Please try a decent version of Gpg4win - we have fixed dozens of bugs in the mean time If the problems persists, please re-open this bug.
Conflicts between Add-Ins are often unavoidable. We have a list of known issues at:
https://wiki.gnupg.org/GpgOL/IncompatibleAddons
If you have more information on that ESET thingy please enter it into the above wiki or leave some description here.
Apr 25 2022
is there any update ? I having the same Issue here on Windows 11 Pro, Outlook Version 2203 (Microsoft 365) 64bit
Any idea? Any update?
Apr 22 2022
Apr 20 2022
Apr 8 2022
gpgol.txt uploaded
Have you selected an Output file in a location where you can write files with your permissions?
I had already tried both, to deselct all other add-ins and to select all possible add-ins.
No change of the behaviour.
Could you please create a log file using the debug settings with Outlook Object Model debugging enabled?
Mar 28 2022
we have a similar problem in our organization. We're using Outlook from Office 365. For two weeks now we have set a GPO for Outlook to prefer plain text messages like in @kimmoal's organization environment.
This causes the same problem: We are getting blank emails when they are encrypted or signed.
Mar 18 2022
I had some more time to test this bug.
Mar 17 2022
we replace the encrypted text and attachments with the decrypted / verified parts