[Kolab-devel] moew spamassassin rules
Steffen Hansen
steffen at klaralvdalens-datakonsult.se
Wed Jun 8 14:31:24 CEST 2005
On Wednesday 08 June 2005 12:19, Stephan Buys wrote:
> I am also playing with spamassasin to try increase its efficiency.
I'm doing exactly the same right now :)
> https://intevation.de/roundup/kolab/issue786
>
> What I can tell you is that I think that spamassassin's home
> directory is located in /kolab/var/amavisd/.spamassassin.
Correct. This means that if you want to run for example sa-learn, you
should:
su kolab-r
export HOME=/kolab/var/amavisd
/kolab/bin/sa-learn ...
> I dont know much about *.cf files but maybe they should be dropped in
> there?
The config part puzzles me a bit. Some of the options are in
amavisd.conf (search for spam_) because amavisd does not allow SA to
modify mail, so inserting X-Spam-* headers etc is actually done my
amavisd. Options not settable from amavisd.conf should go
to /kolab/etc/spamassassin/local.cf
> I would be interested in your results with this as this is also
> becoming an issue for us...
> On Tuesday 07 June 2005 22:03, Matt Douhan wrote:
> > Hey
> >
> > How do I make the kolab spamassassin to reckognise new *.cf files ?
> >
> > I tried replacing the local.cf file with a new one and dropped all
> > cf files into the same dir, but it did not work, I also tried
> > dropping the new cf files into the sahre/spamassassin dir but tht
> > dog did not hunt.
regards
--
Steffen Hansen | Klarälvdalens Datakonsult AB
Senior Software Engineer| http://www.klaralvdalens-datakonsult.se
|
| Platform-independent
| software solutions
More information about the devel
mailing list