GNOME Bugzilla – Bug 236994
Add option to load remote content for specified site or sender
Last modified: 2015-08-11 15:38:31 UTC
Please fill in this template when reporting a bug, unless you know what you are doing. Description of Problem: Some newsletters/mailing lists send each issue/message from a unique e-mail address. For example, the "Daily Dilbert" newsletter from www.comics.com sends each days message from an e-mail address like the following: dailycomic#2.33852.31393035303533.1@comicsmail.unitedmedia.com where the numbers following the "#" character are different for each message. This creates a problem when using the "Mail Preferences-->HTML Mail-->Loading Images-->Load images if sender is in address book" setting since there is no single e-mail address to put in the address book. (The easy work-around for this is to add the sender to the address book for each message received.) It would be nice to have a way to specifiy patterns based on sender or other criteria norally used in filters to determine if images should be loaded. For example, I would like to be able to specify that images load in all messages from the comicsmail.unitedmedia.com domain. Steps to reproduce the problem: N/A Actual Results: N/A Expected Results: N/A How often does this happen? N/A Additional Information: N/A
Bumping version to a stable release.
*** Bug 740246 has been marked as a duplicate of this bug. ***
I made this similar to Mozilla's remote content handling [1]. The option in a preview panel is shown when there is skipped at least one remote content download. The list of allowed sites and senders is available in Edit->Preferences->Mail Preferences->HTML Messages tab, where I also renamed the section about loading images to more general Remote Content loading, which is more appropriate now, because this can be also CSS files and other similar HTML email content. Created commit 3c4bfdd in evo master (3.17.1+) [1] https://support.mozilla.org/en-US/kb/remote-content-in-messages
*** Bug 721793 has been marked as a duplicate of this bug. ***
*** Bug 753479 has been marked as a duplicate of this bug. ***