From owner-freebsd-questions@FreeBSD.ORG Fri Aug 10 18:04:37 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0255616A421 for ; Fri, 10 Aug 2007 18:04:37 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from eskimo.tundraware.com (eskimo.tundraware.com [66.92.130.161]) by mx1.freebsd.org (Postfix) with ESMTP id 6EAF813C459 for ; Fri, 10 Aug 2007 18:04:34 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from [192.168.0.2] (ozzie.tundraware.com [66.92.130.199]) (authenticated bits=0) by eskimo.tundraware.com (8.14.1/8.14.1) with ESMTP id l7AI4OV4042248 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Fri, 10 Aug 2007 13:04:25 -0500 (CDT) (envelope-from tundra@tundraware.com) Message-ID: <46BCA829.3090408@tundraware.com> Date: Fri, 10 Aug 2007 13:02:17 -0500 From: Tim Daneliuk Organization: TundraWare Inc. User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: FreeBSD Mailing List Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-tundraware.com-MailScanner-Information: Please contact the ISP for more information X-tundraware.com-MailScanner: Found to be clean X-tundraware.com-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.399, required 1, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60) X-tundraware.com-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Subject: FreeBSD 6 and 'mailman' Issues X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tundra@tundraware.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2007 18:04:37 -0000 I've installed mailman from both the current ports and packages and noted a common problem. It seems that after a clean install, sometime later, permissions are getting changed on its directory tree. In going through the various /etc/periodic entries, I don't see where this is getting done. There is some very brief discussion of this in the mailman docs, but I'm still slightly confused. So..., I guess the question is, how to do I install mailman such that check_perms does not grumble about things like this: directory permissions must be 02775: /usr/local/mailman/archives/private/testing.mbox directory permissions must be 02775: /usr/local/mailman/archives/private/testing directory permissions must be 02775: /usr/local/mailman/archives/private/testing/2007-August directory permissions must be 02775: /usr/local/mailman/lists/testing Problems found: 4 Re-run as mailman (or root) with -f flag to fix Do I need to install mailman with some special flag set or is there a way to keep whatever is doing this from clobbering the permissions? FWIW, I am running sendmail with MailScanner/clamav/spamassassin. There are thus three running instances: root 1066 0.0 0.1 4492 2588 ?? Ss 11:00PM 0:10.65 sendmail: accepting connections (sendmail) root 1073 0.0 0.1 3640 2232 ?? Is 11:00PM 0:00.03 sendmail: Queue runner@00:15:00 for /var/spool/mqueue (sendmail) smmsp 1081 0.0 0.1 3508 2112 ?? Is 11:00PM 0:00.03 sendmail: Queue runner@00:15:00 for /var/spool/clientmqueue (sendmail) TIA, -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/