> > Anyone else here trying to use SpamAssassin to filter > ALL incoming mail for many users in Vpopmail on Qmail? > > Is Qmail-Scanner the way to go? http://qmail-scanner.sourceforge.net/ > ifspamh? http://www.gbnet.net/~jrg/qmail/ifspamh > > Any tips/URLs/FAQs appreciated. > I'm pretty new to it, on the brink of understanding, > but could use any pointers from people who've beenthere/donethat. > > Thanks!
You don't have to use qmail-scanner to run SA in vpopmail. Although it is a great combination if you are looking for virus scanning as well. To run SA w/vpopmail do the following: 1. Patch vpopmail with the seekable patch (http://www.thesafebox.com). This allows procmail or maildrop to work with vpopmail. 2. Next install procmail or maildrop as a filtering/delivery agent. This is where the message is run thru SA to check for spaminess. 3. Modify the .qmail-default for each domain to look like (of course I am using maildrop): | preline maildrop ./.mailfilter 4. Here is a sample .mailfilter file: #################################################### VPOP="| /var/vpopmail/pop/bin/vdelivermail '' bounce-no-mailbox" VHOME=`/var/vpopmail/pop/bin/vuserinfo -d $EXT@$HOST` if ( $SIZE < 262144 ) { exception { xfilter "/usr/bin/spamc -f -u $EXT@$HOST" } } if (/^X-Spam-Flag: *YES/) { exception { include $VHOME/Maildir/.mailfilter } ## IF YOU WANT TO GATHER ALL SPAM INTO 1 MAILDRIR #exception { # to /home/pop/spam/ #} ## OR IF YOU WANT TO DELIVER SPAM TO THE USERS MAILDIR ## for filtering in their email client exception { to "$VPOP" } } else { exception { include $VHOME/Maildir/.mailfilter } exception { to "$VPOP" } } 5. Of course modify paths to match your site. 6. You can run SA 2.20 to recognize vpopmail virtual users. Read the "spamd/README.spamd-vpopmail" file in the dist for more info. With this you can give the users the ability to create their own user_prefs if you want. 7. The upside to integrating SA this way (instead of using qmail-scanner) is that it is easier to only run it if a user wants it whereas qmail-scanner runs *EVERY* piece of email thru it thus increasing the load on the server. I have run it both ways at my site and am now using this approach. I added a line that looks for the existence of a file in the users. IF if exists then run SA, if not then deliver normally. This gives the user the ability to turn it on/off. Of course this approach requires a perl script that users can use to modify their SA settings. _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
