Closed Bug 206339 Opened 22 years ago Closed 18 years ago

improve PR_LOGGING for junk mail filter, so we can evaluate problems

Categories

(MailNews Core :: Backend, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
mozilla1.9beta3

People

(Reporter: sspitzer, Assigned: rkent)

References

Details

Attachments

(2 files)

add PR_LOG for junk mail filter, so we can evaluate problems there are a couple bugs that it would really help to have some verbose pr logging of the junk mail filter in order to track down issues.
adding two bugs which this would really be helpful
Blocks: 196213, 200087
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.4final
blocking 1.4. this shouldn't add risk (since it will be off by default), but gives us a way to track down problems in 1.4 final bits.
Flags: blocking1.4+
this is really verbose. but it's a start.
ok, that patch has landed. r/sr=bienvenu, a=sspitzer now, this can morph to improving the logging. we need log levels, so that we can reduce the verboseness. there's also some more things I'd like to PR_LOG. no longer blocks 1.4
Flags: blocking1.4+
Summary: add PR_LOG for junk mail filter, so we can evaluate problems → improve PR_LOGGING for junk mail filter, so we can evaluate problems
to use this, on windows: NSPR_LOG_FILE=c:\log.txt NSPR_LOG_MODULES=BayesianFilter:5 watch out, log.txt is going to get big on you. mine got to be 41 MB! (this is why the bug is still open, it's too verbose)
Would bug 181534 sidestep the intention of this bug (evaluating the problems of the current junk filter implementation), or does this bug block 181534?
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
Status: ASSIGNED → NEW
The existing spam logging, as mentioned in comment 5, always generates large amounts of output. This patch provides 4 different amounts of logging output: +// Logging levels are implemented as follows: +// 1 (PR_LOG_ALWAYS) just show one line per message with junk score +// 2 (PR_LOG_ERROR) add any error messages +// 3 (PR_LOG_WARNING) add per message tokens used +// 4 (PR_LOG_DEBUG) add additional tokenization results plus other details This should satisfy the needs and allow closing of this bug (plus of course allowing logging to be enabled more routinely by people who want to track spam performance without all of the excessive output).
Attachment #295742 - Flags: review?(mkmelin+mozilla)
Status: NEW → ASSIGNED
Assignee: nobody → kent
Status: ASSIGNED → NEW
QA Contact: esther → backend
Hardware: PC → All
Target Milestone: mozilla1.4final → mozilla1.9 M11
Attachment #124050 - Attachment description: patch → [checked in] patch
Comment on attachment 295742 [details] [diff] [review] Add rational log levels I'm only a reviewer for mail/ - looks good to me though. Try r?/sr? from bienvenu, he's ccd.
Attachment #295742 - Flags: review?(mkmelin+mozilla)
Attachment #295742 - Flags: superreview?(bienvenu)
Attachment #295742 - Flags: review?(bienvenu)
Comment on attachment 295742 [details] [diff] [review] Add rational log levels thx, Kent.
Attachment #295742 - Flags: superreview?(bienvenu)
Attachment #295742 - Flags: superreview+
Attachment #295742 - Flags: review?(bienvenu)
Attachment #295742 - Flags: review+
Keywords: checkin-needed
Checking in mailnews/extensions/bayesian-spam-filter/src/nsBayesianFilter.cpp; /cvsroot/mozilla/mailnews/extensions/bayesian-spam-filter/src/nsBayesianFilter.cpp,v <-- nsBayesianFilter.cpp new revision: 1.68; previous revision: 1.67 done
Status: NEW → RESOLVED
Closed: 18 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: