Hi David,

On  Thu, 12 Oct 2006 13:40:47 -0400 UTC (10/12/2006, 12:40 PM -0500 UTC my
time), David Calvarese wrote:

D>>> Really?  I'm having no problems using TB! with IMAP and SSL.

>> I reported this earlier, 3-4 weeks ago.  I have a remote server that only
>> accepts SSL connection... the SSL cert has just expired... The cert is in my
>> root TB! chain, has been for years. TB! will not allow me in, even though I
>> (or anyone) must authenticate. That IMAP server does not allow port 143,
>> regular connection, just dedicated SSL IMAP on port 993.

>> Since the cert has been good for two years, just recently expired, TB! has
>> decided it will not allow the connection... Every other IMAP client on the
>> planet allows me to connect except TB! I do not like it when an email client
>> tells me what it will or will not accept in an SSL connection, not putting
>> that decision in the user's hands. It seems to forget that I must
>> authenticate anyway. Since I cannot connect to this IMAP server, I cannot
>> use TB!  The address book, trusted CA should not dictate whether to accept
>> the connection just because the cert is out of date. That is my decision.

D> That is certainly odd...  Sounds like a bug to me.

It is a bug (or RL's decision). RL has known about it for a long time, since
starting IMAP into TB!, yet nothing has been done to date to correct it.
Curtis has mentioned it long ago in this forum, several times, as have I,
and a few others using IMAP.

-- 
Gary





________________________________________________________
 Current ALPHA is 3.86.03 | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
IMPORTANT: To register as a Beta tester, use this link first -
http://www.ritlabs.com/en/partners/testers/

Reply via email to