https://bugs.kde.org/show_bug.cgi?id=332167
Bug ID: 332167 Summary: KMail is failing to encrypt PGP/Inline for non-signed key Classification: Unclassified Product: kmail2 Version: 4.11.5 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: kolafl...@kolahilft.de I can't send an PGP/Inline email to a receiver with an key I didn't sign before. If I sign the receivers key before sending OR use PGP/MIME everything's working fine. Reproducible: Always Steps to Reproduce: 1. Create a new email. 2. Encrypt the email and set the encryption-format to PGP/Inline. 3. Click "Send". Actual Results: KMail tells: It was not possible to create a message composer. Expected Results: E-Mail should be encrypted and send using the PGP/Inline format. I tried to find the bug searching in messagecomposer/composer/keyresolver.cpp https://projects.kde.org/projects/kde/kdepim/repository/revisions/6fce5eb967cc02398bcf9032959e48d0a3c64b78/entry/messagecomposer/composer/keyresolver.cpp Line 547 ValidTrustedOpenPGPEncryptionKey ) != item.keys.end() ) { // -= trusted? looks suspicious. I tried replacing it with: ValidOpenPGPEncryptionKey ) != item.keys.end() ) { Same for line 1575 NotValidTrustedOpenPGPEncryptionKey ); // -= trusted (see above, too)? I replaced with NotValidOpenPGPEncryptionKey ); But both didn't helped. I just got another error telling me, that the key is corrupt (it definitely isn't - I can use it for PGP/MIME and in Thunderbird it also works for PGP/Inline). -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs