Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Connect » BAYES_00: -1.665 on spam messages? (should I reset my spammassasin db?)
  •  
sproket90

Messages: 37
Karma: 0
Send a private message to this user
Hi all,

I have notice many, almost all messages that are spam have the a negative BAYES_00: -1.665, score... example

X-Spam-Status: No, hits=2.5 required=3.5
tests=DNSBL_BL.SPAMCOP.NET: 2.10,DNSBL_ZEN.SPAMHAUS.ORG: 2.10,BAYES_00: -1.665,
TOTAL_SCORE: 2.535


What does this mean? and should I just reset the spamassasin DB?

Thanks,
Sproket90

Smile
  •  
m.sand

Messages: 35
Karma: -4
Send a private message to this user
Seeing the same problem here.
X-Spam-Status: No, hits=4.3 required=4.5tests=DNSBL_ZEN.SPAMHAUS.ORG: 6.00,BAYES_00: -1.665,HTML_MESSAGE: 0.001,TOTAL_SCORE: 4.336
X-Spam-Level: ****


Another problem is that I have configured SPF Failed Checks with 1.5 points, but that does not show up... Why?
  •  
m.sand

Messages: 35
Karma: -4
Send a private message to this user
From the debug-files I get the following:
Seems like the spammers are getting better...

16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: bayes: tie-ing to DB file R/O /opt/kerio/mailserver/store/spamassassin/bayes/bayes_toks
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: bayes: tie-ing to DB file R/O /opt/kerio/mailserver/store/spamassassin/bayes/bayes_seen
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: bayes: found bayes db version 3
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: bayes: DB journal sync: last sync: 1239832635
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: bayes: corpus size: nspam = 1375, nham = 9908
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: bayes: score = 0
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: bayes: DB expiry: tokens in DB: 109932, Expiry max size: 150000, Oldest atime: 1236966093, Newest atime: 1239860933, Last expire: 1239731477, Current time: 1239861397
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: bayes: DB journal sync: last sync: 1239832635
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: bayes: untie-ing
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: bayes: untie-ing db_toks
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: bayes: untie-ing db_seen
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: rules: ran eval rule __TAG_EXISTS_BODY ======> got hit
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: rules: ran eval rule HTML_90_100 ======> got hit
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: rules: ran eval rule BAYES_00 ======> got hit
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: rules: ran eval rule __MIME_HTML ======> got hit
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: rules: ran eval rule HTML_MESSAGE ======> got hit
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: rules: ran eval rule __TAG_EXISTS_HTML ======> got hit
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: rules: ran eval rule MIME_HTML_ONLY ======> got hit
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: rules: ran eval rule HTML_TITLE_EMPTY ======> got hit
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: rules: ran eval rule __TAG_EXISTS_HEAD ======> got hit
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: rules: running raw-body-text per-line regexp tests; score so far=-1.335
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: rules: running full-text regexp tests; score so far=-1.335
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: check: running tests for priority: 500
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: rules: running meta tests; score so far=-1.335
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: rules: running header regexp tests; score so far=-1.335
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: rules: running body-text per-line regexp tests; score so far=-1.335
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: uri: running uri tests; score so far=-1.335
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: rules: running raw-body-text per-line regexp tests; score so far=-1.335
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: rules: running full-text regexp tests; score so far=-1.335
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: check: running tests for priority: 1000
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: rules: running meta tests; score so far=-1.335
[16/Apr/2009 00:56:37][5913] {spamassassin} Perl_stderr: [5912] dbg: rules: running header regexp tests; score so far=-1.335
  •  
m.sand

Messages: 35
Karma: -4
Send a private message to this user
After getting 5 spams/min I decided to reset the SpamAssassin db and now everything is working as expected and I get score of 15-20 on the incoming mails. Have no clue what happened to make the db corrupt(?). To bad that a years worth of learning just got erased but the situation was not tolerable.

/msa
  •  
freakinvibe

Messages: 1541
Karma: 62
Send a private message to this user
Quote:

To bad that a years worth of learning just got erased


That's not quite correct. The Bayes DB can only hold a certain amount of tokens, so you probably lost some weeks (depending on how much spam you get).

Dexion AG - The Blackberry Specialists in Switzerland
https://dexionag.ch
  •  
m.sand

Messages: 35
Karma: -4
Send a private message to this user
OK. And with the flood of spam coming in it will probably learn pretty fast... Very Happy
Previous Topic: KOC offline store - encrypted?
Next Topic: Kerio and Vmware ESX
Goto Forum:
  


Disclaimer:
Kerio discussion forums are intended for open communication between forum members and may contain information and material posted by members which may be useful in learning about Kerio products. The discussion forums are not intended to provide technical support for any specific product. Any information implied or expressed in the discussion forums is that of the posting member. Kerio is in no way responsible for the information posted in the forums, or its accuracy. Kerio employees may participate in the discussions, but their postings do not represent an offical position of the company on any issues raised or discussed. Kerio reserves the right to monitor and maintain the forums to promote free and accurate exchange of information.

Current Time: Thu Oct 19 09:11:11 CEST 2017

Total time taken to generate the page: 0.00445 seconds
.:: Contact :: Home ::.
Powered by: FUDforum 3.0.4.