-
All replies
-
Helpful answers
-
Dec 7, 2015 8:30 PM in response to charlieavilajrby computerhead,So I found a simpler solution and it did not require resetting my account.
- open Terminal.app (type terminal in spot light, tiny magnify glass top right)
- rm ~/Library/Preferences/com.apple.mail.plist
(this is optional, this did not work when simply trying it) - defaults write com.apple.mail DisableInlineAttachmentViewing -bool NO
- defaults write com.apple.mail DisableInlineAttachmentViewing -bool YES
- Open mail.app
- Go to Menu Mail -> Preferences
- Under viewing tab, uncheck and check "Load Remote content in message"
Doing the above steps I was able to see the fixes immediately in the mail app.
** I should note that this started happening after an OS upgrade. I suspect some "plist" files have gotten corrupted or someone on the apple side did not do there QC very well. Anyways, good luck to others. Hope this helps!!!
-
Jun 16, 2016 8:22 PM in response to computerheadby Simonron,In my case it was because I was using a proxy. Once I had turned it off ( it had stopped working ) the images came back. This can be done in system prefs - network - advanced - DNS - clear out dead settings - and/or select Proxy and play with that a bit.
-
-
Jun 19, 2016 12:51 AM in response to Simonronby appreciate,when we go in system preferences > network > advanced > proxies : check the box use passive FTP mode ( PASV )
if possible uncheck all proxies , uncheck the box exclude simple host names .
-
Jun 25, 2016 8:57 PM in response to konnektorby eyadmac,for me Little Snitch application was the problem.
I went to the roles and search for mail then remove all deny rule for "mail". then problem solved
-
Jul 9, 2016 4:28 AM in response to eyadmacby Nikos Gianniris,well done mate! i tried the previous suggestions, they didn't work..experience w Apple has so far taught me that the source of many of these sudden errors is soon to be found in 3rd party apps and the way the user has set some preferences and/or rules - opaque OS X updates don't help as things that once worked may break and that makes troubleshooting hard. I also found that there usually is an easier way before resolving to command line..
As u suggested I had a look in my snitch rules (and cleared up a lot redundant and erroneous ones that have accumulated over the years) and now (old and new) posts load perfectly. Cheers!

