From owner-freebsd-perl@FreeBSD.ORG  Fri May 28 17:08:19 2004
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 3335316A4CE
	for <perl@freebsd.org>; Fri, 28 May 2004 17:08:19 -0700 (PDT)
Received: from forrie.com (forrie.ne.client2.attbi.com [24.62.207.61])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A232543D1D
	for <perl@freebsd.org>; Fri, 28 May 2004 17:08:18 -0700 (PDT)
	(envelope-from forrie@forrie.com)
Received: from [127.0.0.1] (i-95.forrie.net. [192.168.1.95])
         by forrie.com  with ESMTP id i4T087UU010619
         for <perl@freebsd.org>; Fri, 28 May 2004 20:08:09 -0400 (EDT)
         (envelope-from forrie@forrie.com)
Message-ID: <40B7D465.4020508@forrie.com>
Date: Fri, 28 May 2004 20:08:05 -0400
From: Forrest Aldrich <forrie@forrie.com>
User-Agent: Mozilla Thunderbird 0.6+ (Windows/20040528)
X-Accept-Language: en
MIME-Version: 1.0
To: perl@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-RAVMilter-Version: 8.3.0(snapshot 20010925) (forrie.ne.client2.attbi.com)
X-MailScanner-LocalNet: Found to be clean
Subject: SpamAssassin Port (setuid issues)...
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: Sat, 29 May 2004 00:08:19 -0000

Has anyone noted problems with "spamd" not being able to properly setuid 
to various users?

I seem to be having this problem (FreeBSD-4.10) -- I've had to shut off 
per-user configuration to stop the failures... I've also had to adjust 
and readjust the permissions in /var/spool/spamassassin to get the db 
functions to work properly.   I do use spamass-milter, but I don't 
believe there are conflicts here -- when I use spamd configured properly 
(with the right user and permissions) and even as root, it still 
generates errors about not being able to access per-user configuration.

Sorry if that's too general of a description - I simply haven't been 
able to narrow down the problem.