Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Mavericks broke IMAP in Mail, throwing bogus SSL error.

Suddenly Mail claimed it couldn't connect to my regular E-mail account at my ISP (not Gmail), because of an SSL error. But my 10.8.5 system with the exact same credentials, account configuration, and router connects no problem.


The error says, "The identity of “mail.myISP.com” cannot be verified. An SSL error has occurred and a secure connection to the server cannot be made."


The Mail "Connection Doctor" test log doesn't show any errors, but the account is still flagged as inaccessible after it's "tested."


Anybody else see this? Mail is useless as it stands.

Posted on Oct 24, 2013 7:36 PM

Reply
34 replies

Oct 26, 2013 10:52 AM in response to Miska_FL

Well this is interesting. Until now I had no problems with the SMTP servers - only IMAP (incoming) was not working.


With your method I came accross some strange behaviour


IMAP is tested and passes the test - greatest success so far! But when it comes to SMTP it just says "an unknown error occured" (translated to english by myself - system runs on german)


Mail does then not respond anymore and I get to see the famous beachball for minutes. Finally decided to kill Mail via activity monitor.

Oct 26, 2013 11:06 AM in response to Miska_FL

I created a new user and tested your way again. It seems as Mail does not check IMAP settings in the first place but does just pass me over to the SMTP settings. After entering them - I get the Error message. But at least not a beachball anymore.


https://www.dropbox.com/s/tnlgz8dum6t3i56/Bildschirmfoto%202013-10-26%20um%2019. 59.58.png


If I may ask: on what ports are your IMAP accounts running? 143? 993? 110?

Oct 29, 2013 2:46 AM in response to Taszyn

Hi Taszyn!


I have exactly the same problem with IMAP, on the same server (nazwa.pl). I see the same strange logs:


READ Oct 29 10:39:08.314 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:ppg.nazwa.pl -- port:993 -- socket:0x6080004cdc80 -- thread:0x61800087fc00

.860dLOGIN BAD Error in IMAP command received by server.


Did you manage to solve the issue by now?


Wojtek

PS. The strange thing is that while IMAP does not wotk on my MacBook, it perfectly runs at home on my iMac whih is also upgraded to Maverics. :-o

Oct 30, 2013 1:49 PM in response to Stokestack

Same problem. Was working fine two days ago. Now all mail accounts (gmail and iCloud) are offline because of 993.


The same accounts on the same network (actually on the same laptop) work in Snow Leopard.

The same accounts work on iPad/iPhone (iOS 7.x)

The same accounts work in Postbox (http://www.postbox-inc.com) running under Maverick.


Cheers,

Andrei

Nov 18, 2013 3:41 PM in response to Stokestack

I have the same issue.

Unfortunately, the mail update hasn’t solved my problem. Im on a Macbook Air. My gmail powered accounts are all running OK but my IMAP account hosted elsewhere refuses to send. I keep getting an error:

Mail was unable to connect to server “mail.xxxxx.me” using SSL on the default ports. Verify that this server supports SSL and that your account settings are correct.

I have tried all settings with SSL on and off. With default ports changed to custom port. Authentication with password and without. get a different error each time I change settings eg

The server “mail.xxxxx.me” refused to allow a connection on the default ports.


The same account is working perfectly on my iMac running 10.8. The issue only started when I upgraded the Air to Mavericks.


NB: I have looked at Keychain settings for iCloud and neither Mail nor Keychain have been activated.

Jan 12, 2014 3:53 AM in response to r.geromin

I find (thanks to my friend Luca) a workaround that solve the problem of IMAP connection in Mail.app.

My IMAP is defined with an IP adress (number). Mavericks (I think) want a name for your IMAP.

So I did these steps:

  1. login ad admin
  2. open terminal
  3. cd /etc
  4. sudo nano hosts
  5. ad a line on host file (I added it on the top): YOUR_IP_ADRESS NAME_OF_YOUR_IP_ADRESS (for example: 192.168.1.1 myadress.com
  6. Save it ad exit (^o, return and ^x).
  7. Open Mail.app and change YOUR_IP_ADRESS with NAME_OF_YOUR_IP_ADRESS.
  8. save, close Mail and open Mail
  9. Mail will work!

I tried this workaround on my iMac and MB Air and it works fine!

Thanks to Luca!


Here the how-to in italian.

Feb 28, 2014 8:50 AM in response to Stokestack

Exact same problem here, after installing latest Mavericks update to supposedly fix the SSL vulnerability.. both of my IMAP mailboxes using SSL on port 993 have completely stopped working. If I change them to use non-SSL in the settings on port 143 they work again fine... but this is probably even more insecure than using SSL with the vulnerability in the code. Ridiculous!

Mar 2, 2014 8:00 AM in response to Taszyn

Some debug info from connection doctor. Basically error message remains the same as before:


READ Mar 02 16:55:21.977 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:balrog.nazwa.pl -- port:993 -- socket:0x6100002c2140 -- thread:0x61800086a1c0

.75bLOGIN BAD Error in IMAP command received by server.


It suggests that there is something wrong with authentication, but switching IMAP to non-SSL standard 143 port solves the problem and Mail.app is able to authenticate properly. So it is NOT problem with authentication, but probably some error in SSL/IMAP implementation 😟. Please fix it finally!

Mavericks broke IMAP in Mail, throwing bogus SSL error.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.