The cert that we use is an actual valid cert issued by Verisign. Not a self signed cert. I just tried the make cert and it appears to have sent out correctly this time. I guess the question comes down to should a real cert be able to work? Or do you have to use the self signed certs?
Andy -----Original Message----- From: John Johnson [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 26, 2003 1:51 PM To: Andy Abshagen; [EMAIL PROTECTED] Subject: Re: [toaster] TLS Ok, This is strange.. Have you tried to make a new cert? -John ----- Original Message ----- From: "Andy Abshagen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 26, 2003 10:47 AM Subject: RE: [toaster] TLS > I've already been down that road. The file (not symlink) is owned by > qmaild.qmail with the correct permissions. > > And as I stated it has been working up until recently. We have been > on the server for about 8 months now. > > Andy > > -----Original Message----- > From: John Johnson [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 26, 2003 1:39 PM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: [toaster] TLS > > > IS the file a symlink? > > -John > > ----- Original Message ----- > From: "Andy Abshagen" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, March 26, 2003 10:28 AM > Subject: [toaster] TLS > > > > We have several boxes that we have used the Toaster on for some > > time. > > Starting today we have been receiving some messages that are bouncing > > back to our users with the following message > > > > TLS found not client cert in control/clientcert.pem > > > > I've looked the cert is still there and is valid. Any clues as to > > what might have happened? > > > > The error in the logs is > > > > @400000003e81eccf08e513a4 delivery 50964: deferral: > > TLS_found_no_client_cert_in_control/clientcert.pem/ > > > > Thanks > > Andy > > > > > >
