User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1 This is related to bug 179568, but is a bit broader. Some e-mails are not spam, but have spam portions to them. A notorious example is Yahoo Groups. Every time you receive a mail from them, the top of the message is an advertisement, an HTML image. You used to be able to opt for Plain Text only, but that option has since been removed. Reproducible: Always Steps to Reproduce: 1. Sign up for a group at groups.yahoo.com 2. Have the group mail be sent to an account set up in Thunderbird 3. Receive a message Actual Results: The top spam portion of the mail loads Expected Results: The graphics should not load, with an option to load the graphics if you choose This is related to 179568. If I had my way, I would design the feature as follows: Put an option in Display downloading remote images. Text would read "When an HTML message has remote images," [dropdown box: "always display the images, "let me choose to display the images", "never display the images"] Behaviors for options 1 and 3 are patently obvious. Behavior for option 2 should give the user an unobtrustive way to download images. Best implementation I've seen is in Office Outlook 2003. At the top of the message, it states "Click here to download pictures. To help protect your privacy, Outlook prevented automatic download of some pictures in this message." Throwing a dialog asking to download the images would be a bad user experience.
Try Tools -> Options -> Advanced -> Privacy -> Block Loading of Remote Images in Mail Messages.
Sure, that works. But what's the mechanism to show the images? Do I always have to go to Options? The Outlook method still seems most reasonable to me.
So you're thinking of maybe a toggle that will switch between viewing/blocking remote images? This has been brought up in #216133. I suggest that we combine the two under one bug #.
Yep, sounds like the exact same feature request. I would have no problems with combining them.
Changing for a more descriptive title.
the other bug is already assigned to scott, so I'm marking this one as dupe *** This bug has been marked as a duplicate of 216133 ***