Lalo Martins <[EMAIL PROTECTED]> wrote:
>
> Oh, one more tidbit: I _can_ save attachments. Go figure.
That's because attachments are saved to *files*, while messages are
saved to *folders*. So attachments don't require any locking (unless
you're saving a message/rfc822 type, which is a message, but now it's
getting confusing).
Basically, Mutt wants to fcntl-lock the folder, to be safe against
someone else writing to it. Your NFS client is not running the
necessary daemon to coordinate that lock with the server, so it fails,
and Mutt gives up rather than possibly trash your mailbox.
If you are *certain* that every mail-handling program at your site uses
the same dot-locking mechanism, you can reconfigure Mutt with
--disable-fcntl, and then you won't have this problem. But if you're
wrong, and there is some program that does try to perform fcntl-locks as
the only method to prevent synchronization problems, then the two
programs can collide and trash the folder if they access it at the same
time.
Best is to fix the locking problem, as you may have other programs that
want to lock files, too.
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there is no man really clever who has not
Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson
UX WTEC Engineer | PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
