Mail missing its viewer window
Started with a hard drive failure. Replaced and restored data from TimeMachine. This also represented an upgrade from Yosemite to High Sierra. Now launching Mail. No windows appear. All menu items are grey except for Preference and Accounts under the Mail menu. Able to open Mail Preferences from menu bar. Can see that accounts (3) are online. Nothing Mail related showing in Console. I suppose it's updating the Mail database, but have left it running for hours, and still no sign of a window (as well as no progress bar indicating the update). Have updated to the very latest High Sierra.
Mail account working find on iPad and iPhone, so it's not a server or account issue.
I've seen this type of behaviour from Mail on a number of occasions and it looks to me like it believes it has a dialogue sub-window open "somewhere" but which you can't find. Usually force quitting and reopening has solved this but a few other options you could try:
1) Quit then hold down the Shift key when opening Mail again - this does similar to Safari in that it tells the app to only open the default window (may, or may not, have affect on that hidden dialogue)
2) Temporarily alter the screen resolution on your Mac, or change monitor - this may prompt the app to "redraw" all the windows back into a visible area.
3) If I remember rightly one of the plist files contains info about current window positions so deleting the relevant plist file might also revert it.
Edit: 4) Also try having your Mac disconnected from any internet connection so that Mail isn't tempted to check account status/connection.
Please confirm if your issue is as described in this Apple Discussions Forum post, "Mail El Capitan menus greyed out after Migration Assistant", I realize that the issue is similar, with the exception of the OS, but read through it and consider applying the steps in Link Davis' response. Link Davis is a very learned and reputable participant on Apple's forums.
If you want to try a less provocative method, restart the Mac while holding the shift key, login and then restart as normal. See if that resolves the issue.
Then again, something could be corrupt in mail and the files that make up or support your messages.
- Quit Mail. Force quit if necessary.
- Back up all data before proceeding.
- In the Finder menu, select Go > Go to Folder and paste this in, ~/Library/Mail/V2/MailData
A folder window will open and you will find some files with names as follows:
- Move those files to the Desktop. Don't remove the folder beginning with V.
- Relaunch Mail. You should be prompted to re-import messages. You may get a warning that the Mail index is damaged and that Mail has to quit. Click OK. The process of re-importing my take only a few minutes or for very large mailboxes it can take hours.
If it looks like it will take hours, you can reduce that wait-time by temporarily adding your home folder to the Privacy list in the Spotlight preference pane. When mail completes the import, remove the exception from Spotlight preferences. If you don't search will be mostly unavailable and you will certainly not be able to search within the Mail.app
- If Mail now works as expected, you can delete the files you moved to the Desktop.
If issues persist post your results.
Silly question perhaps, if the viewer window is not visible did you try command-0 (that's a zero) to bring it up.
Turned out to be an unsolvable problem in the time my friend allowed me to work on it. Have moved onto Spark.
On a different Mac, I configured his three accounts and they work perfectly, but took over half an hour to download the 30,000+ messages from the server.
So we know it's not the account itself then. Trying a new user account would only identify if the OS itself is to blame which I doubt. I think there may be some mailbox corruption. The problem is identifying it, the more mailboxes the more probing needed.
The corrupt mailboxes appear to be stalling Mail during the conversion process, you can try to identify the mailboxes that Mail is choking on. To do this quit Mail, move suspect mailboxes out of ~/Library/Mail/ (to the Desktop for example), and trash any Envelope Index files you see in ~/Library/Mail/. This should cause Mail to recreate the index and import the mailboxes that remained in ~/Library/Mail/.
If this works
You can then manually import the problematic mailboxes as 'Other'.
~/ is notation for your home folder.
Start from scratch followed by manually importing mailboxes as you see fit.
Alternatively, set up Mail from scratch and manually import after the download. You didn't mention any missing emails that might have gone as a result of trying what is essentially a from scratch exercise but then again you might not have checked for omissions. Anyway, the steps below will at least allow you to use Mail again. You can then resolve importing any old mail messages that might be missing because they were 'on my Mac' after the fact as you see fit.
- Quit Mail.
- In the Finder, go to ~/Library/. Move (not copy) the entire Mail folder to the Desktop and back it up incase (please).
- Locate com.apple.mail.plist inside the ~/Library/Preferences/ folder and move it to the Desktop.
- Open Mail and set it up again from scratch. If Mail asks for an opportunity to import existing mailboxes, don’t.
- Patiently wait for the sync process to occur.
- From the Mail menu go to File > Import Mailboxes. Follow the onscreen instructions to begin importing mail from the Mail folder that’s on the Desktop. Choose to import as 'Mail for Mac OS X' and locate the .mbox folders as the import targets.
Remember ALL the old mailboxes are on the desktop (done in step 2) but leave them there until the import complete and then consider importing them in stages as per step 6. I believe one or more of the mailboxes on the desktop are corrupt or even a single message is glitched enough to halt the import in a most peculiar way.
I know that this appears rather intrusive, but the fact that import simply stalls or worse stops entirely tells me that there must be a glitch somewhere in the ~/Library/Mail/ that you may be able to isolate in stages as per step 6. I recommend you follow step 6 in stages, don't try to import everything back at once or you might not know when you bump into the corrupt items. If you import using the rule of halves it will help you to more quickly isolate in the problematic files.
The rule of halves involves considers only half of the entire material at one time. In this case it's on the desktop (the old mail folder) and importing half at one time is how you should proceed. If that half imports without issue then you continue importing the remaining half and you continue to follow this cascading approach until you encounter an unexpected result which is a tell-tale sign of what you should now consider as the potentially affected batch of file representing the cause of the issue. At that point of discovery, it is prudent to apply this rule of halves on this suspect target batch of files. You will eventually find the file(s) sourcing the original issue.
Some considerations before importing the contents of the old mail messages on the desktop
I would not do this right away. The first thing to analyze is if it appears all your message are back. If the answer is true then don't immediately trash the old message from the desktop. Leave them there until you are satisfied that nothing is missing. Only then should you import because importing may actually create duplication and with that let me introduce you to Jolly Roger. When you go there click on software and then choose to download Remove Duplicate Messages-Mail 1.3.6.zip. After unzipped you will find a readme and an AppleScript.
Below is the splash screen as it displayed when I ran the AppleScript form the Finder but the read me has a more interesting installation process outline. I tried the AppleScript, it is nothing short of genius but slow going. It also provides verbosity in the terminal window, displaying where it is at and is interactive, asking you for what you want to do, the latter you can define on start of the app. This is an extremely well designed AppleScript and built to prevent catastrophic loss of messages, that being said backup first.
I sincerely hope this helps otherwise you are welcome to chime back with indication of where things went off course and a description of that 'brick wall'
It is there. The name starts with com.apple.mail.something…
The containers folder is there for sandboxing.
A few messages back you mentioned the following:
I have removed the contents of ~/Library/Mail a couple times (no help),
Can you provide more on the no help part? After moving the Mail folder to the desktop what happened after launching Mail?
Concerning the logs and core data. The framework, Coredata, is an object graph manager. An object graph is a collection of objects that are connected to one another. Some of the objects Coredata manages can persist on disk. As a non-software developer with limited knowledge on Coredata it is hard to explain the log, at least for me but because Coredata manages object graphs for multiple apps and users I would venture to say that perhaps Contacts.app data can't be read by Mail but this is a very wild guess on my part.
I can't explain the log files at this point but for the sake of understanding the main issue…
- Please remove all those items we spoke of before you reported the log. This include the ~/Library/Mail and the plist files. In addition, please delete all files inside ~/Library/Caches folder. Perform these while Mail is not open.
- Restart or logout of your account and log back in to your account.
- After doing so, ensure that the Contacts.app is working as expected. Quit Contacts.
- Open System Preferences>Internet Accounts.
- Select your accounts one by one and turn off those that have the Mail option turned on.
- Launch Mail.
- If necessary start turning on accounts one by one, not all at once from the Mail>Accounts menu.