After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 599689 - Evolution does not use latest Certificate
Evolution does not use latest Certificate
Status: RESOLVED DUPLICATE of bug 372435
Product: evolution
Classification: Applications
Component: Mailer
2.26.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-10-26 20:03 UTC by Guido
Modified: 2010-05-20 18:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Guido 2009-10-26 20:03:47 UTC
I got a new VeriSign certificate as a replacement for my Thawte certificate. After importing the new certificate Evolution still uses the old certificate. Even if removed from the list of certificates. 
(I can verify that by doublechecking the serial number. I made sure that settings under "Mail accounts" -> "My Account" -> "Security" -> "Signing certificate" are ok. -> new cert. selected.)

Let me know if you need any additional Information.
Comment 1 Guido 2009-10-27 07:43:41 UTC
I sent a test message to an other account of mine. When checking the (my) senders certificate there it turned out that Evoltion _does_ use the correct certificate. 

So it seems that there is a mistake with viewing signatures sent to myself.

Just to make sure:
 - I have two certificates which are currently valid
 - I sign outgoing messages (Evolution is configured in that way, that it should use my latest certificate)
 - When sending signed messages to my own account checking the signature reports that the old certificate has been used.
 - When sending signed messages to an other account checking the signature reports that the new certificate has been used.
Comment 2 André Klapper 2009-10-28 16:58:21 UTC
Please never set the gnome target field yourself. Thanks.
Comment 3 Milan Crha 2010-05-20 18:18:54 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 372435 ***