Closed
Bug 179502
Opened 22 years ago
Closed 17 years ago
investigate footprint of marking ~64k bugmails as not spam
Categories
(MailNews Core :: Filters, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: timeless, Unassigned)
References
(Blocks 1 open bug)
Details
mozilla mail used ~ 770 mb of vm to do this, and was very unresponsive on my
system because windows had trouble juggling that in 384mb of physical memory.
Updated•20 years ago
|
Product: MailNews → Core
Comment 1•18 years ago
|
||
Assigning bugs that I'm not actively working on back to nobody; use
SearchForThis as a search term if you want to delete all related bugmail at
once.
Assignee: dmose → nobody
Comment 2•17 years ago
|
||
David [arrg] this should should be dupeable to something mark read or mark junk but I'm not finding it.
aaaah, tenth query - bug 236842?
QA Contact: laurel → filters
Comment 3•17 years ago
|
||
closing invalid, given that marking 64k bugmails is not advisable and more importantly the major bayes checkin of 2004-05-12 [1]. If a problem still exists it would be against markedly different code.
[1] checkin notes: Bug #230093, Bug #181534, Bug #237095 --> Port thunderbird junk mail improvements to the trunk. Replace the core bayesian junk mail algorithm with a chi-squared probability distribution modeled after spam bayes and Gary Robinson's work. Change the model for how we count tokens across messages. Token counts get out of alignment when re-training against already classified messages. Revamp the junk mail tokenizer. Make it a hdr sink listener and add custom tokens for attachment information. Ignore tokens larger than 13 characters. Tokenize purely off of white space. Ignore tokens less than 3 bytes in length. There is still a lot more work to be done to the tokenizer."
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Assignee | ||
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
•