9
edits
Changes
→Show remote content in messages sent TO a specific recipient address: new section
Such layout is really helpful if one uses wide screen - all necessary panels may be displayed next to each other and all necessary information from inbox panel are displayed.
== Show remote content in messages sent TO a specific recipient address ==
There is no way for "Show remote content" filter to always show remote content in messages SENT TO a specific RECIPIENT.
When using a forwarding address from Blur (formerly MaskMe) individual messages from a specific sender may arrive from a forwarding SENDER address unique to that specific message.
Only the RECIPENT'S forwarding address always remains the same, e.g. whatever@opayq.com
Problem:
I and many others are using Abine's Blur (formerly MaskMe), which generates temporary forwarding email addresses on the fly, to help block SPAM, if & when it starts to arrive.
When I use one of these addresses, I often see "To protect your privacy, Thunderbird has blocked remote content in this message."
At present, the only filtering options offered by T-bird are:
- Show remote content in this message (only)
- Edit remote content options...
- Allow remote content for [sender])
- Allow remote content for <URI>
However, none of these would work for showing any future content sent to my Blur address, because
- the address from which the message is sent is unique for each message
- the remote content is not always from the same location
- I don't want to override T-bird's protection from unknown remote content altogether, and
- I don't want to have to elect to "Show remote content in this message" every time.
Because the messages are always sent to the same address, which is unique to the actual sender, I would like to be able to enable remote content for all messages sent TO a particular address, just as when I create a Message Filter in T-bird. In effect, this would function the same as whitelisting a particular sender, because each address is only given to one sender, unless & until they share it, of course. As soon as that happens, I block the address.
Possible suggested solution :
This change to the Options menu within each message would be quite useful:
- Show remote content in this message (only)
- Edit remote content options...
- Allow remote content for [sender])
- Allow remote content for <URI>
NEW - Allow remote content sent to [Recipient address]
------------------------------------------------------
However-----------------------------------------------
Because "Allow remote content sent to [Recipient address]" might be accidentally used by someone to effectively allow ALL remote content in nearly ALL of the emails they receive, it might be better to allow wildcards (* &/or ??? etc.) when manually editing the list of exceptions from Tools:Options:Privacy:Mail Content.
This would enable more advanced users to create exceptions for *@opayq.com or FWD*@opayq.com or any other domain, as well as *.amazonaws.com, *.cloudfront.com/*.cloudfront.net, or *.akamai.com/*.akamai.net
