Bayes database messed up after purging some tables

I had a problem last week w/ my Maia database, and so I purged some tables that I didn’;t think were critical. After doing so, my bayes filtering began blocking a bunch of messages that shouldn217;t be blocked. It is just scoring tons of messages with the bayes_99 rule. In fact, it looks like every message is being scored by that rule. So this is obviously a big problem. I have temporarily disabled bayes filtering in spamassassin  (use_bayes 0 in local.cf).

 

The tables that were purged were:

 

awl

bayes_seen

bayes_token

maia_sa_rules_triggered

maia_stats

 

Can anyone tell me what is actually happening, as well as the correct way to fix it?

 

Thanks in advance for your help,

__

 Douglas Mortensen

         Network Consultant

           Impala Networks

 

   CCNA, MCP, MSSBS, A+, Linux+

 

Hi Douglas,

 

My First intention would be to flush the bayes_seen and the bayes_token tables again. Considering the situation we where in when we first flushed the tables maybe something went completely wrong when it started filling those empty tables  again after the first flush(with mysql acting very weird and all). ; I would also flush the maia_sa_rules table and after that run the load-sa-rules.pl script just to make sure your rules in the database are ok too (off course this has nothing to do with the scoring)

 

In my opinion it’s ok to flush the bayes_seen and bayes_token table if you want to train bayes from the beginning. Correct me if I’m wrong  someone?

 

Greetings,

 

Jeffrey Schilperoord

 

 

I had a problem last week w/ my Maia database, and so I purged some tables that I didn’;t think were critical. After doing so, my bayes filtering began blocking a bunch of messages that shouldn’t be blocked. It is just scoring tons of messages with the bayes_99 rule. In fact, it looks like every message is being scored by that rule. So this is obviously a big problem. I have temporarily disabled bayes filtering in spamassassin  (use_bayes 0 in local.cf).

 

The tables that were purged were:

 

awl

bayes_seen

bayes_token

maia_sa_rules_triggered

maia_stats

 

Can anyone tell me what is actually happening, as well as the correct way to fix it?

 

Thanks in advance for your help,

__

 Douglas Mortensen

         Network Consultant

           Impala Networks

 

   CCNA, MCP, MSSBS, A+, Linux+

 

Jeffrey,

 

I really appreciate your help. Since I’ve disabled the bayes scoring, things seem to be going ok for now, but I still want to see if we can get this fixed, and turn the bayes back on. Since, it seems that I’ve got some time here, I’m going to hold off on doing anything yet, and wait to see if we get any other advice coming through the mailing list.

 

Thanks again,

 

 

Hi Douglas,

 

My First intention would be to flush the bayes_seen and the bayes_token tables again. Considering the situation we where in when we first flushed the tables maybe something went completely wrong when it started filling those empty tables  again after the first flush(with mysql acting very weird and all). ; I would also flush the maia_sa_rules table and after that run the load-sa-rules.pl script just to make sure your rules in the database are ok too (off course this has nothing to do with the scoring)

 

In my opinion it’s ok to flush the bayes_seen and bayes_token table if you want to train bayes from the beginning. Correct me if I’m wrong  someone?

 

Greetings,

 

Jeffrey Schilperoord

 

 

I had a problem last week w/ my Maia database, and so I purged some tables that I didn’;t think were critical. After doing so, my bayes filtering began blocking a bunch of messages that shouldn217;t be blocked. It is just scoring tons of messages with the bayes_99 rule. In fact, it looks like every message is being scored by that rule. So this is obviously a big problem. I have temporarily disabled bayes filtering in spamassassin  (use_bayes 0 in local.cf).

 

The tables that were purged were:

 

awl

bayes_seen

bayes_token

maia_sa_rules_triggered

maia_stats

 

Can anyone tell me what is actually happening, as well as the correct way to fix it?

 

Thanks in advance for your help,

__

 Douglas Mortensen

         Network Consultant

           Impala Networks

 

   CCNA, MCP, MSSBS, A+, Linux+