Bug 341760

When I receive a signed or encrypted email, objecttreeparser will properly verify or encrypt the email, and set the proper color in the email. What then happens is that the message signer and key id are displayed as whatever the latest key i added to my database is. This is merely a cosmetic issue, but it's incredibly annoying and may unveil a larger issue.
The issue lies in ObjectTreeParser::writeOpaqueOrMultipartSignedData. The contents of 'result' are correct, result = m->verifyResult(); returns the proper signing key information. The contents of 'key' however have the wrong key, and that's what ends up getting displayed. That is set by key = m->signingKey();.

I added debugging strings to track down the issue. My keystore contains 7 keys, for reference. 
My example email has been signed by mgorny. 
qDebug() << "There are " << key.numUserIDs() << " in the key of " << key.userID(0).email() << " ID"; for whatever reason returns "There are  4  in the key of  kristian.fiskerstrand@sumptuouscapital.com  ID", later debugging shows that key.keyID() equals 0B7F8B60E3EDFAE3.

Conversely 'result', which should contain similar information to key actually does not. 'result' actually contains the correct information, and reports the fingerprint as the correct key of B07A1AEAEFB4464E.

The issue here appears to be that either key = m->signingKey(); is returning the completely wrong key, or that different code should be used to return said key.

Reproducible: Always