User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007 MultiZilla/188.8.131.52b Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007 MultiZilla/184.108.40.206b I would like to be able to prevent spam mails from loading images and scripts. I would like privacy settings such as preventing the loading og images and/or scripts and/or the message itself to be set on a pr. folder basis (via a tabe in the folder properties). I'm using spamassassin and procmail and accessing via IMAP. My spam gets placed in an imap spam folder. I would like the option to prevent images from getting displayed in messages in this folder but allow messages in my inbox to display images and/or run scripts. I also hasve procmail places vira in a folder in which I would like messages to prevented to load even when I click on them (it could write something like 'Messages in this folder are not loaded. To view this message anyway click *here*. To change the settings of this folder click *here*.' in the preview pane and message window. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Confirming. Clarifying summary: was: Tab in folder properties to set privacy options (image and script) now: Set remote script & image loading per folder, not globally
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Tab in folder properties to set privacy options (image and script) → Set remote script & image loading per folder, not globally
xref bug 196964, seeking similar per-folder control over Junk.
*** Bug 246492 has been marked as a duplicate of this bug. ***
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
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.