This is the mail archive of the
mailing list for the Cygwin project.
RE: Mutt 1.4-1 opens mbox read-only
- From: "Gary R. Van Sickle" <g dot r dot vansickle at worldnet dot att dot net>
- To: <cygwin at cygwin dot com>
- Date: Wed, 24 Jul 2002 22:29:55 -0500
- Subject: RE: Mutt 1.4-1 opens mbox read-only
> 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.
What particular permissions were they?
> 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 $?
> 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?
mutt_dotlock isn't built as a separate executable in my distro, but rather the
functionality is compiled directly in. You have to configure with
"--enable-external-dotlock" to build it.
Gary R. Van Sickle
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html