> > Now, I run spamd -d -x -a then spamc -d 127.0.0.1 < sample-spam.txt > > and it comes back without any spam tags (nothing saying OK, nothing > > saying not ok). > > This is a shot in the dark, but I filed bug 245 because if you start > spamd with the -a switch (auto-whitelists), each user that calls spamc > must have a ~/.spamassassin folder or the message doesn't get processed (I > *think* because spamd can't create the auto-whitelist.lock file in that > directory). > > If you don't have that folder create it (mkdir ~/.spamassissin) and see > if that fixes your problem.
I noticed the same problem with a fresh install yesterday, and it doesn't help to create the ~/.spamassassin directory. spamd will create the auto-whitelist.lock just fine, and also the auto-whitelist.db, but still don't tag the messages sent through it. When running spamd in debug mode, it "hangs" on trying to open the auto-whitelist db, and after the default 30 tries it gives up with the message "Cannot open ~/.spamassassin/auto-whitelist: permission denied" or similar. I've tried to set permissions of files and directories without luck. Shouldn't spamd move over to run as myself in this step? (started as root) /Egge _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
