From owner-freebsd-isp Fri Jan 10 4:12:25 2003 Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C908A37B401 for ; Fri, 10 Jan 2003 04:12:23 -0800 (PST) Received: from scorpio.DrkShdw.org (user205.net239.fl.sprint-hsd.net [209.26.20.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99D9143F6D for ; Fri, 10 Jan 2003 04:12:17 -0800 (PST) (envelope-from scorpio@drkshdw.org) Received: from scorpio (jeff [192.168.1.2]) by scorpio.DrkShdw.org (8.12.6/8.12.6) with ESMTP id h0ACD5kn002723 for ; Fri, 10 Jan 2003 07:13:13 -0500 (EST) (envelope-from scorpio@drkshdw.org) From: "Jeff Palmer" To: Subject: RE: SpamAssassin spawned 700 perl processes Date: Fri, 10 Jan 2003 07:13:09 -0500 Message-ID: <000101c2b8a1$a66a3960$0201a8c0@scorpio> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal In-Reply-To: <000001c2b8a0$461f26c0$0201a8c0@scorpio> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hate to follow up my own post, but I left some information out. Currently, calling spamassassin with the -L switch allows spamassassin to work, without doing any of the DNS lookups, and thereby not letting razor et al affect it's performance. This of course decreases spamassassins ability to accurately tag spam, but for now seems a very viable option. At least the mail server will continue running. And at least some spam will still be tagged. Jeff > -----Original Message----- > From: owner-freebsd-isp@FreeBSD.ORG [mailto:owner-freebsd-isp@FreeBSD.ORG] > On Behalf Of Jeff Palmer > Sent: Friday, January 10, 2003 7:03 AM > To: freebsd-isp@FreeBSD.ORG > Subject: RE: SpamAssassin spawned 700 perl processes > > Seems yesterday that razor, razor2 and pyzor were down. > The current thinking on the SA mailing lists, is that the razor > timeout setting was uneffective. > > There has been a work-around implemented in 2.50 (due any time now) > which should eliminate this problem in the future should the situation > arise again. > > > Jeff Palmer > scorpio@drkshdw.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message