On Sun, Sep 14, 2003 at 11:22:35AM +1000, Terry Allen wrote: > 1 Is it possible to install Spam Assassin for filtering & deleting > the spam without altering the existing sendmail configuration?
Yes, there is. If your machine is already using procmail as the mailer for local delivery, it is enough to just create an appropriate delivery recipe in your .procmailrc. Otherwise you'll also need a .forward file in the homes of all users that want to use spamassassin. > If so, could somoeone point me to some sort of wlakthrough or > eail me with some details please. 1. Check if procmail is being used. 1.1 Check if procmail is being used as a local mailer by default Create a file $HOME/.procmailrc for a local nonprivileged user. Have it contain :0 * Subject:.*testmail $HOME/procmail_works and send a mail to that user with the subject "testmail". If procmail_works is being created in that users $HOME, you are using procmail as a local user. 2. If procmail is not being used, create a .forward file You need to execute all of step 2.x only if step 1 did not create a procmail_works file. 2.1 Locate the procmail program # which procmail outputs a path. Write that one down. 2.2 Create a .forward file to invoke procmail Create $HOME/.forward with |"/path/to/procmail" where /path/to/procmail is the full path to procmail from 2.1. 2.3 Test again as in 1.1 The test from 1.1 should now work. 3. Create a spamassassin .procmailrc Delete the .procmailrc from 1.1 and create a new one: :0fw | /path/to/spamassassin :0 * ^X-Spam-Level:.*\*\*\*\*\*\*\*\*\*\* $HOME/spammed-sure :0 * ^X-Spam-Level:.*\*\*\*\*\* $HOME/spammed-probable where /path/to/spamassassin is the full path to spamassassin This is three rules, all starting with :0. The first one does invoke spamassassin, the second one will match all mail processed by the first rule and deliver to $HOME/spammed-sure if the mail has scored more than 10 points of spam score (count the number of \* pairs). The third rule will catch all mail with 5 to 10 points of spam score and deliver to $HOME/spammed-probably. You might want to delete spammed-sure unconditionally (you could even deliver to /dev/null, to throw such mail away) and want to check spammed-probable in regular intervals for false positives. > 3 I noticed Mailscanner during searches - is it relatively easy to > couple this with Spam Assassin? Mailscanner has support for spamassassin invocation > Many thanks for any help - I'd really rather not fiddle with > what is currently a pretty tightly locked down mail server & which is > working well. I have around 15 domains that are handling mail, so I > need to try & keep the server up & running while not stuffing any > working things up. Thanks again. You might want to look into starting spamassassin as "spamd" with the -m option and using "spamc" instead of "spamassassin" in the above mentioned examples. This is very easy, part of the default install, much faster, better load controlled and pretty much a drop-in replacement for spamassassin. Kristian ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
