I am confused by the BAYES_00=-1.19 score. Where is it defined to user Bayes_00? I looked in /opt/zimbra/conf/local.cf and this is what is in there:

Code:

# This is the right place to customize your installation of SpamAssassin.
#
# See 'perldoc Mail::SpamAssassin::Conf' for details of what can be
# tweaked.
#
# Only a small subset of options are listed below
#
###########################################################################

From what I see in conf., pretty much everything is commented out. If that is the case where is it getting the information to run any tests at all? "use_bayes 1" I just uncommented a few minutes ago, but it seems it was using it all along anyway, except I cannot understand the large negative scores. Any help would be appreciated.

10-12-2012, 01:16 PM

jpsinacola

I have noticed that all of my e-mail is coming though BAYES_00, which is giving a -1.9. I took a look at spamassassin and ran ./sa-learn --dump magic. Returned error to use the -D option. When run with the -D option, I get a long list with this near the bottom:

So, apparently I have quite a bit of spam/ham messages in the db. From some fiddling I was doing, I guess I broke the bayes scoring portion since it is no longer in my e-mail headers. Here is the output of /opt/zimbra/conf/local.cf:

Code:

# This is the right place to customize your installation of SpamAssassin.
#
# See 'perldoc Mail::SpamAssassin::Conf' for details of what can be
# tweaked.
#
# Only a small subset of options are listed below
#
###########################################################################

My next issue is to assess the bayes scoring, since it always scores as bayes_00 even if it was an obvious spam, which drags the whole score down. That may lead me to believe that the info provided to the bayes db may not be very good. I will research this more.

10-22-2012, 01:49 PM

jpsinacola

From what I can gather, my bayes db seems to be working fine, except I cannot get it to show back in the header of my e-mail. I tried to enable dspam but that seemed to flag everything as spam. So I am back trying to get bayes to work. I checked my salocal.cf and salocal.cf.in and they both have use_bayes 1. I also check /opt/zimbra/conf/spamassassin/local.cf and that also has use_bayes 1. I have stopped and restarted all Zimbra services. I am not sure how to proceed ti get it to show up again. Any help? Here are my configs:

Code:

salocal.cf

# This is the right place to customize your installation of SpamAssassin.
#
# See 'perldoc Mail::SpamAssassin::Conf' for details of what can be
# tweaked.
#
###########################################################################
#
# rewrite_header Subject *****SPAM*****
# report_safe 1
# trusted_networks 212.17.35.
# lock_method flock

# This is the right place to customize your installation of SpamAssassin.
#
# See 'perldoc Mail::SpamAssassin::Conf' for details of what can be
# tweaked.
#
# Only a small subset of options are listed below
#
###########################################################################

I am going to look for a vanilla copy of both files, even though mine may be or very close to originals anyway. Any reason anyone can think of why it would be in the email header would be a big help.

10-24-2012, 09:15 AM

jpsinacola

:mad:
With my tinkering and attempt to learn how this all works together, I am only left to surmise that I changed use_bayes 1 to use_bayes 0 at some point, and changed it back. However, I did not get the bayes filtering back. Even though I checked salocal.cf.in, salocal.cf. and local.cf, at this point all have use_bayes 1. I have stopped and restarted all services and still no bayes. Spamassassin is working, I am also using RBL's. Where can I look to see what is going on with bayes and how I can make it work again?

10-24-2012, 09:21 AM

jpsinacola

Ok, well, this is odd. I noticed in my zmlocalconfig that mysql was enabled, which I do not recall enabling. So I looked up how to revert back to the default db, so I did that and then restarted all services. Voila, Bayes is now back in my email header. So, it looks like it was the mysql setting to TRUE, which I changed back to FALSE. Maybe all this blabbering will help someone some day.