Bayes troubles

[Will Nordmeyer <wi...@willspc.net>]

I'm running SA 3.1.1 on my Cobalt RaQ 4 and have been having expiration 
troubles.  A mail message comes in, and as part of the process, the 
auto_expire runs (it seems) - it frequently times out though, leaving 
the half finished expire file out there (which then results in grumpy 
customers complaining because their accounts are full).

I tried switching to a systemwide Bayes - 
I created a directory /etc/mail/spamassassin/bayes
I gave that directory 777 permissions and made the owner "nobody"

I added the following fields to local.cf

# Enable the Bayes system
use_bayes 1
bayes_file_mode 0777
bayes_path /etc/mail/spamassassin/bayes/bayes


But it seems that everybody's local bayes system continues to be run.

What'd I do wrong?

--Will

RE: Bayes troubles

[Will Nordmeyer <wi...@willspc.net>]

OK...  I did the greps you recommended and didn't find any use_dcc lines...
I even did:

grep use_dcc /home/sites/*/users/*/.spamassassin/user_prefs and still didn't
find anything (checking all user directories).

(actually, my running SA build is in /home/spam-filter... (bin, share, etc.
- I'm on a cobalt RAQ and can't upgrade the primary PERL to PERL 5.8 - so I
made a little subsystem)

I found the report_contact flag in the 10_misc.cf in both
/usr/share/spamassassin & /home/spam-filter/share/spamassassin.  

I have an old build in /usr/share/spamassassin that I need to delete (thanks
for reminding me).

I think I'll hold out until V3.1.2 is released since, according to traffic
here, it is fairly close.  (Maybe I'll download & install the latest razor
and be razoring as well now).

Thanks Matt!

--Will

-----Original Message-----
From: Matt Kettler [mailto:mkettler@evi-inc.com] 
Sent: Friday, April 28, 2006 11:40 AM
To: Will Nordmeyer
Cc: users@spamassassin.apache.org
Subject: Re: Bayes troubles

Will Nordmeyer wrote:
> Matt,
> 
> I ran lint this AM (I frequently forget that part :-)), and only had 2
> issues - 
> 
> warn: config: failed to parse line, skipping: use_dcc 1
> warn: config: warning: score set for non-existent rule RAZOR2_CHECK
> 
> I can't find where the use_dcc or the RAZOR2_CHECK are set though.  None
of
> the .cf files in /etc/mail/spamassassin have them.

Perhaps a user_prefs has them.
Or if you have "inherited" a system,someone edited the /usr/share/ files?
Or maybe someone put it in a .pre file in /etc/mail/spamassassin?


