Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 25 Jul 2002 10:30:07 -0400 From: Jason Tishler Subject: Re: Mutt 1.4-1 opens mbox read-only In-reply-to: To: cygwin@cygwin.com Mail-followup-to: cygwin@cygwin.com Message-id: <20020725143007.GA2092@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: <20020724123728.GA1556@tishler.net> Gary, On Wed, Jul 24, 2002 at 10:29:55PM -0500, Gary R. Van Sickle wrote: > > 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? Until I installed exim, /var/spool/mail was owned and writable by me: $ ls -dl /var/spool/mail drwxr-xr-t 2 jt Domain U 4096 Jul 25 10:01 /var/spool/mail After installing exim, I changed the ownership and permissions to: $ chown exim:mail /var/spool/mail $ ls -dl /var/spool/mail drwxrwxr-t 2 exim mail 4096 Jul 25 10:01 /var/spool/mail With the above permissions mutt could not dotlock files in /var/spool/mail and opened my inbox read-only. When I opened up permissions (i.e., added other writable): $ chmod o+w /var/spool/mail $ ls -dl /var/spool/mail drwxrwxrwt 2 exim mail 4096 Jul 25 10:01 /var/spool/mail mutt became "happy" and opened my inbox read/write. 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/