Closed
Bug 234661
Opened 21 years ago
Closed 21 years ago
Need to integrate JunkMail filters with manual Mail Filtering
Categories
(MailNews Core :: Filters, enhancement)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 202605
People
(Reporter: levik, Assigned: sspitzer)
Details
User-Agent:
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Currently, the two features are almost exclusive to one another. Mail filters
run BEFORE junk filtering, and therefore, messages that are moved on the basis
of manual filters end up not being run through the Bayesian filtering.
Bayesian Junk mail filters should run first on every individual message as it's
downloaded. Then manual filters should run on it. Manual filters should be able
to act upon the results of Bayesian filtering (should be able to filter on the
Junk score of a message - for example, if it's 0.9 and higher, immediately
delete the message from mailbox and server, 0.5-0.9 - mark it as junk, etc).
Manual filters should also have the option of altering/overriding the spam score
in a SpamAssasin style. For example, I should be able to say that anything
coming to a particular email address will get a 0.2 bonus to its spam score.
There should also be filter options to mark the message as an outright
spam/non-spam, which should update ("teach") the Bayesian filters in the same
way as if this action was taken manually. For example, if I know that all the
email that comes to "spam@mydomain.com" is DEFINITELY spam, I should be able to
use this information to automatically train a filter.
The current implementation of Junk Filtering is 90% accurate, but still gives me
the odd false positive, which means I can't reliably allow it to delete junk
from my mailbox - as such it's fairly useless since I am still forced to look
over every message (even those marked as junk). With the ability to use filters
on the results of the junk classification, I would gain a valuable tool to make
Bayesian filtering more effective.
Reproducible: Always
Steps to Reproduce:
Comment 1•21 years ago
|
||
*** This bug has been marked as a duplicate of 202605 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•