Hello,
I have a setup where my MTA delivers mail to an mbox file, which
then is in turn exported via nfs read only to the client where
mutt is running. Main purpose of this construction is viewing
certain attachments.
While all this works fine the first time mutt is started, after a
while there
On Thu, August 23, 2012 08:53, Joerg Dorchain wrote:
I have a setup where my MTA delivers mail to an mbox file, which
then is in turn exported via nfs read only to the client where
mutt is running. Main purpose of this construction is viewing
certain attachments.
While all this works fine
On Thu, Aug 23, 2012 at 10:28:35AM +0200, Christian Brabandt wrote:
On Thu, August 23, 2012 08:53, Joerg Dorchain wrote:
I have a setup where my MTA delivers mail to an mbox file, which
then is in turn exported via nfs read only to the client where
mutt is running. Main purpose of this
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
On Thu, Aug 23, 2012 at 01:24:40PM +0200, Joerg Dorchain wrote:
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
Hello,
Is there a filter to select threads containing flagged mail?
BTW, i've asked a similar question about finding mails with
text/calendar attachments but the ~b filter is way too slow to be
usable. I only need to change the color of these mails in the index.
I saw the RFC on mutt-dev about
* On 23 Aug 2012, Alexis Letessier wrote:
Hello,
Is there a filter to select threads containing flagged mail?
~(~F)
BTW, i've asked a similar question about finding mails with
text/calendar attachments but the ~b filter is way too slow to be
usable. I only need to change the color of
Hello,
I've been trying to tweak my colour scheme recently, and found some
strange functionality which I don't understand. I'm not sure if it's a
bug or an error in my configuration -- and if it is a bug I don't know
whether it lies in mutt, or s-lang, or my terminal.
The problem is as follows:
