Thanks for the suggestion. I too have had spamassassin set up through procmail, and prefer to do it this way. However, in this case, that means spamassassin is still running on our mail/NIS server, which means ypserv will continue to get snockered. I turned to doing the filtering via evolution, because then I expect the filtering will be done on a different machine - one which doesn't have problems associated with high load. On Mon, 2004-05-24 at 19:16, Tom Cooper wrote:
Dan Stromberg wrote:First off, let me say, my incoming mailbox, which I've switched to ~/mail/mybox, is huge. I'm trying to set a good example for my endusers, by not leaving this large quantity of mail in my maildrop, /var/mail/strombrg.I just went through this process, and have been quite successful.Anyway, I set up a filter which "Pipes message to shell command" spamassassin -e (with a hard path), and refiles the message if there's a nonzero exit status to my "evospam" folder. It's not working. I'm bummed. I get HUGE quantities of spam.I'm no expert on this sort of thing, but I handle this by using procmail to move my mail from the mailspool to ~/mail/MyMail Along the way, Procmail does some analysis and them invokes spamassassin to check the mail for spam. This seems to work, particularly since I've got a great body of spam with which to train spamassassin. I'm still getting some spam, but this process has helped! Here's one stanza of my .procmailrc: :0fw:spamassassin.lock | spamassassin :0e { EXITCODE=$? } :0: * ^X-Spam-Flag: Yes subfolders/caughtspam I hope that this helps! Please let me know if you need more information about this. Regards, Tom Cooper I picked up this and a bunch of other tips at the following sites: http://bradthemad.ath.cx/tech/hacks/procmail_tricks.php http://wiki.apache.org/spamassassin/UsedViaProcmail http://www1.umn.edu/adcs/help/email/UnixProcmail.html
-- Dan Stromberg DCS/NACS/UCI <strombrg dcs nac uci edu>
Attachment:
signature.asc
Description: This is a digitally signed message part