Closed Bug 180087 Opened 22 years ago Closed 18 years ago

Junk Mail Controls from Menu can be moved in Mail Account Settings

Categories

(SeaMonkey :: MailNews: Message Display, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nicubunu, Assigned: mnyromyr)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a) Gecko/20021113 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a) Gecko/20021113 The new introduced Junk Mail Controls feature is activated from menu->Tools->Junk Mail Controls... Here is launched the 'Junk Mail Controls' window, where you can set up he junk filter for every account. In my opinion, the best place for this window is in the Edit->Mail & Newsgroups Account Settings, like a leaf for every account (similar with Server Setings, copies & Folders) Reproducible: Always Steps to Reproduce:
QA Contact: olgam → laurel
Severity: trivial → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** Bug 208228 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
Assignee: sspitzer → mail
David, Scott, any thoughts?
iirc, Scott had worked on something like this but didn't finish it in time for 1.5
I've got some work for this feature going on in Bug 257990. We'll need to do some work to make it work with seamonkey too but it shouldn't be that hard if someone wants to add the extra pieces for the suite.
I'm pretty close to being done with the work in 257990 to make this happen. I could use a volunteer to make my patch work for the seamonkey suite. That would involve: 1) adding the global junk settings UI to the seamonkey pref pane by adding the elements I added to privacy.xul and privacy.js in th epatch in 257990.
Depends on: 257990
oh and I forgot 2) update junkLog.xul and junkLog.js
Status: NEW → ASSIGNED
Assignee: mail → mnyromyr
Status: ASSIGNED → NEW
This has been fixed by bug 257990 and bug 335846.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.