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 08:37:28 -0400
From: Jason Tishler <jason AT tishler DOT net>
Subject: Re: Mutt 1.4-1 opens mbox read-only
In-reply-to: <20020722202048.GA21538@trash.net>
To: cygwin AT cygwin DOT com
Mail-followup-to: cygwin AT cygwin DOT com
Message-id: <20020724123728.GA1556@tishler.net>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
User-Agent: Mutt/1.4i
References: <20020722202048 DOT GA21538 AT trash DOT net>

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).

While installing Cygwin exim yesterday, I *may* have stumbled onto your
problem.  After changing the permissions of /var/spool/mail to meet the
needs of exim, I started to get the read-only mbox problem myself.  I
determined that if mutt cannot dotlock an mbox then it will open it
read-only.  This can easily tested by using mutt_dotlock:

    $ mutt_dotlock -t /var/spool/mail/jt
    $ echo $?
    5

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?

Jason

--
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/