<snip> >> Try downloading the Home version instead.
> I agree, TB! seems to be choking on the token issue. I'm going to try > installing Home version now to see if that helps. Will report back ASAP. > Thanks for your help so far. Ok, I downloaded and installed the Home version (BTW the Help/About screen still listed TB! version as being v3 Pro but I definitely removed every single trace of TB! - registry included so I'm assuming this is simply just another bug in TB! v3?) but that made no difference at all. The same annoying problem is still presenting itself. Any other ideas before I give up on TB! and start the laborious task of exporting everything over to Thunderbird? These numerous "Bat bugs" are just becoming too much now! :( On a somewhat related note, my email provider has issued a new POP3 certificate today but TB! keeps giving me the error: "TLS handshake failure. Invalid server certificate (The issuer of this certificate chain was not found)." Now, the certificate was issued by Comodo Group so I know there isn't a problem with the issuer and the old certificate they were using worked fine. The structure and issuer of the certificate is fine so why is TB! having such a problem with it? I even manually installed the issuer's certificate into TB! but it then reports "Invalid signature match" for the new POP3 certificate. The email account and associated certificates work fine in other email programs but TB! seems to have real problems dealing with certificates. Any ideas? Please. TIA -- ________________________________________________ Current version is 3.00.00 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
