Bug 321486 - wrong report about invalid gpg signature
Summary: wrong report about invalid gpg signature
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 4.10.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2013-06-22 09:59 UTC by Thomas Arend
Modified: 2018-10-27 04:05 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Arend 2013-06-22 09:59:05 UTC
when a gpg key has more than one e-mail address and the message with attachments is not send with the first e-mail address k-mail reports a wrong signature for the first mail address.

The send message is ok, but the received massage is wrong.


Reproducible: Always

Steps to Reproduce:
Send a Mai to yourself with a gpg key with more than one e-mail adress. 
Actual Results:  
Send message signature reported as ok.
Received message signature reported as wrong.

Expected Results:  
When the signature in the send message in the outbox is ok, the signature on the received message should also be ok.
Comment 1 Jan Hendrik Nielsen 2013-07-25 15:05:55 UTC
I can confirm this behavior on openSUSE 12.3 with kmail version 4.10.5.
Comment 2 Sandro Knauß 2014-03-30 22:54:34 UTC
can you upload an example mail, please?
'cause actually I have one gpg key with more than one e-mail adress and don't get invalid signatures. 

Also and test with 4.12 would be good.
Comment 3 Andrew Crouthamel 2018-09-25 03:40:21 UTC
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 set the bug status 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!
Comment 4 Andrew Crouthamel 2018-10-27 04:05:17 UTC
Dear Bug Submitter,

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!