Craig McLean wrote: > Don, some thoughts inline.. > > Don Levey wrote:
>> >>> From what I see now, this is because if root is running it then the >>> user >> shifts to 'nobody'. This is damn inconvenient. So, I've tried to >> shift to >> using user 'spamassassin' by using the "-u spamassassin" switch on >> both >> spamd and spamass-milter. When I do this, though, I can't actually >> read the >> user_prefs file for user root. But why am I even trying to open it >> for root, >> when spamassassin is the UID? > > Why not combine the user_prefs and the local.cf, and move the > whitelist somewhere where 'spamassassin' user can read/write to it? > The latest in my quest to get SA to work properly... I've made sure that the whitelist and Bayes DB can be written to and be read by 'spamassassin'. I've set the '-u spamassassin' flag for both the /etc/sysconfig/spamassassin and /etc/sysconfig/spamass-milter startup files. I've restarted spamd, spamass-milter, and sendmail. My ps list shows that 'spamassassin' is running spamd, and 'root' is running spamass-milter. In my maillog file, I am getting errors: * for 'named' accounts, spamd can't find the user_prefs file * for 'aliased' accounts, spamd can't find the username. I know that I can solve the latter by putting the '-x' flag on the spamass-milter startup line. Do I need to worry about the former? That is, am I causing any problems by running this way, or am I simply now set up so that I can run user-specific rules in addition to the site-wide ones? -Don p.s. In case it wasn't clear, SpamAssassin really rocks! I don't want my current frustration to get in the way of the appreciation and adulation the developers deserve.
