On Mon, Apr 16, 2001 at 12:24:34AM -0500, Tim Legant wrote:
> Yes and no. Mutt has to be compiled with the correct options to do it.
> Assuming you're on a system where qmail uses flock (not HP/UX or
> Solaris), configure mutt with --enable-flock. Then they're both talking
> the same language.
Th
On Mon, Apr 16, 2001 at 04:03:45AM +, Jim Breton wrote:
> On Sun, Apr 15, 2001 at 02:11:46PM -0500, Tim Legant wrote:
> > It's a maildir feature that this can't ever happen.
> >
> > It's a mbox "feature" that you have to use locking to prevent it from
> > happening.
>
> Lol.. yep.
>
> This
On Sun, Apr 15, 2001 at 02:11:46PM -0500, Tim Legant wrote:
> It's a maildir feature that this can't ever happen.
>
> It's a mbox "feature" that you have to use locking to prevent it from
> happening.
Lol.. yep.
This is occurring with regular mailboxes. I would have expected Mutt to
do that lo
On Sun, Apr 15, 2001 at 12:26:10PM +0200, Andre Berger wrote:
> * Jim Breton <[EMAIL PROTECTED]>, 2001-04-15 11:39 +0200:
> > Something I've been noticing is that if my MDA (qmail-local from qmail
> > 1.03) writes a new message to a mailbox while Mutt (1.2.5i) is in the
> > process of opening that
* Jim Breton <[EMAIL PROTECTED]>, 2001-04-15 11:39 +0200:
> Something I've been noticing is that if my MDA (qmail-local from qmail
> 1.03) writes a new message to a mailbox while Mutt (1.2.5i) is in the
> process of opening that mailbox, I will end up with two exact copies of
> that message in the