From owner-freebsd-questions@FreeBSD.ORG Mon Mar 2 13:58:29 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B604106566C for ; Mon, 2 Mar 2009 13:58:29 +0000 (UTC) (envelope-from mikhailg@webanoide.org) Received: from msa.vap.navalradio.cl (smtp.vap.navalradio.cl [201.236.67.147]) by mx1.freebsd.org (Postfix) with ESMTP id C822F8FC14 for ; Mon, 2 Mar 2009 13:58:28 +0000 (UTC) (envelope-from mikhailg@webanoide.org) Received: from [172.18.80.120] ([172.18.80.120]) (authenticated bits=0) by msa.vap.navalradio.cl (8.14.2/8.14.2) with ESMTP id n22DwP7Y003318; Mon, 2 Mar 2009 13:58:26 GMT (envelope-from mikhailg@webanoide.org) Message-ID: <49ABE5FC.40009@webanoide.org> Date: Mon, 02 Mar 2009 10:58:20 -0300 From: Mikhail Goriachev Organization: Webanoide User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Andrew Moran References: <8806A36E-A839-481A-8E59-9F79DEB6B51A@me.com> In-Reply-To: <8806A36E-A839-481A-8E59-9F79DEB6B51A@me.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: SpamAssassin/Perl eating enormous amounts of memory? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2009 13:58:29 -0000 Andrew Moran wrote: [...] > Has anyone heard of this? Or any pointers on what I can do to figure > out what is causing it? > > Your advice is much appreciated. As an alternative: You could try mail/mimedefang. It calls spamassassin to evaluate an e-mail but without having it running all the time. This can solve your problem of running out of memory. For instance, sendmail could be the first line of defence with its own rules (rDNS, noMX, RBLs and what not). Then mimedefang with a set of rules to further reject dodgy e-mails (helo/ehlo, spoofings, SPF and so on). After that, spamassassin comes into play (controlled by mimedefang), but only at the end as a last line of defence. By the time it gets to the end, a lion's share has already been rejected and that means less work for spamassassin. I hope this helps. Regards, Mikhail.