RE: Mutt 1.4-1 opens mbox read-only

RE: Mutt 1.4-1 opens mbox read-only

[Jens Schuessler]

Gary,

I've compiled Mutt now with --enable-dotlock=NO with the original
sources and the patched ones from your site and it works with writable
mboxes as it should.
Packet is available for testing at
http://www.trash.net/~jgs/cygwin/mutt-1.4-1.tar.bz2

Jens

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

Re: Mutt 1.4-1 opens mbox read-only

[Jason Tishler]

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/

Re: Re: Mutt 1.4-1 opens mbox read-only

[Jens Schuessler]

* Jason Tishler <jason@tishler.net> [24-07-02 14:37]:
> 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
> 
> Please try running mutt_dotlock -t on your mbox.  Does it indicate
> incorrect permissions?

Hi Jason,

i would if i could, but there isn't a mutt_dotlock.exe in my
installation or in the official package!? I got a manpage for it, but
no executable. Normally, it should be a part of the mutt-package, or
am i wrong?

Jens

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

Re: Mutt 1.4-1 opens mbox read-only

[Dr. Volker Zell]

>>>>> "Jason" == Jason Tishler <jason@tishler.net> writes:

    Jason> Jens,
    Jason> On Mon, Jul 22, 2002 at 10:20:49PM +0200, Jens Schuessler wrote:
    >> I've compiled Mutt now with --enable-dotlock=NO

    Jason> IMO, the above is a bad idea because you are defeating one of the
    Jason> standard ways to lock a file to prevent corruption if there are multiple
    Jason> writers (e.g., mutt and procmail).

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

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

    Jason> If you get a "5" (instead of "0"), then the permissions of
    Jason> /var/spool/mail are not correct.

    Jason> Please try running mutt_dotlock -t on your mbox.  Does it indicate
    Jason> incorrect permissions?

Where is mutt_dotlock ? There is only a usr/man/man1/mutt_dotlock.1 in
mutt-1.4-1.tar.bz2.

    Jason> Jason

Ciao
  Volker


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

RE: Mutt 1.4-1 opens mbox read-only

[Gary R. Van Sickle]

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

Re: Mutt 1.4-1 opens mbox read-only

[Jason Tishler]

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/

Re: Mutt 1.4-1 opens mbox read-only

[Jens Schuessler]

* Jason Tishler <jason@tishler.net> [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/

Re: Mutt 1.4-1 opens mbox read-only

[Jason Tishler]

Jens,

On Sat, Jul 27, 2002 at 02:54:22AM +0200, Jens Schuessler wrote:
> * Jason Tishler <jason@tishler.net> [24-07-02 14:37]:
> > 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.

I'm glad the mutt is working for you now.  However, it would be nice to
better understand why configuring without --enable-external-dotlock
causes this problem.

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/

RE: Mutt 1.4-1 opens mbox read-only

[Gary R. Van Sickle]

> Jens,
>
> On Sat, Jul 27, 2002 at 02:54:22AM +0200, Jens Schuessler wrote:
> > * Jason Tishler <jason@tishler.net> [24-07-02 14:37]:
> > > 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.
>
> I'm glad the mutt is working for you now.  However, it would be nice to
> better understand why configuring without --enable-external-dotlock
> causes this problem.

Hmmm.  Well, in the interim, I think I'll just rebuild and reissue the package
with --enable-external-dotlock and call that good.

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

Re: Re: Mutt 1.4-1 opens mbox read-only

[Jens Schuessler]

* Jason Tishler <jason@tishler.net> [30-07-02 21:50]:
> Jens,
> 
> On Sat, Jul 27, 2002 at 02:54:22AM +0200, Jens Schuessler wrote:
> > * Jason Tishler <jason@tishler.net> [24-07-02 14:37]:
> > > 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.
> 
> I'm glad the mutt is working for you now.  However, it would be nice to
> better understand why configuring without --enable-external-dotlock
> causes this problem.

I made the mutt_dotlock-test with the official package installed and
echo $? gave me an "0" on all mboxes though they weren't writable by
mutt?! So I dont' know what causes this problem with the internal
dotlock.

Jens

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

RE: Mutt 1.4-1 opens mbox read-only

[Jens Schuessler]

$ ls -l Mail
total 350
drwxr-xr-x   10 horst    544             0 Jul  2 21:42 .
drwxr-xr-x   24 horst    544             0 Feb 20 17:07 ..
drwxr-xr-x    2 horst    544             0 Jun  6 19:04 Cygwin
drwxr-xr-x    2 horst    544             0 Jul  2 21:41 Debian
drwxr-xr-x    2 horst    544             0 May 29 03:13 Indymedia
drwxr-xr-x    2 horst    544             0 May 29 03:13 Linux
drwxr-xr-x    2 horst    544             0 May 29 03:13 Security
drwxr-xr-x    2 horst    544             0 Jun 20 19:40 TrashNet
-rw-r--r--    1 horst    544         69209 Jul 12 18:32 cpr
-rw-r--r--    1 horst    544        287746 Jul 17 00:50 mbox
-rw-r--r--    1 horst    544             0 Jun  6 00:40 muell
drwxr-xr-x    2 horst    544             0 Jun 29 00:12 sent
drwxr-xr-x    2 horst    544             0 Jul  2 21:40 sge
-rw-r--r--    1 horst    544             0 Jul 17 00:50 spamblock

All mailboxes are on 644.

Jens

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

Re: Mutt 1.4-1 opens mbox read-only

[news]

On 11 Jul 2002, Jens Schuessler <jgs@trash.net> wrote:

> Can anyone
> reproduce this problem? Im running cygwin on W98.

For me also. If you did something incorrectly then so did I.

_______________________________________________________
The FREE service that prevents junk email http://www.mailshell.com

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

RE: Mutt 1.4-1 opens mbox read-only

[Gary R. Van Sickle]

> On 11 Jul 2002, Jens Schuessler <jgs@trash.net> wrote:
>
> > Can anyone
> > reproduce this problem? Im running cygwin on W98.
>
> For me also.

On Win98?

> If you did something incorrectly then so did I.
>

Uncool.  I see nothing of the sort on XP, and I have no Win98 machine to test
on.  Can you guys give me an "ls -l" of your mail directory?

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

Re: Mutt 1.4-1 opens mbox read-only

[Charles Krug]

On Tue, Jul 16, 2002 at 12:12:59AM -0500, Gary R. Van Sickle wrote:
> > On 11 Jul 2002, Jens Schuessler <jgs@trash.net> wrote:
> >
> > > Can anyone
> > > reproduce this problem? Im running cygwin on W98.
> >
> > For me also.
> 
> On Win98?
> 
> > If you did something incorrectly then so did I.
> >
> 
> Uncool.  I see nothing of the sort on XP, and I have no Win98 machine to test
> on.  Can you guys give me an "ls -l" of your mail directory?
> 

I have the same thing on Win95.  My mail directory shows permissions to
be 766.

This worked correctly until the version spin.  Did dotlock change to
break Win95?


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

Mutt 1.4-1 opens mbox read-only

[Jens Schuessler]

I just installed the new mutt-package and mutt opens my mailfolders
only in read-only mode, so i downgraded it to 1.2.5i and everything
works as it should. Can anyone reproduce this problem?
Im running cygwin on W98.

Jens

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