This is being displayed on some messages for which I don't have a public key: "Not enough information to check signature validity." Screenshot: http://picpaste.com/not_enough.png German: "Es sind nicht genügend Informationen zur Überprüfung der Signatur vorhanden." Instead KMail should tell me that it misses the public key and give me the key id of that key, so I can start searching for it. Thunderbird+Enigmail handle the same email much better, telling me "Unverified signature" and then there's a details button giving me the public key id. (there's no details button in KMail) Here's a copy of such an email without private details. If someone needs an original copy for debugging (without blackened stuff) send me an email and I'll send it to you. I just don't want to make the whole email completly public because it wasn't written by me. ---------- Return-Path: <mitglieder-bounces@lists.fux-eg.org> Delivered-To: [...] Received: from localhost (cubox [127.0.0.1]) by [...] (Postfix) with ESMTP id [...] for [...]; Tue, 9 Aug 2016 [...] Received: from [...] ([127.0.0.1]) by localhost ([...] [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id [...] for [...] Tue, 9 Aug 2016 [...] Received: from [...] ([...] [[...]]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by [...] (Postfix) with ESMTPS id [...] for [...]; Tue, 9 Aug 2016 [...] Received: from [...] ([...] [[...]]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by [...] (Postfix) with ESMTPS id [...]; Tue, 9 Aug 2016 [...] Received: from [...] (localhost [127.0.0.1]) by [...] (Postfix) with ESMTP id [...]; Tue, 9 Aug 2016 [...] X-Original-To: mitglieder@lists.fux-eg.org Delivered-To: [...] Received: from [...] ([...] [[...]]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by h07.hostsharing.net (Postfix) with ESMTPS id 5227AC9436; Tue, 9 Aug 2016 [...] Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by [...] (Postfix) with ESMTPS id [...]; Tue, 9 Aug 2016 [...] Received: from [192.168.1.4] ([[...]]) by mail.gmx.com [...] Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) In-Reply-To: [...] Date: Tue, 9 Aug 2016 [...] Message-Id: [...] References: [...] To: [...] X-Mailer: Apple Mail (2.1510) X-Provags-ID: [...] X-UI-Out-Filterresults: notjunk:[...] Subject: [...] X-BeenThere: mitglieder@lists.fux-eg.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mitglieder der Fux Genossenschaft <mitglieder.lists.fux-eg.org> List-Unsubscribe: <http://lists.fux-eg.org/options/mitglieder>, <mailto:mitglieder-request@lists.fux-eg.org?subject=unsubscribe> List-Archive: <http://lists.fux-eg.org/private/mitglieder/> List-Post: <mailto:mitglieder@lists.fux-eg.org> List-Help: <mailto:mitglieder-request@lists.fux-eg.org?subject=help> List-Subscribe: <http://lists.fux-eg.org/listinfo/mitglieder>, <mailto:mitglieder-request@lists.fux-eg.org?subject=subscribe> From: [...] Reply-To: [...] Cc: fux Mitgliederliste <mitglieder@lists.fux-eg.org> Content-Type: multipart/mixed; boundary="===============[...]==" Errors-To: mitglieder-bounces@lists.fux-eg.org Sender: "Mitglieder" <mitglieder-bounces@lists.fux-eg.org> --===============[...]== Content-Type: multipart/signed; boundary="Apple-Mail=_[...]"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_[...] Content-Type: multipart/alternative; boundary="Apple-Mail=_[...] --Apple-Mail=_[...] Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 [...] > _______________________________________________ > Mitglieder mailing list > Mitglieder@lists.fux-eg.org > http://lists.fux-eg.org/listinfo/mitglieder --Apple-Mail=_[...] Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "> [...]</div>= </div> <br = class=3D""></div></div>_______________________________________________<br>= Mitglieder mailing list<br><a = href=3D"mailto:Mitglieder@lists.fux-eg.org">Mitglieder@lists.fux-eg.org</a= ><br>http://lists.fux-eg.org/listinfo/mitglieder<br></blockquote></div><br= ></div></body></html>= --Apple-Mail=_[...]-- --Apple-Mail=_[...] Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org [...] -----END PGP SIGNATURE----- --Apple-Mail=_[...]-- --===============[...]== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline _______________________________________________ Mitglieder mailing list Mitglieder@lists.fux-eg.org http://lists.fux-eg.org/listinfo/mitglieder --===============[...]==-- Reproducible: Sometimes
= Correction = I still get the message after importing the key. So: 1. KMail should provide more details about what's going wrong in general. 2. Fix this specific bug. If you tell me where I can get some debug output (KMail doesn't seem to have an "-v" verbose option) I'll happily provide it! Maybe related: https://bugs.kde.org/show_bug.cgi?id=323168
The message/warning only disappears when i set the certificate trust to "ultimately". The message is very unclear: it should at least mention trust level, and maybe link to kgpg. IMO "ultimate" trust ievel is a bit much to demand anyway.
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!