From owner-freebsd-current  Thu Nov 16  8:36:42 2000
Delivered-To: freebsd-current@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP id 58A4E37B4CF
	for <freebsd-current@FreeBSD.ORG>; Thu, 16 Nov 2000 08:36:39 -0800 (PST)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA83126;
	Thu, 16 Nov 2000 11:36:13 -0500 (EST)
	(envelope-from wollman)
Date: Thu, 16 Nov 2000 11:36:13 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <200011161636.LAA83126@khavrinen.lcs.mit.edu>
To: void <float@firedrake.org>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Proper permissons on /var/mail
In-Reply-To: <20001116151809.A15312@firedrake.org>
References: <Pine.BSF.4.21.0011160650180.41866-100000@arnold.neland.dk>
	<20001116151809.A15312@firedrake.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

<<On Thu, 16 Nov 2000 15:18:09 +0000, void <float@firedrake.org> said:

> I have a similar problem -- every time I make world, perms on /var/mail
> get set to 775.  Mutt considers my mailbox read-only until I change it
> to 1777.

It is misconfigured (or perhaps just broken).  1777 mode for /var/mail
is insecure, but was necessary in the mists of ancient past, before
UNIX learned to do file locking.  Unless your mail spool is shared
over NFS (don't do that), locking is reliable and .lock files should
never be used or relied upon.

-GAWollman



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message