On Thu, 2004-12-23 at 19:51 -0800, suse-list wrote:
David Install amavisd, clamav Update via yast.
Set in yast to use amavisd with postfix.
Now all of your configurations are run from /etc/amavisd.conf. That is you will not use your spam settings under the spammassasin config file (not totally true, but it helps to know this.). This should help.....
<SNIP>
I read through some of Neal's stuff, specifically this: http://www.justsuse.com/guides.php?which=23 The bottom line is that I'm going to write up what's going on here. Mail comes to port 25. Postfix picks it up. Postfix's config passes the email to amavisd running on port 10024. (Look at /etc/postfix/master.cf.) Then amavisd passes the email back to postfix on port 10025. (Look at /etc/amavisd.conf.) (Amavisd is configured OotB with the support for using clamd NOT enabled. Also clamd is setup for network use, not local, which I think would be backwards of the normal use case. Why SuSE would ship the config like this, I have NO idea, but you'll have to change these things.) Here's the tricky part. If you want spam scanning, you can take two paths. According to the article above, calling spamassassin from amavis makes spamassassin look for configs in different places, and might (I can't really be sure) not look at users' ~/.spamassassin/user_prefs.) I decided to skip allowing amavis to pass off to spamassassin. I commented out the spam checks in its config file. Instead, I put my old /etc/procmailrc file back into place: :0 hbfw | /usr/bin/spamc Which hands off to spamd. Luckily, it would seem that spamassassin is smart enough not to scan the email twice. If I leave spam detection enabled in amavis, and leave my feed to spamc in my procmailrc file, it would seem that only the amavis check is performed. So, at least there's that, right? This seems to be the most general way of using the tools as shipped. YMMV. I have to take SUSE to task on this one. There ought to be some writeup in the manual on how their email config is supposed to work. This whole setup took me almost a whole day to probe from the backside to see how it worked. Admittedly, I had never used virus scanning in email before, so this was a new chapter. But it remains that just writing up a few paragraphs like I did above would really have saved me a lot of time, and I'm sure I'm not alone here. Regards, dk