On 10/06/05, Marc Haber <mh+exim-users@???> wrote:
> Hi,
>
> I am currently making my first attempts at content scanning with
> exiscan and spamassassin.
>
> On my test host, I would like to have one spamassassin bayes database
> per recipient domain, and have thus configured exim like:
>
> | warn
> | spam = $domain:true
> | set acl_VAR_SPAM_SCORE = ($spam_bar) $spam_score
> | set acl_VAR_SPAM_REPORT = $spam_report
>
> This works fine and gives me spamassassin headers.
Does it? $domain isn't defined in the DATA acl for the oft-quoted
reason that you might have more than one recipient. I think it might
be using a default (and I don't know what that default might be).
> However, I don't see any bayes database being written to the FS, and
> no bayes tags show up in the spamassassin headers.
SA uses the unix user you pass and stores the db in ~/.spamassassin/,
unless overridden, and unless you've enabled SQL for Bayes.
Bayes tests don't kick in until SA has learnt 200 spam and 200 ham
messages (both of which numbers can be overridden). If you're seeing
autolearn=ham and autolearn=spam, it's busy learning and will start
using the BAYES_XX tests as soon as it's seen enough.
IMHO the SQL back-end is more flexible than the filesystem because it
will handle arbitrary 'virtual' users, as long as you can send in a
'username' in the 'spam=' line.
Peter
--
Peter Bowyer
Email: peter@???
Tel: +44 1296 768003
VoIP: sip:peter@???
