Bug 5991 - HAM entries done automatically by system
Summary: HAM entries done automatically by system
Status: RESOLVED INVALID
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: 3.1.9
Hardware: Other Linux
: P1 critical
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-28 22:29 UTC by Hans-Joachim Fischer
Modified: 2008-10-06 13:35 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Hans-Joachim Fischer 2008-09-28 22:29:52 UTC 
SPAM emails automatically are registered in the spam data base as ham.

3.1.9-1.e15
Comment 1 Matt Kettler 2008-09-30 17:59:35 UTC 
Can you attach some samples?

Also, I would seriously consider upgrading. The 3.1.x series is pretty much dead at this point.

The current release is 3.2.5, and 3.3.0 under development.
Comment 2 Sidney Markowitz 2008-09-30 18:19:09 UTC 
Even more than samples, I would like some details. I can't make enough sense out of this bug report to be able to even start to track it down.

All you said was, "SPAM emails automatically are registered in the spam data base as ham."

The only way that could be a SpamAssassin bug is if you are using the autolearn option and mail that scores below the spam threshold is being learned as spam. Is that was is happening? If so, are you using spamassassin or spamc/spamd or some other software that uses SpamAssassin? Is it with all ham or only some ham, and if the latter under what conditions does it happen and when does it not happen?

If you are using something besides SpamAssassin's built in autolearn option, then if mail that scores as spam is automatically learned as ham it sounds like the fault of whatever you are using to decide how to learn the mail.

Details, please.
Comment 3 Sidney Markowitz 2008-10-06 13:35:10 UTC 
No response after a reasonable time. Closing as INVALID as there is not enough information here to make it a valid bug report.