Just for the record, in case it helps anyone else - I found a
workaround to my problem.
The problem is that spamd 3.1.0 insists on trying to create per-user
config files in its user's home directory, even when I tell it not
to, and this causes errors if its user has no home directory. I
On Dec 15, 2005, at 4:50 PM, Matt Kettler wrote:
SpamAssassin tools in general default to creating bayes and AWL
directories
relative to the current user's homedir.
I think this is a bug in SpamAssassin 3.1.0, because it didn't try to
create these directories in 3.0.4, and nothing I do in 3
On Dec 15, 2005, at 4:11 PM, Vivek Khera wrote:
On Dec 15, 2005, at 2:04 PM, Brian Kendig wrote:
I'm running spamd as "spamd -d -x -u nobody", I've commented out
AWL from v310.pre, and I set "bayes_auto_learn 0" so that it
shouldn't try to create a Bay
I'm still not able to figure this out. I can find no reason why
SpamAssassin should be trying to create files in anybody's home
directory, but I'm still seeing this error logged every time spamd
processes a message:
spamd: mkdir /dev/null: File exists at ///Library/Perl/5.8.1/Mail/
Spam
Dec 14 13:27:46 www spamd[3654]: mkdir /dev/null: File exists at ///
Library/Perl/5.8.1/Mail/SpamAssassin.pm line 1467
Dec 14 13:27:46 www spamd[3654]: locker: safe_lock: cannot create
lockfile /dev/null/.spamassassin/auto-whitelist.mutex: Not a
directory
scantime=0.6,size=,user=exim,uid=-2,
On Dec 14, 2005, at 2:52 PM, Theo Van Dinter wrote:
On Wed, Dec 14, 2005 at 01:39:16PM -0500, Brian Kendig wrote:
Dec 14 13:27:46 www spamd[3654]: mkdir /dev/null: File exists at ///
Library/Perl/5.8.1/Mail/SpamAssassin.pm line 1467
Dec 14 13:27:46 www spamd[3654]: locker: safe_lock: cannot
I'm running Exim 4.60 on Mac OS X, and calling SpamAssassin
automatically through SA-Exim (which makes Exim pass mail thru
spamd). SpamAssassin 3.0.4 was running fine, but when I upgraded to
SpamAssassin 3.1.0 (by downloading and compiling the source, after
using CPAN to update all the opt
I'm getting errors when I try to use SpamAssassin 3.0.2 (and the same
errors with 3.0.1), on Mac OS X 10.3.7. Specifically, when I call it
from a command line with no arguments (same as if I give it "-t <
sample-spam.txt"):
$ spamassassin
Global symbol "$re_strict" requires explicit package na