+++ This bug was initially created as a clone of Bug #386468 +++

Figured it'd be better to have a separate bug for this issue...

Please describe the problem:
I'm going to attach a message that is encrypted to the following test key: http://johannes.sipsolutions.net/files/testkey.asc

The message is signed by my key as gpg shows:

johannes:~$ gpg --decrypt /tmp/msg

You need a passphrase to unlock the secret key for
user: "Some Tester (never use this key) <testkey@example.org>"
1024-bit ELG-E key, ID B6F004FF, created 2006-12-16 (main key ID 4C6B3A42)

gpg: encrypted with 1024-bit ELG-E key, ID B6F004FF, created 2006-12-16
      "Some Tester (never use this key) <testkey@example.org>"
This is just a short test message.
gpg: Signature made Sat 16 Dec 2006 12:27:37 PM CET using DSA key ID 9AB78CA5
gpg: Good signature from "Johannes Berg <johannes@sipsolutions.net>"
gpg: [...]

But evolution claims that it is not signed!


Steps to reproduce:
1. import the secret and public key from the attachments to bug 386468
2. import my public key 9AB78CA5 from a keyserver
3. import the message from the attachment to bug 386468
4. view the message

Actual results:
"encrypted" and lock with green check is displayed, clicking the lock shows "not signed"

Expected results:
clicking the lock shows that it is signed by me

Does this happen every time?
yes