autolearn=disabled why?

[Kyle Wheeler]

Hello,

I've noticed some odd behavior in spamc/spamd, and I'm curious if it's
the "expected" behavior or if something is wrong. Specifically, in my
email headers, I see all the usual tags, and then autolearn=disabled.
Now, I want autolearning, I like autolearning, and it's done
autolearning in the past with no problem.

The reason I think it might be expected behavior is because of my setup,
which is a little odd. My mail gets scanned twice: once by spamassassin,
once by spamc, with a "spamassassin -d" in the middle. (I'm in the
middle of tentatively migrating from spamassassin to spamc/spamd --- I
used to have problems with spamc/spamd locking up and not processing
email, but with newer versions, I want to give it another shot.) I'm
using SpamAssassin 3.0.3 (stuck here until Debian decides it's worth
their while to release 3.0.4 into stable :P). I run the original
spamassassin with no flags, via procmail, like so:

:0 fw: spamassassin.lock
| env HOME=${HOME} /usr/bin/spamassassin

HOME is constructed, because this procmail is called by vpopmail's
delivery mechanism.

That's been working flawlessly, including auto-learning, but it's eating
lots of CPU. Now I'm adding this:

:0 fw
| spamassassin -d

:0 fw: spamassassin.lock
| spamc -U /var/lib/spamassassin/sock -u ***@mydomain.com

Spamd is running like this:

/usr/bin/spamd \
--syslog=stderr \
--max-children 5 \
--socketpath=/var/lib/spamassassin/sock --socketowner=vpopmail \
--socketgroup=vchkpw \
-H --create-prefs --vpopmail -u vpopmail 2>&1

Is it disabling the autolearning because it already autolearned it,
maybe? Or is it disabling the autolearning because of something else
that might be going wrong?

~Kyle
--
I am against religion because it teaches us to be satisfied with not
understanding the world.
-- Richard Dawkins

[Theo Van Dinter]

Post by Kyle Wheeler
Is it disabling the autolearning because it already autolearned it,
maybe? Or is it disabling the autolearning because of something else
that might be going wrong?

It's disabled because you've disabled it somewhere. :)

This is in the FAQ: http://wiki.apache.org/spamassassin/AutolearningNotWorking

[Kyle Wheeler]

Post by Theo Van Dinter

Post by Kyle Wheeler
Is it disabling the autolearning because it already autolearned it,
maybe? Or is it disabling the autolearning because of something else
that might be going wrong?

It's disabled because you've disabled it somewhere. :)
This is in the FAQ: http://wiki.apache.org/spamassassin/AutolearningNotWorking

Ah, excellent --- that exactly answers my question. (Now it says
autolearn=unavailable, rather than autolearn=disabled.)

In my own defense, that page isn't on the FAQ page:
http://wiki.apache.org/spamassassin/FrequentlyAskedQuestions - it's not
obvious that there are more FAQs that aren't listed there available on
the CategoryFaq page.

~Kyle
--
Time is an illusion. Lunchtime doubly so.
-- Douglas Adams

[Bill Taroli]

Post by Theo Van Dinter

Post by Kyle Wheeler
Is it disabling the autolearning because it already autolearned it,
maybe? Or is it disabling the autolearning because of something else
that might be going wrong?

It's disabled because you've disabled it somewhere. :)
This is in the FAQ: http://wiki.apache.org/spamassassin/AutolearningNotWorking

I've been very concerned about the autolearn=unavailable, since to me
this indicates some kind of configuration or environment problem. I
would prefer that it just say "no" or something a little more germane to
the situation that this is a catch-all for any possible unknown
condition: "unknown".

I suppose, like always, the only way to be sure of why it's
"unavailable" is to spamassassin -D on it. But still some care should be
taken that the word used is generally meaningful from the perspective of
a mail admin reading it. "unavailable" can mean something really
horrible when you're using MySQL... or even Bayes (file perms, etc).

Bill

[Aiko Barz]

Post by Kyle Wheeler
/usr/bin/spamd \
--syslog=stderr \
--max-children 5 \
--socketpath=/var/lib/spamassassin/sock --socketowner=vpopmail \
--socketgroup=vchkpw \
-H --create-prefs --vpopmail -u vpopmail 2>&1

I had a similar problem some time ago. I switched the spamd uid from "root"
to "spamd". But spamd is the one who does the learing stuff. So he
wants to be able to enter $HOME. Because every of my users has its
own uid, I did the following:

PATH OWNER PERMISSIONS
$HOME uid:users 710
$HOME/.spamassassin/ spamd:users 700
$HOME/.maildir/ uid:users 700

spamd can read/write the users bayes database, while the user is the only
person, who is able to access ".maildir/".
I don't know if there is a better way.

Bye,
Aiko