Mac Mail - Message Body Not Displayed

Many here believe the best settings for Trusteer and similar disruptive and useless Anti-Virus software is in the Trash, never to be re-Installed.

Your Mac is already well-protected against random, invisible attacks. You need to stay sharp about the trojan horses that require your complicity to get Installed.

http://www.apple.com/osx/what-is/security/

.

..... sorry, I should have said "unless it's hidden".

Thank you worked a treat after I updated to OSX Sierra

Thank you Linc, worked a treat after updating to MacOS Sierra

Hate to butt in here, but why moving the envelope files in mail do the trick

I would have thought moving .mbox files out would work. If IMAP, these will be re-created.

Since u are displaying messages fine on iPhone and using icould i assume it's IMAP....

I have this issue as of today with my iPhone with ios 10.0.2. Message subject downloads but when you open it the message body is blank.

Thanks

Tommy

Problem solved with the removal of Trusteer!!! Thanks!!

Good start but for Sierra you have to alter it a bit. Just go to ~/Library/Mail and click on V4 and then MailData. After that, the instructions worked like a charm for me.

The same thing has happened on my iMac several times. Each time I have to turn off the iMac completely and turn it on again. Some times that works sometimes not. It is becoming a real bore. Thinking of going back to a Windows computer as this is not the only problem with my Apple Mac and iPad. Think Apple is spening too much time on their other products and neglecting pioneers like me who was an early switcher from Windows and a great Apple advocate. No more.

Try rebuilding the mailbox.

Rebuild mailbox

If that doesn't work, try re-indexing the mailboxes. This can take awhile if you have a lot of mail.

Reindex messages For El Capitan, try looking in V3. Sierra use V4

Reindex messages (2) See post by Linc Davis

Since this arose (after upgrading to OSX 10.12.2 a few days ago) I too have tried everything advised here, including the rebuilding, reindexing, PRAM zap, and changing the settings in Trusteer - to no avail.

From a different forum, I tried starting in "safe mode" (gotta love that screen flickering!) which did solve the problem... until about 2 minutes after the next normal reboot. That implies that the issue is another process interfering with Mail.

By disabling Trusteer entirely (clicking "Stop Rapport" and going through the convoluted authorisation process), I got the problem to go away. At least in my case, the issue is having Trusteer running when Mail is launched.

In reporting this to Rapport's makers, an outfit called IBM, I noticed that Rapport updates itself in the background by default, which may explain some other users' experience of significant performance changes occurring despite their having made no conscious updates. I'd like to suggest to Apple that any time an installed application makes an update, the system could pop up a message to confirm that this has occurred, and offer a simple route to reverse the update.

Meanwhile, hooray! I can see my email. Including the latest invoice from Apple. Hooray!

The compliments of the season to you all...

Apple doesn’t routinely monitor the discussions. These are mostly user to user discussions.

Send Apple feedback. They won't answer, but at least will know there is a problem or a suggestion for change. If enough people send feedback, it may get the problem/suggested change solved sooner.

Feedback

I tried rebuilding the mailboxes, manually and automatically and restarting but after uninstalling Trusteer this is what worked for me so far, thanks.

Grant, the article you're referencing is not helpful. It suggests to click the "See more" text to see the full conversation, but the issue discussed here is that there is ZERO text displayed in the body of the emails, period. There's no "See more" or less. There is nothing. And I followed Linc's suggested strategy but it did not help.

This is super annoying because Mail is work and it's gotta be done 😟

I'm with you on this. Unfortunately.