Ok, I'll see if importing will work also. But initially it said I needed to import it, and I did that, the error I get now is that the name doesn't match. So if I create a new cert with the correct name, then obviously import, that should be the end of the errors. So once I get my staff's computers to import a correctly named cert and the error doesn't come back, I can live with that.
Thanks John On Tue, Aug 26, 2008 at 1:51 AM, Jake Vickers <[EMAIL PROTECTED]> wrote: > Tek Support wrote: >> >> Thanks, I'll do that, and do I need a 3party signed cert (like HTTPS)? >> >> > > The reason you're getting the other error is because the cert is not signed > by a trusted authority. If you don't have it signed by a trusted authority, > you'll be getting the same error unless you import the certificate (in which > case you might as well import the current one - it's a self signed cert is > all). > > --------------------------------------------------------------------- > QmailToaster hosted by: VR Hosted <http://www.vr.org> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
