On 08/22/2012 04:10 PM, Ben Johnson wrote:
I did end-up overriding the bayes_path, which provided a workaround for
the permissions issues. Cheers to the suggestion.
This is not a workaround, it's common practice in many types of setups
and documented, but due to numerous reasons can't be set as a default.
If the install routine would require/create a
/etc/mail/spamassassin/bayes path it could bite "other" systems than
standard Linux distros.
(note to myself: discuss this in dev list)
As so often, the clue is diagnostics.
In this case, I think we all worked backwards, first answering your
questions before getting the big picture.
Defining a global
bayes database is probably a better solution overall, but bear in mind
if you have to wipe and retrain you need to check the permissions on the
new database files after you run sa-learn the first time.
This is an important point; thanks for articulating it.
Once you start seeing bayes hits, I'd switch to autolearn, disable auto
expiration and set a weekly cron job to do the expiration.
That way Bayes keeps itself busy and you only have to train low scored
stuff on a daily basis (cron job as amavis imap user user) or rsync the
imap folder content out and sa-learn from target path
All appears to be well in SpamAssassin Town for the time being (don't
think you've heard the last of me, though!). Thanks to everyone who
shared his or her expertise.
Learning SA seems like a never ending process - the deeper you go, the
more of its beauty comes to light.
Axb
