David T-G proclaimed on mutt-users that:
> Are you sure that shouldn't be 2775 instead? I don't think we need
> stickiness, but to ensure that only root and mail can write in there...
Not the mailboxes - the directory /var/spool/mail/ ...
From the pine 4.21 docs ...
In installations like mine where people run both mutt and pine 4.21, this is
needed .
What Systems Managers Need to Know about Pine File Locking
There is an extensive section on locking in the Pine technical notes;
this information is intended to provide answers to some common questions:
1. Why did locking change in Pine 4.00? The actual locking mechanisms did
not change in 4.00. What changed is that when one particular locking
mechanism used by Pine fails, Pine now issues a warning message. Prior to
4.00, the locking failure would occur, but no warning was issued.
2. Is this what the "Mailbox vulnerable" message is about? Yes. It means
that Pine was unable to create a lockfile in the spool directory, generally
because of overly restrictive protections on the spool directory. The correct
permissions on the spool directory for running Pine are 1777, i.e.
read-write-execute permission for everyone, with the sticky-bit set, so only
owners of a file can delete them.
--
Suresh Ramasubramanian + Wallopus Malletus Indigenensis
mallet @ cluestick.org + Lumber Cartel of India, tinlcI
Be valiant, but not too venturous.
Let thy attire be comely, but not costly.
-- John Lyly
