[Prev][Next][Index][Thread]
Re: weird pine message
Alexandre Khalil <iskandar@EESUN2.tamu.edu> wrote:
|On Thu, 19 Dec 1996, Ira Abramov wrote:
|
|>[Error creating /var/spool/mail/ira.lock.850999139.6405.ard: Permission
|>denied]
|
| You could allow the same permissions on /var/spool/mail as on /tmp,
|that is 1777
|
|#ls -ld /var/spool/mail
|drwxr-xr-t 3 root mail 2048 Dec 6 12:25 /var/spool/mail/
|
|# chmod 1777 /var/spool/mail
|
|#ls -ld /var/spool/mail
|drwxrwxrwt 3 root mail 2048 Dec 6 12:25 /var/spool/mail/
|
| Otherwise, you might have to recompile pine to have it create the lock
|file in /tmp.
|
| Over here, we preferred the first solution because popper and some
|odd-ball mailers also put lock files in the mail directory. Also, the
|users can recreate their mailbox should anything happen to the original
|one. Yes, quota is turned on on the mail partition.
I assume you suggest this so the sticky bit will prevent people from
touching other people's mailboxes. But what about the following
scenario:
1. user A doesn't have a mailbox
2. user B does "touch /var/spool/mail/A"
3. user A recieved mail.
Won't user B be able to read user A's mail?
If I got it right, Debian solved the problem by making /var/spool/mail
group-writable to the "mail" group, and making all the right processes
belong to that group (e.g. in.pop3d).
Cheers,
--Amos
--Amos Shapira | "Of course Australia was marked for
133 Shlomo Ben-Yosef st. | glory, for its people had been chosen
Jerusalem 93 805 | by the finest judges in England."
ISRAEL amos@dsi.co.il | -- Anonymous
Follow-Ups:
References: