SSL handshake error

oh and I'm on OSX 10.9 with Mailmate 1.7.1

It looks like a server problem. Could you ask your IT department?

I get the following if I try to connect to the server manually without using MailMate:

> openssl s_client -connect exchange.imperial.ac.uk:imaps
CONNECTED(00000003)  
140735247878588:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:766:  
---
no peer certificate available  
---
No client certificate CA names sent  
---
SSL handshake has read 7 bytes and written 322 bytes  
---
New, (NONE), Cipher is (NONE)  
Secure Renegotiation IS NOT supported  
Compression: NONE  
Expansion: NONE  
---

Thanks for the quick response, waiting for them to come back to me. Strangely it seems to work for other accounts on the server.

I also get this error message and it asks me to re-enter the password:
Server response: C2 NO AUTHENTICATE failed
Command attempted "*********"

with the *s looking to be the password

Looks like that was a temporary error with the handshake error, but the most recent authenticate problem is still happening (that started yesterday, which isn't related to today's outing apparently) and they're not sure why this account isn't connecting.

It came back with this regarding the authenticate error

"The error suggests that the client is using an unsupported method for signing on. From previous experience, some clients if set to use auto for signing on can by default uses an supported method."

Any ideas on how to change the method, or testing this?

Hi,
i don't know if this is related, but i keep getting the same error when trying to connect to Gmail accout (and it started from today morning).

"MailMate encountered the following error: “Failed SSL handshake.”.

I use version 3880 of Mailmate.

@Stefan: Well, MailMate has not changed behavior which makes me think that the server has changed behavior. If you open the Activity Viewer (⌥⌘0) and find the connection to the server then we could analyze the connection attempt (which ends with NO AUTHENTICATE) and see if MailMate is doing something wrong.

@Majiec: That's not related. I have no other reports about this (for Gmail). Let me know if it does not stop.

Seems like it's been fixed over the weekend, who know's that the problem with the server was. Thanks!

Stef