Well, that is a detailed bug report. Thanks.
Ok. If you can confirm that then it means that my analysis is right. Still unexpected to get an error there. I have to do some more tests with Exchange Online but that would be another issue. If this issue is fixed by turning of debugging then it will also be fixed by my patches.
Mon, Nov 19
You are right that Outlook behaves normally if debugging is deactivated.
I had major problems with 3.1.4 and never used it until 3.1.5 came
along, so I guess it might be an existing problem.
While I can't reproduce it myself (because I probably don't have the right mails in my exchange) looking at your log I think that I see the problem there might be an issue with the error handling in openProperty. So for old mails the openProperty probably fails because we have exchange online for that and the property is not yet available in Outlook and then the error is not correctly handled and it crashes.
This should be fixed in commit fd34415bdd57332424bd5a98d279e2331678a2fb
Was released with 3.1.5
Was released with 3.1.5
Sun, Nov 18
hm, adding: --with-tar=tar to my invocation of ./configure appears to leave gpg-zip with:
My problem isn´t linked to forwarding encrypted e-mails and / or attachments. It occurs by ordinary PGP mails WITH attachments which are not ASCII format. Encrypted e-mails without attachmoments or in ASCII format will be delivered.
Sat, Nov 17
oh! i suppose i underestimated the severity of it. apologies!
Form my understanding this needs to be fixed urgently.
Fri, Nov 16
So for me, sending encrypted attachments by selecting them from disk works fine for attachments. up to ~200k (I haven't tried larger ones).
Pretty obvious. Thanks.
Thu, Nov 15
I have a warning already in my working copy.
I fixed the gpgrelay link.
Wed, Nov 14
"Miranda ICQ [Unix] CHAT" also doesn't work. Maybe it would be a good idea to check all of them via script or something like that...
i don't see any active use of it in all of debian: https://codesearch.debian.net/search?q=gpg-zip
Thank you very much for the quick response and try-out in detail!
Bug or user error?
It is useful if you often log out and in, for example using remote remote ssh session. If you don't like it, you should "gpgconf --kill gpg-agent" in your .bash_logout. ~/.xsession or whatever your system uses. Instead of --kill you can also use --reload so that the passphrase cache is flushed immediately and not only at the end of the TTL.
Thanks. Just pushed the change to master.
Let me also note that gpg-zip was not installed since 2006 due a conflict with gpg1.
gpg-zip is deprecated because we have replaced it by gpgtar. Given that you have a workaround for Debian I tend to close this bug as WONTFIX.
Thanks for reporting your problem. We are highly interested in any crash. But please note that our minimum supported Exchange Version is 2010 because 2007 has reached end of life in april 2017. So I cannot test with that Server.