Closed Bug 230463 Opened 21 years ago Closed 14 years ago

remote images from allowed servers are not displayed

Categories

(SeaMonkey :: MailNews: Message Display, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: mg8, Unassigned)

References

(Blocks 1 open bug)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20040102
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20040102

I checked "Do not load remote images in Mail and Newsgroup messages" but want to
have them displayed if they come from certain servers. I added these servers to
the "allow" list under "Manage Image Permissions" but this does not seem to have
any impact on remote images in Mail and Newsgroup.

Reproducible: Always

Steps to Reproduce:
*** Bug 232785 has been marked as a duplicate of this bug. ***
Confirming...
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: MacOS X → All
Hardware: Macintosh → All
*** Bug 241208 has been marked as a duplicate of this bug. ***
I remember seeing some screenshots of a new version of Outlook Express due to be
released in Windows XP Service Pack 2 - they didn't display external images in
mail by default, but it had one of those little bars above the preview window
with a button to load images for this email only.  Maybe this kind of feature
could be integrated, and released before XP SP2 :)
(In reply to comment #4)
> I remember seeing some screenshots of a new version of Outlook Express due to be
> released in Windows XP Service Pack 2 - they didn't display external images in
> mail by default, but it had one of those little bars above the preview window
> with a button to load images for this email only. 
TB now has this, see Bug 216133. Similiar bug for Seamonkey is Bug 172184.
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Blocks: 442526
Assignee: mail → nobody
QA Contact: esther → message-display
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.