From owner-freebsd-questions@FreeBSD.ORG  Wed Apr 21 11:56:14 2010
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 28C171065674
	for <questions@freebsd.org>; Wed, 21 Apr 2010 11:56:14 +0000 (UTC)
	(envelope-from fquest@paz.bz)
Received: from mail.qcislands.net (mail.qcislands.net [207.34.147.83])
	by mx1.freebsd.org (Postfix) with ESMTP id 0F4928FC1A
	for <questions@freebsd.org>; Wed, 21 Apr 2010 11:56:13 +0000 (UTC)
Received: from [209.53.164.100] (helo=[192.168.1.4])
	by mail.qcislands.net with esmtp (Exim 4.71)
	(envelope-from <fquest@paz.bz>) id 1O4Y16-000IOP-JL
	for questions@freebsd.org; Wed, 21 Apr 2010 04:22:52 -0700
Message-ID: <4BCEE00D.9040704@paz.bz>
Date: Wed, 21 Apr 2010 04:22:53 -0700
From: Jim Pazarena <fquest@paz.bz>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: questions@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-local_scan: locally submitted (100)
Cc: 
Subject: spamd update
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2010 11:56:14 -0000

I recently upgraded p5-Mail-SpamAssassin on FreeBSD 8.0,
and now exim generates the following error message in
its logs:
spam acl condition: cannot parse spamd output

spamd and exim ran fine until I performed this update.
can anyone suggest where to commence fixing this?

I have already run "sa-update" which didn't fix the issue.

Thanks!