On Fri, 10 Jun 2005 15:42:52 +0100, Peter Bowyer <peeebeee@???>
wrote:
>On 10/06/05, Marc Haber <mh+exim-users@???> wrote:
>> 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).
It works as in "uses the normal, non-bayes, spamassassin tests and
generates reports which vaguely fit the message."
>> 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.
So, I couldn't even use $local_part on the right side of the ACL
statement if I don't have a corresponding local unix account on the
system?
>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.
And there is no in-between like telling spamd where to put the
database in the file system? So I have to choose between local unix
accounts and having a fully-fledged database?
Greetings
Marc
--
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
