Today, when I tried to send an encrypted mail in kmail, kmail would respond with the error message "Could not compose message: General error". Initially, I thought I might have hit bug 324963, when indeed the problem was caused by an expired key specified in an "encrypt-to" statement in my gpg.conf. gpg does give an error message in this case: > $ gpg -e > gpg: F481DB0F8A627E7E: skipped: unusable public key > gpg: [stdin]: encryption failed: unusable public key Please include the gpg error message in the error dialog. A "general error" is not helpful at all to the user.
Indeed we need to add better info. I will investigate it.
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
As of kmail 5.2.3, the proper error message is included. I.e. for the situation described in the original bug report, kmail now tells me "Could not compose message: unusable public key".