Closed
Bug 269432
Opened 20 years ago
Closed 18 years ago
"Allow remote images if the sender is in my ..." should allow selecting more than one address book.
Categories
(Thunderbird :: Preferences, enhancement)
Thunderbird
Preferences
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: mozilla-bugs, Assigned: mscott)
Details
I have two address books (roughly speaking "Personal" and "Work"), so there is no way for me to select a single one for the "Allow remote images if the sender is in my ..." setting.
Comment 1•20 years ago
|
||
Possible workaround: Create an address book called "Newsletters" and add all senders to it that use remote content (usually newsletters).
Comment 2•19 years ago
|
||
Maybe it would be good if Thunderbird automatically created a separate addressbook called "Whitelist" which contains those addresses which I want to allow for images, but don't need in my real addressbook.
Comment 3•19 years ago
|
||
(In reply to comment #2) No. Adding a "whitelist" is merely a *workaround*. This would mean managing ONE person's address in TWO locations (e.g., AB:Friends and AB:Whitelist).
The same goes for "Do not mark messages as spam if sender is in..." - you can only select one address book.
Comment 5•19 years ago
|
||
Reporter (or anyone authorized): Can you please change the "OS" to "All"? (I'm on Windows XP and Windows 2000)
Updated•18 years ago
|
OS: Linux → All
Hardware: PC → All
Comment 6•18 years ago
|
||
The address books could be listed with check-boxes:
Allow remote images if the sender is in my: [ ] Personal Address Book
[ ] Collected Addresses
[ ] Friends
[ ] Family
[ ] Work
[ ] Newsletters| Assignee | ||
Comment 7•18 years ago
|
||
I'm going to mark this as invalid because we are about to get rid of the address book white listing feature all together for blocking remote content. It will now be on a per person basis and the card for that person can be in any of your address books. See Bug 357321 for more details!
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•