Closed Bug 198762 Opened 22 years ago Closed 22 years ago

spam not recognized; junk mail filters not working at all

Categories

(MailNews Core :: Filters, defect)

x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 194238

People

(Reporter: andreas.hoefler, Assigned: naving)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3; MultiZilla v1.4.0.2) Gecko/20030312 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3; MultiZilla v1.4.0.2) Gecko/20030312 Mozilla 1.3: Incoming spam-mail does not seem to be marked as spam even if I have hundreds of mails in my junk-folder beeing marked as spam. It seems, that junk-filter does not "learn". But training.dat grows with each marked spam-mail. Re-running junk mail controls on already spam-marked mail unmarks it again. Mozilla-profile has been converted from an old Netscape 4.71 profile at mozilla installation/first run. Reproducible: Always Steps to Reproduce: 1. Install mozilla 1.3 2. Convert old Netscape 4.71 profile with mail to mozilla profile 3. Start MailNews 4. Mark spam as junk 5. Get new spam Actual Results: New spam not marked as spam Expected Results: New spam marked as spam JunkControls is set to automatical move junk to junk-folder. Logging is activated but no logs seem to appear.
Have you explicitly marked at least one message as non-junk? (See bug 194238 for details.) If that works, please comment here or resolve the bug appropriately.
Maybe it's a dupe of bug 194238. 194238 was opened 2-20-2003 It got fixed 3-15 You're build is Mozilla 1.3 03-12-2003
Ok, marking non-spam as non-spam explicitely worked. But all messages had non-spam-mark... Wasn't there an "?"-mark somewhere in the past when mails weren't classified yet? Has this "?"-status been removed or became obsolete?
*** This bug has been marked as a duplicate of 194238 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.