On Wed, 2004-02-25 at 00:32, David Purton wrote: > On Tue, Feb 24, 2004 at 11:03:49PM -0500, David Clymer wrote: > > On Tue, 2004-02-24 at 19:43, David Purton wrote: > > > On Wed, Feb 25, 2004 at 11:04:58AM +1030, David Purton wrote: > > > > On Tue, Feb 24, 2004 at 07:04:27PM -0500, Stephen wrote: > > > > > On Tue, Feb 24, 2004 at 04:40:44PM +1030 or thereabouts, David Purton wrote: > > > > > > I set up sa-exim over the weekend and it works nicely, but... > > > > > > > > > > <snip> > > > > > > > > > > > I can't even find where the daemon stores the whitelist database to > > > > > > delete file :( > > [snip] > > > > > > > > > > > Woohoo - thankyou > > > > > > Any ideas where it was storing this stff before? > > > > > > dc > > > > > > > I believe that spamassassin stores whitelists, bayesian tokens, etc in > > the home directory of the user that it runs as. This allows you to have > > spamd do filtering based on data specific to each user. > > > > If you are running spamd, check the /root/ directory for your missing > > whitelists or other data. If I remember correctly, spamd runs as root > > initially, then switches to the user which is requesting a scan (either > > the user spamc is run as, or as specified like so: spamc -u bob). If the > > user doesnt exist, it falls back to nobody. > > So in the case of sa-exim - I assume spamc is run as user Debian-exim, > right? >
> Debian-exim of course has no home directory - so where would shere > would it have been puuting said files? > If you run spamd with the -D or --debug option you should be able to see what user it runs as (as well as a bunch of other things) in syslog. Perhaps that will include some info about what files it is writing to as well. > It is definitely not putting them anywhere in /root > Of course not...I'm not sure where I came up with that. At some point I remember fooling with my spamd config and having those end up in /root, but I'm pretty sure thats not the default, so strike my original comment on that :) I'm kinda working from memory, since I don't have access to the machine that I had this set up on. Hopefully I can remember something you find useful. -davidc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
