Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 24 Jul 2002 09:21:28 -0400
From: "Guy L. Oliver" <oliverg AT BATTELLE DOT ORG>
Subject: Re: Mutt 1.4-1 opens mbox read only
To: cygwin AT cygwin DOT com
Message-id: <20020724132128.GA520@battelle.org>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-disposition: inline

Jens,

On Mon, Jul 22, 2002 at 10:20:49PM +0200, Jens Schuessler wrote:
> > I've compiled Mutt now with --enable-dotlock=NO
> 
> IMO, the above is a bad idea because you are defeating one
> of the standard ways to lock a file to prevent corruption if
> there are multiple writers (e.g., mutt and procmail).

I ended up recompiling with out dotlock my self, because I
found that regardless of permissions on the mail file and
its directory ( I belive I tried all possible combos) I
couldnt get things to work right with dotlock on.  My
problem was different, but there you have it.  course, i'd
love to be proven wrong. :-)

> If you get a "5" (instead of "0"), then the permissions of
> /var/spool/mail are not correct.
> 
> Please try running mutt_dotlock -t on your mbox.  Does it
> indicate incorrect permissions?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/