how is that supposed to be helping the original poster?
I believe he was asking for a possibility to explicitly mark a certificate as trusted locally. To my knowledge Thawte & alia can only issue him an official one, which is not really what he was aiming for.
I would join the request for the possibility to store an exception for an otherwise invalid certificate just as I can (for example) in Firefox...having had the same problem in the past. The insistence of TheBat! in keeping complaining about the certificate at each and every connection is quite annoying.
Best regards
--
Viktor
Wednesday, April 6, 2011, 2:32:27 PM, you wrote:
| Hello, Search for VeriSign, Thawte, Comodo. -- Vilius From: tbbeta-boun...@thebat.dutaint.com [mailto:tbbeta-boun...@thebat.dutaint.com] On Behalf Of Simon Martin Sent: 2011 m. balandžio 6 d. 16:05 To: tbbeta@thebat.dutaint.com Subject: TLS + Self Signed Certificate Hi all, I host my own mail server (Courier). Being the cheapskate that I am, I use a self signed certificate for TLS/SSL connections. I am using the internal S/MIME and TLS implementation. I have had different scenarios in different versions. This is the current 5.0.8 behaviour: if I set the "Secure to dedicated port" option in the Account dialog then every TLS/SSL connection (IMAP or SSL) complains about the self signed certificate. Is there anywhere I can register my certificate to avoid these errors? Regards. -- __ _ Debian GNU User Simon Martin / /(_)_ __ _ ___ __ __ Project Manager / / | | '_ \| | | \ \/ / Milliways / /__| | | | | |_| |> < mailto: smar...@milliways.cl \____/_|_| |_|\__,_/_/\_\ Si Hoc Legere Scis Nimium Eruditionis Habes --------------------------------------------------------------------------- Freehosting PIPNI - http://www.pipni.cz/ |
________________________________________________________ Current beta is 5.0.6.1 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
