From owner-freebsd-questions@FreeBSD.ORG Fri Jan 30 20:07:16 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 327ED16A4CE for ; Fri, 30 Jan 2004 20:07:16 -0800 (PST) Received: from uti.com (matrix.uti.com [204.248.52.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id A864543D1D for ; Fri, 30 Jan 2004 20:07:14 -0800 (PST) (envelope-from moliveri@uti.com) Received: from greyswandir.uti.com ([204.248.53.142]) by uti.com with esmtp (Exim 3.36 #1) id 1AmmPZ-000G6z-00 for freebsd-questions@freebsd.org; Fri, 30 Jan 2004 22:07:14 -0600 Message-Id: <5.2.0.9.0.20040130220557.00aac138@matrix.uti.com> X-Sender: moliveri@matrix.uti.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Fri, 30 Jan 2004 22:08:21 -0600 To: freebsd-questions@freebsd.org From: Mike Oliveri Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: SpamAssassin quits after upgrade X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2004 04:07:16 -0000 Hi all, I've recently upgraded both Exim (to 4.30) and SpamAssassin (to 2.63) on my FreeBSD 5.1 box via their Ports, and suddenly I can no longer get SpamAssassin to work. If I enable spam scanning in Exim (the FreeBSD port includes the Exiscan-acl patch), none of my mail is delivered. If I comment out the lines pertaining to SpamAssassin scanning, everything works fine again. Has anyone else run into this problem, and hopefully resolved it? Thank you, Mike Oliveri moliveri@uti.com