ok, I tried setting /root/.spamassassin/* including subdirs as rw by ALL and setting thier group membership to 'mail' (same as my mail user who spamd is running as) still get:
Mar 19 11:56:08 bacon spamd[22447]: connection from localhost [ 127.0.0.1 ] at port 45093 Mar 19 11:56:08 bacon spamd[23808]: Creating default_prefs [/root/.spamassassin/user_prefs] Mar 19 11:56:08 bacon spamd[23808]: Couldn't create readable default_prefs for [/root/.spamassassin/user_prefs] Mar 19 11:56:08 bacon spamd[23808]: clean message (0/5) for root:8 in 0 seconds. Ed Kasky wrote: > I would check the permissions on /root/.spamassassin/user_prefs and be > sure it's writable by the user you are running spamd as. Wether as > owner or a group membership. I like to use "wheel" for situations > like this and assign users that I trust to the group. > > Ed > ~~ > At 10:20 AM Tuesday, 3/19/2002, you wrote -=> > >> ok, so I added "-u mail" for spamd's startup and now have this in my >> main log: >> >> Mar 19 10:20:27 bacon spamd[22447]: connection from localhost [ >> 127.0.0.1 ] at port 44544 >> Mar 19 10:20:27 bacon spamd[22490]: Creating default_prefs >> [/root/.spamassassin/user_prefs] >> Mar 19 10:20:27 bacon spamd[22490]: Couldn't create readable >> default_prefs for [/root/.spamassassin/user_prefs] >> >> which seems like it's trying to create files in the root home which >> it obviously can't running as a non-root user. >> >> And I get this in my procmail log: >> >> procmail: Executing "spamc" >> procmail: [22456] Tue Mar 19 10:19:46 2002 >> procmail: Assigning >> >"PATH=/home/jjbacon/bin:/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/X11R6/bin" >> >> >> If it's not running as root, isn't it supposed to use some global prefs? >> >> --- FROM spamd.README ----------- >> >> If you do not need to let your users define their own rules, maintain >> their own >> whitelists, or have non-world-readable home and ~/.spamassassin >> directories, >> then just set spamd up to run with the "-u username" option. Since >> spamd can >> use auto-whitelisting, which requires it maintain a database of email >> addresses >> on-disk, you should use a non-"root" but non-"nobody" user: >> "mailnull" or" >> "mail" are good choices, or even create a "spamd" user. >> >> --------------------------------- >> >> BTW, thanks for all your help. >> >> Ed Kasky wrote: >> >>> A coupe of things to try: >>> >>> Add the following to the top of your .procmailrc >>> >>> # set to yes when debugging >>> VERBOSE=yes >>> # Remove ## when debugging. Set to no if you want minimal debugging >>> LOGABSTRACT=all >>> LOGFILE=/var/log/procmail/procmaillog.`date +%m-%d-%y` >>> >>> The location of your logs is up to you - just be sure to set the >>> privelages according to the user owning the process. >>> >>> >>> >>> At 11:32 PM Monday, 3/18/2002, you wrote -=> >>> >>>> Mar 18 22:01:01 bacon spamd[8224]: connection from localhost [ >>>> 127.0.0.1 ] at port 36584 >>>> Mar 18 22:01:01 bacon spamd[9258]: Still running as root: user not >>>> specified, not found, or set to root. Fall back to nobody. >>> >>> >>> >>> This seems to be telling you there's an error with the user that >>> owns the spamd process. Read the security section at >>> http://spamassassin.org/dist/spamd/README.spamd and see if that >>> helps running as a different user. >>> >>> Ed >>> Ed Kasky >>> Los Angeles, CA >>> . . . . . . . . >>> What we anticipate seldom occurs; >>> what we least expect generally happens. >>> --Benjamin Disraeli >> >> >> >> >> >> _______________________________________________ >> Spamassassin-talk mailing list >> [EMAIL PROTECTED] >> https://lists.sourceforge.net/lists/listinfo/spamassassin-talk > > > Ed Kasky > Los Angeles, CA > . . . . . . . . > Experience is knowing a lot of things you shouldn't do. _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