grep use_dcc /usr/share/spamassassin/*.cf
grep use_dcc /etc/mail/spamassassin/*.cf
grep use_dcc /etc/mail/spamassassin/*.pre
grep use_dcc ~/.spamassassin/user_prefs

> 
> I tried running the spamassassin --lint --debug and dump the dbg output to
a
> file, but apparently I'm screwing up the redirect because my output file
> always is empty.

You can't redirect the debug output with > or |. It is output to stderr, not
stdout.

In bash type shells you can re-direct stderr using 2> instead of >

> 
> I'm running via spamd and have restarted spamd.  By the way, I'm running
> V3.1.1 (and for some reason it puts @@CONTACT_ADDRESS@@ in the emails
saying
> that spam detection software running on blah blah blah - know how I can
> easily fix that without having to rebuild?).


That makes me fairly concerned about the integrity of the build. I'd
strongly
suggest rebuilding anyway.

That said, you can edit /usr/share/spamassassin/10_misc.cf and edit the
report_contact option there. BE VERY careful editing this, and be sure to
lint
afterwards.

Note: In the general case I would advise against editing any of the .cf
files in
/usr/share/spamassassin. They will all be obliterated and re-written if you
upgrade or re-install. In this case, that's perfectly fine.

Re: Bayes troubles

[Matt Kettler <mk...@evi-inc.com>]

Will Nordmeyer wrote:
> Matt,
> 
> I ran lint this AM (I frequently forget that part :-)), and only had 2
> issues - 
> 
> warn: config: failed to parse line, skipping: use_dcc 1
> warn: config: warning: score set for non-existent rule RAZOR2_CHECK
> 
> I can't find where the use_dcc or the RAZOR2_CHECK are set though.  None of
> the .cf files in /etc/mail/spamassassin have them.

Perhaps a user_prefs has them.
Or if you have "inherited" a system,someone edited the /usr/share/ files?
Or maybe someone put it in a .pre file in /etc/mail/spamassassin?


grep use_dcc /usr/share/spamassassin/*.cf
grep use_dcc /etc/mail/spamassassin/*.cf
grep use_dcc /etc/mail/spamassassin/*.pre
grep use_dcc ~/.spamassassin/user_prefs

> 
> I tried running the spamassassin --lint --debug and dump the dbg output to a
> file, but apparently I'm screwing up the redirect because my output file
> always is empty.

You can't redirect the debug output with > or |. It is output to stderr, not stdout.

In bash type shells you can re-direct stderr using 2> instead of >

> 
> I'm running via spamd and have restarted spamd.  By the way, I'm running
> V3.1.1 (and for some reason it puts @@CONTACT_ADDRESS@@ in the emails saying
> that spam detection software running on blah blah blah - know how I can
> easily fix that without having to rebuild?).


That makes me fairly concerned about the integrity of the build. I'd strongly
suggest rebuilding anyway.

That said, you can edit /usr/share/spamassassin/10_misc.cf and edit the
report_contact option there. BE VERY careful editing this, and be sure to lint
afterwards.

Note: In the general case I would advise against editing any of the .cf files in
/usr/share/spamassassin. They will all be obliterated and re-written if you
upgrade or re-install. In this case, that's perfectly fine.

RE: Bayes troubles

[Will Nordmeyer <wi...@willspc.net>]

Matt,

I ran lint this AM (I frequently forget that part :-)), and only had 2
issues - 

warn: config: failed to parse line, skipping: use_dcc 1
warn: config: warning: score set for non-existent rule RAZOR2_CHECK

I can't find where the use_dcc or the RAZOR2_CHECK are set though.  None of
the .cf files in /etc/mail/spamassassin have them.

I tried running the spamassassin --lint --debug and dump the dbg output to a
file, but apparently I'm screwing up the redirect because my output file
always is empty.

I'm running via spamd and have restarted spamd.  By the way, I'm running
V3.1.1 (and for some reason it puts @@CONTACT_ADDRESS@@ in the emails saying
that spam detection software running on blah blah blah - know how I can
easily fix that without having to rebuild?).

--Will
-----Original Message-----
From: Matt Kettler [mailto:mkettler@evi-inc.com] 
Sent: Thursday, April 27, 2006 5:37 PM
To: Will Nordmeyer
Cc: users@spamassassin.apache.org
Subject: Re: Bayes troubles

Will Nordmeyer wrote:

> I added the following fields to local.cf
> 
> # Enable the Bayes system
> use_bayes 1
> bayes_file_mode 0777
> bayes_path /etc/mail/spamassassin/bayes/bayes
> 
> 
> But it seems that everybody's local bayes system continues to be run.

Did you run spamassassin --lint? Perhaps there's a typo in one of your .cf
files
that's causing the above to be skipped over.

(If the parser gets sufficiently confused it may wind up skipping large
parts of
your config while it tries to recover. Rules with no ending delimiter for a
regex are particularly good at causing this, but other things can too.)

If you use spamd, or any tool that calls SA at the Perl API level
(MailScanner,
Amavis, etc) did you restart it? (local.cf is only parsed by these at
startup).

Re: Bayes troubles

[Matt Kettler <mk...@evi-inc.com>]

Will Nordmeyer wrote:

> I added the following fields to local.cf
> 
> # Enable the Bayes system
> use_bayes 1
> bayes_file_mode 0777
> bayes_path /etc/mail/spamassassin/bayes/bayes
> 
> 
> But it seems that everybody's local bayes system continues to be run.

Did you run spamassassin --lint? Perhaps there's a typo in one of your .cf files
that's causing the above to be skipped over.

(If the parser gets sufficiently confused it may wind up skipping large parts of
your config while it tries to recover. Rules with no ending delimiter for a
regex are particularly good at causing this, but other things can too.)

If you use spamd, or any tool that calls SA at the Perl API level (MailScanner,
Amavis, etc) did you restart it? (local.cf is only parsed by these at startup).