*Newbie Alert*

Afternoon all,

I'm a customer of a large host (Hostgator) and I am using their shared hosting implementation of SA for my personal email. I also have SSH access to my server, under a jailed shell.

SA works well for me, but I wanted to add bayes filtering. Hostgator told me that bayes filtering wouldn't work on a shared host, but I added the 'use bayes 1' and 'bayes_auto_learn 1' into my user_prefs file anyway. It seems to work OK and it began building a bayes_toks file. After enough mails had been processed I began seeing the Bayes rules firing off in my incoming email. This was all done some time ago.

So far, so good.

I decided to look into the kind of maintenance that might be involved, and discovered that my .spamassassin directory had /lots/ of bayes_toks.expire files in it.

I've tried running sa-learn --force-expire but nothing seems to happen at all. The .spamassassin directory shows as being owned by my current user, as do all the contents.

I tried running sa-learn -D --dump magic to see what output that gave, but it gives only this at the end of a lot of rule information:-

[375] dbg: rules: __MO_OL_4BF4C merged duplicates: __MO_OL_F6D01
[375] dbg: rules: __MO_OL_F475E merged duplicates: __MO_OL_FF5C8
[375] dbg: conf: finish parsing
[375] dbg: config: score set 1 chosen.
ERROR: Bayes dump returned an error, please re-run with -D for more information:-

The full output is here:-

http://pastebin.com/m69d332c4

What I suppose I'm trying to ask is this:-

1) Am I asking too much trying to run bayes filtering on a shared host in this manner?

2) How should I be manually maintaining the bayes data if sa-learn doesn't seem to be working from my account?

Rob

Reply via email to