From owner-freebsd-perl@FreeBSD.ORG  Mon May  2 19:40:40 2005
Return-Path: <owner-freebsd-perl@FreeBSD.ORG>
Delivered-To: freebsd-perl@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E472816A4CF
	for <perl@freebsd.org>; Mon,  2 May 2005 19:40:40 +0000 (GMT)
Received: from mail.ciam.ru (mail.ciam.ru [213.147.57.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6046343D58
	for <perl@freebsd.org>; Mon,  2 May 2005 19:40:40 +0000 (GMT)
	(envelope-from sem@FreeBSD.org)
Received: from [213.85.81.137] (helo=[213.85.81.137])
	by mail.ciam.ru with esmtpa (Exim 4.x)
	id 1DSgmU-000NF7-Hj; Mon, 02 May 2005 23:40:38 +0400
Message-ID: <42768238.7050504@FreeBSD.org>
Date: Mon, 02 May 2005 23:40:40 +0400
From: Sergey Matveychuk <sem@FreeBSD.org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Brandon Kuczenski <brandon@301south.net>
References: <20050426220155.C77061@ocean.301south.net>
In-Reply-To: <20050426220155.C77061@ocean.301south.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: perl@freebsd.org
Subject: Re: SpamAssassin-3.0.2 patch?
X-BeenThere: freebsd-perl@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: maintainer of a number of perl-related ports
	<freebsd-perl.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-perl>,
	<mailto:freebsd-perl-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-perl>
List-Post: <mailto:freebsd-perl@freebsd.org>
List-Help: <mailto:freebsd-perl-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-perl>,
	<mailto:freebsd-perl-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 02 May 2005 19:40:41 -0000

Brandon Kuczenski wrote:
> A developer reports that "It's specifically a problem with perl on *BSD
> platforms."

I can't see what a problem with perl on *BSD. It most like it's a 
problem with SpamAssasin on *BSD platform.

But the patch is useful anyway.

--
Sem.