Q: Mail not working after update OS X 10.10.4 and IOS 8.4

What worked for you? There are a lot of posts to this thread!

bob

Still not working after following this thread.

1. Reinstalled 10.10.4 [failed]

2. Checked Automatically detect and maintain settings [failed]

Please let us know what the next steps are because this is causing us serious productivity issues on our work.

A SHORT-TERM SOLUTION.   Press and HOLD shift while LAUNCHING the MAIL application and HOLD IT until Mail atarts up.  Worked for me...

A SHORT-TERM SOLUTION.   Press and HOLD shift while LAUNCHING the MAIL application and HOLD IT until Mail atarts up.  Worked for me...

Yup, The shift thing doesn't work for me. My ISP has said they are aware of apples changes and have given me new settings I'll try them and let you know how I get on

OK, what I did (not mentioned in this thread so far) was to delete the saved state file. I saw this somewhere else, tried it and it worked for me. The reason I wrote a script is that I have to do it *every* time I run Mail or it will hang again.

To do this, I created a bash script mymail.sh and run it instead of Mail:

#!/bin/bash

cd ~/Library/Containers/com.apple.mail/Data/Library/Saved\ Application\ State

rm -R -f com.apple.mail.savedState

open /Applications/Mail.app

and that worked for me.

Just this morning, I forgot and opened Mail the normal way and of course it hung. After a force quit, I tried again and it still hung. The problem was multiple Mail tasks still running after the main Mail program was force quit. You can view them from the command line:

ps auxw | egrep -i mail

fredlaxton      66117   0.0  0.1  2543040  13784   ??  S     6:50AM   0:00.11 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker -s mdworker-mail -c MDSImporterWorker -m com.apple.mdworker.mail

fredlaxton      66116   0.0  0.1  2552540  14000   ??  S     6:50AM   0:00.12 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker -s mdworker-mail -c MDSImporterWorker -m com.apple.mdworker.mail

fredlaxton      66115   0.0  0.1  2543040  13856   ??  S     6:50AM   0:00.12 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker -s mdworker-mail -c MDSImporterWorker -m com.apple.mdworker.mail

fredlaxton      66114   0.0  0.1  2543040  14128   ??  S     6:50AM   0:00.14 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker -s mdworker-mail -c MDSImporterWorker -m com.apple.mdworker.mail

fredlaxton       1692   0.0  0.1  2584360  19524   ??  S     4:33PM   0:00.32 /System/Library/PrivateFrameworks/MailService.framework/Versions/A/XPCServices/ com.apple.MailServiceAgent.xpc/Contents/MacOS/com.apple.MailServiceAgent

so I killed them manually from the command line by specifying the task number (the second column):

sudo kill 66117 66116 66115 66114 1692

and then verified by running:

ps auxw | egrep -i mail

again, which only showed itself (the egrep command).

Now when I run my bash script, Mail starts and acts normally, including sending and receiving email...

I found that i couldn't send emails after 10.10.4 update, had to turn off SSL & then all fine, may also have to set Authentication to ' None '  5 Macs & 2 iPhones all the same issue & the same fix worked !  

The shift key solution does not work for me either. Seems to work for when the mail app crashes or hangs up.  I can't send or receive, but the Mail app opens fine, shows old mail, lets me open archived mailboxes etc.

The connection doctor in the App is showing red on connecting to both the incoming and outgoing servers of my ISP.

Checking or unchecking Automatically detect and maintain account settings has not helped.  I created another user account and configured the mail app manually.  Connection doctor shows red here also.

Downloaded Thunderbird and configured it.   This did work. 

Problem seem related to the update.  It is Version 8.2 (2102) correct?

Jim

From my ISP:

"The most recent Apple update has adjusted a few of the outgoing SMTP mail settings which is required to send mail."

They then set out my settings - these may be different from yours, so check with your ISP - but these worked.

I deleted the old SMTP server, then as follows:

Outgoing server: [as your server]

Outgoing server port: 587

SSL: Off

Allow insecure authentication: on

Authentication: Password

Username: [as per your settings]

Password: [as per your settings]

I updated my macbook pro the other day to 10.10.4 and my email crashes almost immediately upon opening the app.  I click on any email and it crashes.  I try to switch to another account and it crashes.  Very frustrating.  I tried going into mail preferences and accounts to try someone else's advice and it crashes as well.

I have tried all sorts of solutions everyone have  posted here and none of them have worked for me. The emails won't  leave my Outbox! I can't send emails but I do receive emails. Geez! I hope Apple do something otherwise I'll be forced to change to outlook (which I hate!).

I know you said you've tried everything but just want to confirm that you have turned off SSL & also switched authentication to ' None ' for outgoing mail server ?

It's just that we have 5 Macs here & that procedure worked for all of them. Obviously yours may be different !

i had to tweak my servers for other reasons and i think i have found the underlying cause. the new ios code (and probably macos as well) has activated a new feature that doesn't like talking with systems doing diffie hellman (dh) ciphers with less that 768 bits for the random generator. i updated my servers to 1024 to deal with a new openssl release and suddenly the iphone was happy again.

i hope there are some other folks on this issue that runs servers and can see if this does fix the issue.

i have confirmed this with another server and set of apple devices.

this really makes sense because i imagine that apple is using the new openssl library that has this restriction, but there are still a lot of servers running older sendmail that defaults to 512 bits. anyone having this problem, contact their isp and tell them to google about for sendmail, dhparam, 512 and to update their servers.

Hi Michael, how do you edit those details? (see image below) How come I cannot edit mine

That was exactly this issue I was having with a sendmail server running on CentOS. 

https://www.safaribooksonline.com/library/view/sendmail-4th-edition/978059651029 9/ch24s09s36.html

Had the fix for me.