Hide Forgot
Description of problem: Cannot sign or encrypt with S/MIME. Version-Release number of selected component (if applicable): evolution-3.0.3-1.fc15.i686 nss-3.12.10-6.fc15.i686 How reproducible: Every time Steps to Reproduce: 1. Import certificate / private key pair 2. Select certificate in email account settings 3. Compose and send signed message Actual results: Evolution does not send message and shows this error message: Could not create message. Because "Cannot find certificate for 'ID COMODO CA Limited de'", you may need to select different mail options Expected results: Sign and send message Additional info: The certificate is a COMODO free email certificate from here: http://www.comodo.com/home/email-security/free-email-certificate.php It imports fine and evolution can even decrypt messages with the private key. It works with Thunderbird. The email is in a E= field quite deep in the cert, not in the CN, this cannot be changed as it is sent by COMODO.
Thanks for a bug report. I let them generate one certificate for me an, then imported it into evolution and selected in the correct email account, in Security options, for bot signing and encrypting. Then I opened a new message, selected this account for "From", and then sent myself three messages, one with S/MIME signed, one with S/MIME encrypted, and one with both S/MIME signed and encrypted options on. I understand from your description that you did exactly the same, thus the difference can be package versions, as I'm using: nss-3.12.10-7.fc16.x86_64 nspr-4.8.8-4.fc16.x86_64 and evolution git master, which has no special changes in this area from yours 3.0.3, as far as I know. I noticed one difference in Edit->Preferences->Certificates in evolution. The imported Comodo certificate shows in Purposes only "Encrypt", where my other personal certificates has there "Sign, Encrypt", though opening the certificate with "View" button shows same values at the top of the General tab, mentioning "Email Signer Certificate" and "Email Recipient Certificate".
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping