> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of
> Brian Wilson
> Subject: amavisd-new + spamassassin
>
>
>
> I am trying to add local rules to my spamassassin set up,
> I am running amavisd-new. It runs spamassassin but nothing I
> do appears to affect what spamassassin config files have in them.
>
> I am supposing I have to shutdown amavisd completely and restart
> it to get it to read spamassasin rules??? But even then it seems
> to ignore /etc/spamassasin/* files.
>
You will have to restart amavisd for it to load in your custom rules. Because
the path for these rules is not defined in amavisd.conf it is controlled by the
SpamAssassin defaults (which I believe is /etc/mail/spamassassin).
To test this, run "spamassassin -D --lint" as the same user that amavisd runs
as (look for the $daemon_user setting in amavisd.conf). You will most likely
need to edit /etc/passwd to allow you to su to that user. Make sure to change
it back to no shell access when you are done.
In the output of "spamassassin -D --lint" will be a line like the following:
debug: using "/etc/mail/spamassassin" for site rules dir
This will tell you where your custom rules belong. Make sure the user amavisd
runs as has read privileges to this directory and subsequent files.
The debug output will also tell you if your rules meet SpamAssassin's syntax.
> Can't quite figure this one out...
>
> I am not running amavisd chroot'ed. Pretty much followed the setup
> from the TSL wiki. I was surprised to discover that I did not have
> to have spamd running at all; amavisd runs spamassasin all on its own.
>
This is well documented. Check out http://www.ijs.si/software/amavisd/,
http://spamassassin.apache.org/, and the accompanying mailing lists for more
information.
HTH
Matt
_______________________________________________
tsl-discuss mailing list
[email protected]
http://lists.trustix.org/mailman/listinfo/tsl-discuss
