As I understand it, permissions are like RWX , RWX , RWX Owner, GroupOfOwner, RestofWorld
So if all users are in the same group, say 'users', then you could do : chmod 660 /var/spool/mail/SPAM to change the permisions on the folder so only group members and the owner can read/write to the folder chgrp -R users /var/spool/mail/SPAM to ensure the group of the folder and it's contents are set to the 'user' group However, the executable flag also used to indicate whether or not people are allowed to change to that directory. So if the above doesn't work, try chmod 770 /var/spool/mail/SPAM chgrp -R users /var/spool/mail/SPAM Which would be slightly safer by dissalowing the rest of the world from writing to the directory in question Wez On Wednesday 03 Jul 2002 10:57 pm, Anthony Hologounis wrote: > Let me ask, so this is the best way to handle spam? > > Righ tnow I have a folder called /var/spool/mail/SPAM that has 666 > permissions. I think this is dangerous but I want to be able to collect all > of the spam in one folder. > So I can see how well my procmail/spamassassin settigns are working. > > If there is another way of doing this thenenlightenme.... > > Cheers! > > Anthony > > >The problem, I think, is that you're trying to have each user's account > >write the spam to /var/spool/mail/caughtspam. > > > >Only one user can own that file, and if it's not been set with permissions > >to allow world to write to it, they won't be able to. > > > >Hence the reason I filter it to "$HOME/mail/caughtspam"...it's going to > >the user's own subdirectory, off of their own home directory, where > >they'll have permission to write. > > _______________________________________________ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
