If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Add ability to bypass Bayesian junk filter using standard filters.

RESOLVED EXPIRED

Status

MailNews Core
Filters
--
enhancement
RESOLVED EXPIRED
14 years ago
9 years ago

People

(Reporter: Bill Nyden, Assigned: (not reading, please use seth@sspitzer.org instead))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113

Bayesian learning system results in large numbers of messages being incorrectly
identified as spam. A filter capability should be added to tell the Junk filter
not to evaluate a message based on Subject, Body or Address criteria.
N.B.: This is similar to, but not the same as Bug #181631, and has, to my mind,
a higher priority, since I have been missing important incoming messages that
have evidently been filed in the Junk folder (it is difficult to scan 300+ spam
messages daily).

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

14 years ago
If you're already accepting the use of filters to achieve what you want, then 
you should be aware of bug 202605 and its blockers (which includes bug 181631).
Since all those bugs pretty much require the change requested by bug 223591 to 
be implemented first, the change requested by 181631 would then do what you 
want.

Also, see bug 189970 and bug 198961.

At any rate, this is an enhancement request.
Severity: normal → enhancement

Comment 2

14 years ago
See also bug 202605

Updated

13 years ago
Depends on: 200788
Product: MailNews → Core

Comment 3

13 years ago
(In reply to comment #2)
> See also bug 202605

You should be able to create a filter with the action "Mark Junk Status" "Not
Junk". With my patch in bug #223591, explicitly marked messages will be ignored
by  the junk classifier.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.