Open Bug 89091 Opened 23 years ago Updated 2 years ago

Implement "quick filters" (easy way to modify existing message filters based on current [spam] message)

Categories

(MailNews Core :: Filters, enhancement)

enhancement

Tracking

(Not tracked)

People

(Reporter: dr, Unassigned)

References

Details

Okay, "quick filters" might be a stupid name, but here's what I'm envisioning:

I get a lot of spam. A *lot* of spam. I have a "Spam" filter which moves
anything likely to be spam directly to the Trash folder. Every day I get spam
from a several new addresses. The spam is easily filtered: it's either from a
domain I'd never expect real email from, or to an address which is obviously
wrong (mail to <anything>.netscape.com, for example, or xwing.aoltw.net). The
pattern I go through to add this to my spam filter is pretty much the same each
time, and is a little bit tedious.

What it would be nice to be able to do, is to be able to bring up a dialog (or
simple menu group) from the mail address context menu, which would encapsulate
this pattern of "If I see this email address, or something looking like this
email address, use this filter on it." Something like that.

I'm not sure exactly how I'd want this feature to behave if I were to design it.
The interaction between this and the do-it-yourself filters we have now *should*
be simple, but has the potential to get complicated. I'd certainly like to see
it in some form or other, though -- I have 20 criteria in my spam filter right
now, after about 10 days running with a new profile :)
We have a few bugs out there relating to this kind of thing, including (but not
limited to) bug 11036, bug 71413, bug 65761.
Marking this a duplicate of 11036

*** This bug has been marked as a duplicate of 11036 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Dear God. Bug 11036 will never see the light of day. It's assigned to
nobody@mozilla.org and seems to be the dumping grounds for the true AI freaks
among the mozealots. I fear for the viability of our product if we deal with all
useful features this way.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Reassigning to Steve Morse, who generally seems to be an implementor of useful
features, FWIW.
Assignee: naving → morse
Status: REOPENED → NEW
Reassigning.
Assignee: morse → nobody
reassign to self. 
Assignee: nobody → naving
*** Bug 91139 has been marked as a duplicate of this bug. ***
bug 71413 seems to propose the most elegant solution for the spam problem. The
solution there works similar to other "blocking" functionality already existing.
I suggest making this bug a dup of it. 
Is this bug somehow dependent on bug 11036? It seems to me they are very closely
related. 
isn't this the same as bug 10097 (or vice versa) ?
mass re-assign.
Assignee: naving → sspitzer
Product: MailNews → Core
sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
Filter on "Nobody_NScomTLD_20080620"
QA Contact: laurel → filters
Product: Core → MailNews Core
Summary: [rfe] Implement "quick filters" → Implement "quick filters"
Aureliano, what do you think?

(In reply to comment #8)
> Is this bug somehow dependent on bug 11036? It seems to me they are very
> closely
> related. 

(In reply to comment #9)
> isn't this the same as bug 10097 (or vice versa) ?
(In reply to comment #13)
> Aureliano, what do you think?
> 
> (In reply to comment #8)
> > Is this bug somehow dependent on bug 11036? It seems to me they are very
> > closely
> > related. 
> 
> (In reply to comment #9)
> > isn't this the same as bug 10097 (or vice versa) ?

For me this is a dupe of bug #11036 (as in comment #1)
Also bug #10097 for me can be closed as dupe of this bug: #10097 is a sub-set of this bug (reporter ask for a feature that "quick filter" by example where the example is the sender I suppose.
Summary: Implement "quick filters" → Implement "quick filters" (easy way to modify existing message filters based on current [spam] message)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.