Hello List! I've been lurking the list(s) since December (when I bought TB1.62r) and had a couple forays into the archives but have not yet found a way to get SSL/TLS working for me on any servers with that capability.
I really need your help here- detailed steps, if possible, would be most appreciated. The first day TB!2 became available for upgrade I jumped as well used every beta since December in an attempt to get this to work. About my 3 problem mail accounts: AKO- us.army.mil is POP3, IMAP4 (preferred), and SMTP, all SSL secure to dedicated and require authentication for use. Server Cert is DOD issued and the entire chain has been imported to system trusted root store. MRB- .myrealbox.com is POP3, IMAP4 (preferred), and SMTP all allow secure to dedicated and StartTLS option, I have to authenticate to SMTP to send past my ISP... Server cert is Comodo issued but has a goofy *.myrealbox.com server name that TB refuses to entertain. I'm not sure how to import their cert to system trusted root store- I don't know how to download a .p* or .cer from the site... Cotse- pop.cotse.com (POP3) and www.cotse.net (SMTP) only and allow secure to dedicated port and StartTLS option. The POP cert is a self CA job and the SMTP cert is issued by Equifax. I have requested they send me a copy of the certs used so I can import them to root... More about my ultra-frustrating problem <g> On AKO I can finally direct connect to pop and imap, not sure what happened here to allow this, but I cannot send SMTP secure (I can send plain though)... I really need the dialog box that pops up and asks to trust this cert to have an enabled 'add to trusted' button. TB continues to complain of the certificate heirarchy... Getting this one working properly is critical, especially smtp since the pop and imap work when I keep eyes on for popup dialog... On MRB I get absolutely nowhere, TB complains of server and cert not matching pop3/imap/smtp.myrealbox.com is server name, *.myrealbox.com is the cert name presented... I really need to get this one working, at least to prompt me for permission rather than silently fail- every single time... On COTSE, neither the pop nor the smtp work, the failure is during the TLS handshake and again is silent- no user prompt to accept nor add to trusted. Is there really any reason this process has not been made simple to the point of fool proof? (maybe a post to tbbeta about that;) I use JBMail3.2 off a USBkey drive and it works flawlessly, asking me the first time if I want to trust the cert and making a hash of it from there, once done- there are no issues unless there is a change. I must say I love TB, especially since IMAP has developed so nicely, but when I bought it in Dec- the version change log was what made me decide TB was for me and that was the exceptional (sounding) SSL/TLS support as well integrated certificate function and PGP support. ok, I know I talk alot, especially for my first post and all- but if you can feel my pain I beg you to reply as detailed as my described plight is... -- Most Sincerely, Mark (aka- Army RedLeg) Using TheBat! 2.00.6 on Win2ksp3+ (plus all patches:) ________________________________________________ Current version is 2.00 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
