Even though you run this in mysql now, it still DOES matter who you run it as. I found out the hard way that it records the user that is logged in as the user the bayes applies as in the database. I had to actually set the bayes_sql_override_username in my local.cf. I trained a bunch of messages as root and my spamassassin (through amavis-new) runs as amavis. It didn't see any of the bayes training I did!
Keith > Ernie Dunbar wrote: >>>>Oct 5 13:26:39 pop spamd[19660]: Cannot open bayes databases >>>>/home/spamc/.spamassassin/bayes_* R/O: tie failed: Permission denied >>>> Oct >>> >>>The typical cause of this is that the file ownership changed on the >>>bayes files when you converted them to 3.0. At least this was the >>> problem >>>I encountered. >>> >>>When I did all my conversions following the UPGRADE procedure as root, I >>>had to go back in and convert the files back to their correct >>> ownerships. >>>Check for that. >> >> >> That's kind of the odd thing. I set the ownership back to spamc, but it >> was changed to root for bayes_journal and bayes_toks shortly therafter. >> >> What I did instead of UPGRADEing, was nuke the whole database and >> rebuild >> it from scratch using some new spam. >> > > This can happen if you have any scripts or process that you use to train > the bayes database. Awhile ago I ran into this issue a few times when I > was logged in as root and manually trained a message (cat msg | sa-learn > --spam), which would occasionally change the ownership of the > journal/etc to root. Fixed that by not doing it as root, though now I > have bayes in SQL so it doesn't matter. > > Ryan Moore > ---------- > Perigee.net Corporation > 704-849-8355 (sales) > 704-849-8017 (tech) > www.perigee.net > > >
