Jari Fredriksson wrote:
>
>
> One can also use
>
> bayes_sql_override_username spam
>
> in local.cf, if the bayes is in a SQL database. I have that, and there
> seems to be no difference if I use -u or not.
>
>
I was wondering whether it was a user issue earlier, but I tried sa-learn
--username=user --dump magic and it seemed to give the same result as the
default user. I tried various different users (even made some up!) but it
didn't complain - still gave me the same dump.
While writing this, I just checked messages on another domain/user and found
that bayes is working there! phew! That's a relief... it seems that it is
only on my domain that we have an issue.
On Friday, due to a lack of understanding of how spamassassin works, I
renamed the following:
/home/snowbnet/.spamassassin/bayes.mutex
/home/snowbnet/.spamassassin/bayes_journal
/home/snowbnet/.spamassassin/bayes_seen
/home/snowbnet/.spamassassin/bayes_toks
I added .old to the end of each.
Afterwards, spamassassin recreated them and I though all was good, but
because bayes stopped working, I changed them back and removed the newly
created versions. In hind sight, I guess it just needed training. Anyway,
don't know if what I did is related to this problem.
Is the 'user', the email account user or the domain user?
Also, I've just noticed that the bayes_journal has not been modified since
Saturday about the time I renamed stuff.
--
View this message in context:
http://www.nabble.com/bayes-not-active-although-enabled--tp24663548p24668896.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
