Comment 22 for bug 19065

@Matthias Heiler:

1. Download the Thawte root CA file by going here:
   http://www.thawte.com/roots/index.html
you can fill out bogus information. I did :-)

2. From Evolution / Preferences / Certificates / Authorities, import a new cert file.
Use the "Thawte Server Roots / ThawtePremiumServerCA.cer" file.
This file has an MD5 hash of "069f6979166690021b8c8ca2c3076f3a"

I believe Mikel Ward has this problem well described and I repeat the gist of his comments:

a. Evolution should not say a certificate is BAD when the problem is simply that it cannot verify the certificate because it does not recognize the Issuer as trusted. It should say UNKNOWN ISSUER, UNTRUSTED ISSUER, or something similar. BAD implied it failed some integrity check.

b. I also agree Evolution ought to be using an existing trusted certificate database. Certificate validation ought to be primarily an OS function, not an application function. If Evolution wants to keep user mail certs, that is fine. But when you go around sticking root CA's in a user app, that seems a little screwy to me.