Before updating to 10.10.4 on my macbook pro, mail would not open correctly around 1 in 5 times. After the latest update I connot open mail without it crashing at all. I cannot access my mail at all. Any ideas on how to fix this issue?
MacBook Pro (Retina, 13-inch, Mid 2014), OS X Yosemite (10.10.4)
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
Step 1
For this step, the title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Enter the name of the crashed application or process. For example, if Safari crashed, you would enter "Safari" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
In the Console window, select
DIAGNOSTIC AND USAGE INFORMATION ▹ User Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.
When you post the log extract or the crash report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.
I agree walter1896. See below post, sorry walter if you deleted this yourself.
I just rebuilt my macbook to work with Yosemite by doing clean erase an install and rebuilding new accounts and reinstalling apps. Mail was fine 10.10.14 broke it on several levels. It is not a case of "back up your data" or "look at the logs" anymore than the screensaver reverting to "National Geographic" was a call to do the same. 10.10.4 finally fixed that screensaver issueI have noticed! We will just have to wait till Apple fixes what they have done to mail instead of toggling checkboxes in "Advanced Preferences" on and off as on "Apple Insider" or following the same above blah blah blah that I see on hundreds of different posts. Gee could it just be something Apple did that has no fix until they fix it themselves? I logged in to make this first ever comment because that above "Please don't indiscriminately dump thousands of lines from the log into this discussion." is driving me nuts everytime I go to look for a solution to something that turns out to be something that is unsolvable till apple fixes it themselves anyway (and breaks other things in the process)
10.10.4 broke my mail
