On Thu, Aug 23, 2012 at 11:39:25AM +0200, Joerg Dorchain wrote: > > If just seems that mutt does not check for new mails at all when > it considers a mailbox read only.
I need to correct myself: With an strace, I see that mutt does a
stat() on the mbox file with every keypress while in the index
screen, the stat() returns the proper size and times.
However, it then forks the mutt_dotlock process, which fails
because it the filesystem with the mbox is readonly.
The source from mbox.c reads
if (mbox_lock_mailbox (ctx, 0, 0) == -1)
{
mutt_unblock_signals ();
/* we couldn't lock the mailbox, but nothing serious happened:
* probably the new mail arrived: no reason to wait till we can
* parse it: we'll get it on the next pass
*/
return (M_LOCKED);
}
Needless to say the assumption expressed in the comments does not
hold.
Would this finding justify a bug report?
A solution might be to add a special case for following readonly
mailboxes (both read only file and file on read only filesystem),
The rest of the logic in the check_mailbox function is correct
here.
The current workaround of exiting and restarting mutt seems quite
cumbersome to me.
Bye,
Joerg
signature.asc
Description: Digital signature
