Gene Heskett wrote: > [EMAIL PROTECTED] .spamassassin]# su spamd > [EMAIL PROTECTED] .spamassassin]$ ls > ls: .: Permission denied > [EMAIL PROTECTED] .spamassassin]$ pwd > /home/spamd/.spamassassin > > >>Fortunately unix is protecting you from yourself here. Your effort >>to give spamd rights to /root/.spammassassin is foolish and outright >>dangerous. > > > No doubt, but I'm just trying to figure out two things. > 1. Why won't spamd run as the user spamd > 2. Why can't the user spamd see, read or write to his own home dir?
well, who owns /home/spamd? What are it's rights? who owns /home/spamd/.spamassassin? what are it's rights? Since you can't ls the directory, for some reason spamd doesn't have the X right to the .spamassassin directory. That's bad. Directories should be rwx to their owners. > > >>Since spamd has no rights to /root, it can't read >>/root/.spamassassin. But stop trying to give spamd any rights to >>root's homedir. It's a dangerous game. You really don't want it to >>have any rights to these files. >> >>Make sure the spamd user has it's OWN homedir in /home/spamd, or some >>such thing. > > > It does, and its contents are now a copy of /etc/mail/spamassassin, as > follows: *Why* is it a copy of /etc/mail/spamassassin??!!! There should be NO .cf files in a .spamassassin dir. Only user_prefs, bayes files and autowhitelist files. Nothing else will be used by SA in this directory, so anything else that's here is mis-placed. > Well, I was gonna show you, but while root can see all of it, spamd is > effectively blind, see above. >
