Moving am email without a GPGOL_UID_DASL fails.
The Fix for T6646 will return the Internet message id and the folder event code didn't handle
tahts yet as the ribbon callback code.
Moving am email without a GPGOL_UID_DASL fails.
The Fix for T6646 will return the Internet message id and the folder event code didn't handle
tahts yet as the ribbon callback code.
rO GpgOL | |||
rO75f46829054e Moving encrypted emails to folder fails |
I could not reproduce this issue with Gpg4win 4.4.1 (which should have it).
So my finding that with Gpg4win-5.0.0-beta345 moving an encrypted message to a folder works, too, is of dubious value…
Moving an encrypted message on Gpg4win-5.0.0-beta357, Outlook LTSC Standard 2024 @ win10 into an inbox subfolder of Ted.Tester and back works for me, too. Does this confirm, that it's working now?
All mails touched by gpgol should already have a GPGOL_UID_DASL. So to replicate:
I could replicate this with both Gpg4Win-4.4.1, Outlook LTSC Standard 2024 @ win10 and unfortunately also Gpg4win-5.0.0-beta369, Outlook LTSC Standard 2024 @ win10. The mail is not moved and just stays in the inbox. It also does not work on retries. So the problem seems not to be solved.
Here's a gpgol.log (Gpg4win-5.0.0-beta369):