From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23132 invoked by alias); 25 Jul 2002 03:30:03 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 23112 invoked from network); 25 Jul 2002 03:30:02 -0000 Received: from unknown (HELO mtiwmhc22.worldnet.att.net) (204.127.131.47) by sources.redhat.com with SMTP; 25 Jul 2002 03:30:02 -0000 Received: from utq6e ([12.75.137.151]) by mtiwmhc22.worldnet.att.net (InterMail vM.4.01.03.27 201-229-121-127-20010626) with SMTP id <20020725032956.EYTP2117.mtiwmhc22.worldnet.att.net@utq6e> for ; Thu, 25 Jul 2002 03:29:56 +0000 From: "Gary R. Van Sickle" To: Subject: RE: Mutt 1.4-1 opens mbox read-only Date: Thu, 25 Jul 2002 05:44:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: <20020724123728.GA1556@tishler.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-SW-Source: 2002-07/txt/msg01986.txt.bz2 > 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. What particular permissions were they? > 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? 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 Brewer. Patriot. -- 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/