Tolga wrote Monday, October 01, 2007 12:11 PM:
[Dallman Ross wrote:[1]]
I am not a sysadmin, so don't state the following with
absolute authority. But I would use at least 755 for /var/log/
and make sure the procmail.log therein is at least 644.
Or if it's not the owner doing the writing to the file,
then 666 or something minimally required for the user who
writes to the file.
/var/log/ is already 755 and procmail.log is already 644.
Yes, and that is the problem, as you made clear enough in a
follow-up when you stated that the failed writes were coming
from users' .procmailrcs, not the /etc/procmailrc. Thus we
have a case of a non-privileged user trying to write to a
file where he only has read permissions. I detailed that
possibility in the part of my message you didn't quote.
But I didn't know for sure at the time what your situation
was. Since you have meanwhile confirmed that to be the case,
we now can see that is the source of your trouble.
A nonprivileged user will not be able to write to a file
not owned by him chmodded to 644. You would need at least
646.
[1] You are deleting attributions of who said what you quote.
Please do not do that.
Dallman
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail