You know to be quite honest i get the same error message with mine no matter what, self signed, etc.
But i'll be honest, it works JUST fine in Mutt, and Mulberry which are my only SSL based applications i test it on. Same error message as you, so i wouldnt worry as much about 'imtest'. It's not foolproof, nor is it 100%. --On Friday, May 10, 2002 10:41 AM -0500 Thaddeus Parkinson <[EMAIL PROTECTED]> wrote: > Jason (and the rest of the Cyrusians out there), > > Thanks for the suggestions. The new certs definately get me different > messages. Now I receive a 'verify error:num=27:certificate not trusted' > on the CA file. I think this might be a problem with imtest not trusting > the CA, anybody have any idea of how to make it see the light? 'openssl > verify' has no problem with them... > > However, it still continues past that and dies in the same spot it was > before. Still not sure if they're related; it's quite irksome. > > I have a new option today, though. As if perhaps an answer to my prayers, > the Fates released a new version of OpenSSL last night. I'm going to > upgrade to 0.9.6d. Keep your fingers crossed that it'll miraculously cure > all of my headaches. > > Thanks again, > Thaddeus Parkinson > >
