Dennis Hammer <[EMAIL PROTECTED]> wrote:
>
> I've got a seemingly major problem with my spoolfile. The permissions
> are 600 and the file belongs to me, but mutt just keeps telling me
> that the mailbox is readonly.
The mutt_dotlock program needs permission to create a dot-lock file in
the mail spool directory. That means that the directory must be
writable in some way. THE PARENT DIRECTORY of your spool file. The
permissions of your spool file itself don't affect how it can be locked.
Mutt is supposed to examine the permissions of your spool directory and
react accordingly. If the permissions are 1777, then mutt_dotlock needs
no extra permissions. If the permissions are 775, then mutt_dotlock
needs to be owned by the same group that owns the spool directory, and
needs to be setgid. If the permissions are 755 or worse, then there is
no recourse; mutt_dotlock shouldn't be installed or used for locking.
This is really getting to be a FAQ around here. Why is this happening?
Did someone package up an RPM that just blithely assumes it knows what
locking method is supposed to be applied on everyone's system?
> When I use pine, there are no problems.
There are two possibilities: 1. Pine is installed incorrectly and is
failing to lock your spool file in a way that prevents other programs
from corrupting it. 2. Pine is doing everything correctly, and Mutt is
trying to lock the spool in a way that's not possible, or necessary.
--
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
