From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/2007 Path: news.gmane.org!not-for-mail From: Tim Haynes Newsgroups: gmane.emacs.gnus.user Subject: Re: spam assassin filtering Date: Wed, 29 Jan 2003 21:52:43 +0000 Organization: What's Organization? Message-ID: <861y2vhbdg.fsf@potato.vegetable.org.uk> References: <874r7vclji.fsf@ibook.optushome.com.au> <87ptqiodvb.fsf@unix.home> <87u1fsw6zn.fsf@ibook.optushome.com.au> <87adhkdl4x.fsf@antithese.de> <87u1fr7lwn.fsf@jan.korger> <87vg07wtej.fsf@unix.home> Reply-To: news_reply@stirfried.vegetable.org.uk NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138668591 13508 80.91.229.2 (31 Jan 2006 00:49:51 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 00:49:51 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:30:02 2006 Original-Path: quimby.gnus.org!newsfeed1.e.nsc.no!nsc.no!nextra.com!peernews.cix.co.uk!lon1-news.nildram.net!195.149.20.147.MISMATCH!mercury.nildram.co.uk!not-for-mail X-Anti-Echelon: Montenegro Original-Newsgroups: gnu.emacs.gnus User-Agent: Gnus/5.090015 (Oort Gnus v0.15) XEmacs/21.4 (Military Intelligence, i686-pc-linux) Cancel-Lock: sha1:Ym0PCBO3sVxk/8BhSufgkIdAa7I= Original-NNTP-Posting-Host: 195.149.39.120 Original-X-Trace: 1043877426 mercury.nildram.net 166 195.149.39.120 Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:2147 Original-Lines: 29 X-Gnus-Article-Number: 2147 Tue Jan 17 17:30:02 2006 Xref: news.gmane.org gmane.emacs.gnus.user:2007 Archived-At: deskpot@despammed.com (Vasily Korytov) writes: > JK> process per message plus some MTA processes. This is verly likely to > JK> eat up all of your RAM and end in an disaster, i.e. you will loose > JK> your mail. (This happend to me while downloading ~100 messages.) > > Use spamd/spamc pair. Anyway, my old modem takes care of not losing my > mail in such situations. =)) Fetchmail will not flush a message off the upstream server if it gets a failure code from the local delivery agent. spamc/d do make it considerably quicker processing a mail, as the perl interpreter is only invoked the once. You can add locking to procmail rules (the fine manpage mentions appending a `:' to the end of the intro line to a recipe triple). Me, I have my colo-swerver handle the initial incoming mails, bogofilter being invoked for anything questionable; the mails that pass are copied on to the ISP at home and pulled down with fetchmail and re-bogofiltered as well. Seems to work :) ~Tim -- But mountains are holy places, |piglet@stirfried.vegetable.org.uk And beauty is free / We can still walk |http://spodzone.org.uk/ Through the garden | Our earth was once green |