Pages: 1
RSS
Problem with TSL(SSL), receive and send fail
 
Hi:
 My log as below,how can i solve the problem?


log:
2009-6-19, 11:26:11: FETCH - The server does not support TLS, it uses SSL protocol version 3.0 which is outdated and insecure (version 3.1 known as TLS is required)
Edited: Ricken Ge - 19 June 2009 07:16:20
 
Does that means only when my ISP update to TLS ,I can use my favourite bat? :cry:
 
You might consider collecting your mail with a regular connection, skipping the (false?) security of SSL alltogether.
__________________________________
I'm just a user of The Bat! I don't work for Ritlabs.
 
Thanks for your response in such a short time :D
My problem is our company requires using SSL,regular connection is not allowed.

The requirement is:
pop ssl 995
smtp ssl 465

our mail server maybe too outdated i guess,but making them to update it is not realistic.
I extremely prefer bat to other clients(I'm a ThunderBird user before),could you give me any other suggestion?
 
I have the same problem!

Have you managed to fis it so far?
 
No, I've given up
 
I have the same problem when want to receive mail by the bat! from company.solution???
 
what program reports in account log?
 
the bat!pro Ver4.2.12.2
the function of The bat! is very good.but if can't use,this is a pity.
 
enter last entries from account log (Ctrl+Shift+A), then we can try to help You...
 
2009-11-3, 23:15:34: FETCH - receiving mail messages
2009-11-3, 23:15:35: FETCH - Initiating TLS handshake
!2009-11-3, 23:15:35: FETCH - The server does not support TLS, it uses SSL protocol version 3.0 which is outdated and insecure (version 3.1 known as TLS is required)
 
well, everything is written in log, server has insecure support of SSL 3.0 only, this version was introduced in 1996 and can not be used in The Bat! for secure connection
 
This is very regrettable that it can't support SSL3.0. More user can use the bat! If the question can be solved.
 
you are asking about using secure connection on insecure SSL 3.0, this is nonsense.
 
Hi,
I have the same problem.
In my company unsupported, old SSL 3.0 was just implemented.
I don't care if it is old or let say not fully secure but now I can not use THE BAT because it doesn't have backward compatibility. I hope you fill fine with losing customers. Returning to hated OUTLOOK...
 
Quote
Pawel Sokolowski wrote:
I don't care if it is old or let say not fully secure but now I can not use THE BAT because it doesn't have backward compatibility. I hope you fill fine with losing customers. Returning to hated OUTLOOK...

Just came back checking whether there's now a solution to this old problem ... well, obviously still not ... I hate people charging money for selling software and then telling their clients they can trash the software they bought 'cause the developer wants to "protect" them - pretty arrogant IMHO ... consequence: those people have to use another "insecure" software but not TB :( - anyway, they learn to buy software that works :)
Pages: 1