GNOME Bugzilla – Bug 562233
mail html images not displayed - no matter what configuration settings are set
Last modified: 2010-03-25 19:38:07 UTC
Please describe the problem: Platform - OS - opensolaris snv-101b - RC2 Html mail containing images do not display. gconf editor shows: load_http_images=1 mail preferences->HTML Messages->Loading Images: neither: Always load images from the internet nor Load images in messages from contacts enable html image display when selected. Did backup of data and settings and removed .evolution directory. Started evolution and restored data and settings - which worked - html images still not diaplayed Steps to reproduce: 1. 2. 3. Actual results: Expected results: Does this happen every time? Other information:
Does Control+I work?
No, Control+I does not work.
I can confirm this one for myself.
I see this also. Some emails will display images, some emails won't, and some emails will display some images but not all. It seems to be consistent in terms of which emails do what - any given email will always exhibit the same behaviour. It also seems to be consistent by sender. I can attach the source for an email that does not display images if that would help.
Note - in my experience, this may have something to do with proxy settings. gconf and evolution have different definitions of the structure of "ignore-hosts" in the %gconf files. gconf schema has it as a list of strings, whereas evolution has it as just a string. Whenever I try to enter a list of hosts manually in evolution, like "localhost, 127.0.0.1, *.domain.com", I get an error like "Expected list, got string" or visa versa. Unlike these other folks, I NEVER get images.
*** Bug 565759 has been marked as a duplicate of this bug. ***
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. (In reply to comment #5) > Note - in my experience, this may have something to do with proxy settings. This is a good catch, I'm going to mention it in the other bug report. *** This bug has been marked as a duplicate of bug 557016 ***