How do you get spamassassin/spamd to work with Amavis? I can't seem to find anything in the SuSE docs that match up with what I see on the internet. For example: I should be able to pop into the /etc/amavisd.conf file and just turn it on. But there's nothing there to do that.
The 03.10.12 at 19:48, Tom Allison wrote:
For example: I should be able to pop into the /etc/amavisd.conf file and just turn it on.
amavis is "turned on" from inside Yast. Spamassassin is a different thing. -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The 03.10.12 at 19:48, Tom Allison wrote:
For example: I should be able to pop into the /etc/amavisd.conf file and just turn it on.
amavis is "turned on" from inside Yast.
Spamassassin is a different thing.
I know, I have amavis turned on in Yast config files. But there is a way for amavisd to run spamassassin as just another filter. This was done under Debian over a year ago and I can't seem to find the same documentation/configuration here. Assuming that I cannot do it from amavis, is there some way that I can do it using Cyrus as my MDA? Normally I would just pop off for a bit of procmail and be done with it, but I really don't see how I can do that here, unless there is someway to chain them together like: postfix->amavis->postfix->procmail-(spamassassin)->cyrus->seive->cyrus folders. Seems rather lengthy. Can I do it in sieve?
Tom Allison wrote:
Carlos E. R. wrote:
[snip]
Normally I would just pop off for a bit of procmail and be done with it, but I really don't see how I can do that here, unless there is someway to chain them together like:
postfix->amavis->postfix->procmail-(spamassassin)->cyrus->seive->cyrus folders.
Try more recent rpms? Just a guess. They chain together fine here using the most recent rpms (amavisd-new, etc.) from the people branch of the SuSE ftp tree (complete with helpful hints in er er help files). Both amavis and spamassassin can be got at from Yast2 (sysconfig editor etc.) and are easy to manage. Spamassassin integration is one of the goals of the new version of amavis. Once you've installed spamassassin, amavisd should pick it up automatically. You can configure what amavis does with spamassassin in some detail via amavis.conf but that's all you really need to do. Which means that you don't need to invoke spamc using procmail although you'll still need to filter on the spamassassin headers. :)
The 03.10.13 at 09:20, Mark wrote:
They chain together fine here using the most recent rpms (amavisd-new, etc.) from the people branch of the SuSE ftp tree (complete with helpful
Do you remember which name (under people)?
Spamassassin integration is one of the goals of the new version of amavis. Once you've installed spamassassin, amavisd should pick it up automatically. You can configure what amavis does with spamassassin in some detail via amavis.conf but that's all you really need to do.
This is very interesting, even more for servers. -- Cheers, Carlos Robinson
participants (3)
-
Carlos E. R.
-
Mark
-
Tom Allison