* jochen issing <[EMAIL PROTECTED]> [2002-09-26 09:44 +0200]: > On Wed, Sep 25, 2002 at 06:47:01PM +0200, Sven Guckes wrote: > > * jochen issing <[EMAIL PROTECTED]> [2002-09-25 16:25]: > > > > after my recent update to 1.4i, I am not able able to remove any mails > > > > out of my spool files. I can open /var/mail/jochen with vim and can > > > > write it, but mutt refuses writing.
Because vim does not create a lockfile. > > > Ah, I have solved the Problem!! > > > It was the directory access to /var/mail, which was rwxrwxr-x > > > and I have been "other". Hence, I actually was not able to write > > > into the directory. I find it quite interesting that mutt 1.4i > > > has a problem with it and vim and my old mutt (1.3.28?) not. Either the old mutt or the old mutt_dotlock binary were setgid mail. > no, its owned by root,root. There are no suid bits set as > for vim and I changed permission of the directory and everything > works fine. If there are other users on your machine, your created a security hole by this. Nicolas
