- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 5 2019
Log loops with:
I have a hang now when keylisting in Kleo with GPGME_DEBUG=9:
Jun 4 2019
Just to clarify, you were able to decrypt and extract it without error? Which tool did you use to extract the tar archive?
The change in message class did not help.
Works for me
Jun 3 2019
Maybe the file was encrypted with a version of gpg4win-3.1.5? We had a serious bug there that sometimes files were corrupted. See: T4332
May 29 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.