#533 ✓resolved
Stefan Piatek

SSL handshake error

Reported by Stefan Piatek | December 13th, 2013 @ 09:32 AM

This email account was working up until about a couple of days ago, maybe with my update to 1.7.1 but not sure. Here's the log file after the error message, the login details are correct and I can access the account using other platforms.

Connection log (2013-12-13 09:29:02 +0000):
Clearing connection to exchange.imperial.ac.uk
Clearing connection to exchange.imperial.ac.uk
Trying to connect to exchange.imperial.ac.uk on port 143
Error: Failed connecting to host (exchange.imperial.ac.uk:143).
“error:0200203D:system library:connect:Connection refused” “error:2007306E:BIO routines:CONN_STATE:nbio connect error” Clearing connection to exchange.imperial.ac.uk
Trying to connect to exchange.imperial.ac.uk on port 993
Successful connection.
Initiating SSL/TLS...
Error: Failed SSL handshake.
“error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol”

Thanks

Stef

Comments and changes to this ticket

  • benny

    benny December 13th, 2013 @ 09:38 AM

    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  
    ---
    
  • benny

    benny December 13th, 2013 @ 01:38 PM

    @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.

  • benny

    benny December 16th, 2013 @ 12:26 PM

    • State changed from “new” to “resolved”

    Since MailMate didn't change over the weekend then I'll also assume it was a server problem :-) Thanks for the update.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Mac OS X email client.

Shared Ticket Bins

People watching this ticket

Pages