Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Sat, 27 Jul 2002 02:54:22 +0200 From: Jens Schuessler To: cygwin AT cygwin DOT com Subject: Re: Mutt 1.4-1 opens mbox read-only Message-ID: <20020727005422.GA20212@trash.net> Mail-Followup-To: cygwin AT cygwin DOT com References: <20020722202048 DOT GA21538 AT trash DOT net> <20020724123728 DOT GA1556 AT tishler DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020724123728.GA1556@tishler.net> User-Agent: Mutt/1.3.28i X-Cool: get your free UNIX account @ http://www.trash.net/ * Jason Tishler [24-07-02 14:37]: > 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? After building the package again with --enable-external-dotlock, I get the mutt_dotlock.exe and my mboxes are writeable, everythings fine. All mboxes got a "0" on this test. Jens $ diff -u makemutt makemutt.new --- makemutt 2002-07-27 02:44:28.000000000 +0200 +++ makemutt.new 2002-07-25 20:20:20.000000000 +0200 @@ -69,6 +69,7 @@ export MAILPATH=/var/spool/mail OPTS="--with-mailpath=/var/spool/mail --with-regex --enable-pop --enable-imap --enable-locales-fix --with-ssl \ +--enable-external-dotlock \ --enable-buffy-size \ --prefix=/usr \ --sysconfdir=/etc \ -- 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/