Bug 244260

Description of problem:
mail-notification cannot verify some valid ssl certificates, and instead
requires the user either not to connect or to accept an unverified certificate.
In my particular case, my IMAP server is using a certificate from a slightly
uncommon certificate authority - I don't know if that's necessary for the
problem. The fix I give below would suggest the problem's broader than that, but
I don't have another IMAP server with which to test.

Version-Release number of selected component (if applicable):
4.0-2

How reproducible:
Every time

Steps to Reproduce:
1. Create a CA, (or use cacert.org)

2. Install your CA root certificate in /etc/pki/tls/certs (put a copy or link to
the cert in pem format in that directory, under the name HASH.0 where HASH is
the output of
openssl x509 -noout -hash <yourcertfile.pem

3. With your new CA, sign a certificate and configure an IMAP server to serve
ssl imap with that certificate. (sorry to abbreviate so much here - let me know
if you need more info on how to do this).

4. Try to monitor a mailbox on your new ssl-protected imap server with
mail-notification 
  
Actual results:
A dialog claiming the certificate isn't valid, asking if you want to proceed.

Expected results:
Success (mail-notification happily monitoring your mail, with no dialog
(validation of the certificate you configured for your imap server succeeds)).

Additional info:
stracing the mail-notification process shows it doesn't look in /etc/pki/tls or
anywhere else.

See the bug in the original project (19578 on savannah.nongnu.org) at the URL
given above.