Is mutt_dotlock supposed to be setgid (sorry Mikko, I meant setgid
nor setuid in other message)? I changed it to 755 and I still get
read-only permission on /var/spool/mail/vdanen which has -rw-rw
permissions and is owned by vdanen.mail.
I can't delete any messages in my inbox with the new
mutt_dotlock setgid mail.
I wrote a moment ago:
Dotlocking will create a file /var/spool/mail/vdanen.lock.
In order to do this, mutt_dotlock needs write access to
that directory, which is normally enabled by making
mutt_dotlock setgid mail.
To illustrate things, here's an example from my system:
% ls -ld /var/spool
On Tue, Jun 20, 2000 at 10:43:52PM +0200, Thomas Roessler wrote:
Dotlocking will create a file /var/spool/mail/vdanen.lock.
In order to do this, mutt_dotlock needs write access to
that directory, which is normally enabled by making
mutt_dotlock setgid mail.
To illustrate things
On Tue, Jun 20, 2000 at 03:08:14PM -0500, Aaron Schrab wrote:
Is mutt_dotlock supposed to be setgid (sorry Mikko, I meant setgid
Yes, it needs to be setgid to the group that owns the mail spool
directory. That's the whole point of it. Dotlocking in some
configurations needs to be
, not of the _file_ in that
directory
Dotlocking will create a file /var/spool/mail/vdanen.lock.
In order to do this, mutt_dotlock needs write access to
that directory, which is normally enabled by making
mutt_dotlock setgid mail.
Ok, but the permissions seem to be fine for that directory
