On Tue, Sep 24, 2002 at 03:43:29PM -0700, Cheryl L. Southard wrote: > However, I still think that spamd should be able to setuid to the > user by itself. According to the man page for spamd: > -u username, --username=username > Run as the named user. The alternative, default > behaviour is to setuid() to the user running "spamc", if > "spamd" is running as root. > So the default behavior should be to setuid to the user receiving the e-mail.
If DROPPRIVS=yes is NOT SET, procmail runs spamc as root. Therefore, spamd doesn't know what user is running spamc and can't setuid to it. > And when I change my /etc/procmailrc file to use "spamassassin -P" instead > of spamc, then it works fine and uses my user_prefs file. I guess > something is strange with spamc/spamd. The difference is IIRC, spamassassin uses the $HOME env variable to determine the location of the user_prefs, which procmail most likely leaves. Spamc does not pass the $HOME variable to spamd, and spamd is forced to take the default for the user spamc is running as, so it chooses /root/spamassassin/user_prefs. -- Duncan Findlay ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
