On Mon, May 29, 2006 at 07:20:31PM -0400, Daryl C. W. O'Shea wrote:
>On 5/29/2006 5:20 PM, George Georgalis wrote:
>>Looking at this block from above SpamAssassin.pm line 1469,
>>it's not clear to me how to avoid the warning/errors listed below.
>>
>>note: I'm doing active (in smtp) filtering, and I do not want to
>>create a .spamassassin directory.
>
>You don't say how, but only when, you're calling SpamAssassin, so who knows.
I was looking for a config option to disable it because SA is
running as a user with no home directory. It's being called like
this
score=$(cat "$tmp" | spamc -x -c) ; testexit=$?
opinion="X-spamc: ${score} ${TCPREMOTEIP}; ${host} ($now)"
case $testexit in
0) pass ;; # ham
1) fail ;; # spam
*) warn ;; # spamc error
esac
>Why doesn't qmail (I assume that is the user SA is running as) have
>rights to create a directory and files in that path?
SA is running as qmaild, which is the UID that handles the port 25
socket. exactly what it can write to is very limited for security.
>You need at least one userstate directory for the qmail user if you're
>going to use disk based auto-whitelists, etc.
I've disabled auto-whitelists in the config, and I don't want any
of the features that require $HOME/.spamassassin -- I just cannot
figure out a good way to make it stop attempting to create the dir.
// George
--
George Georgalis, systems architect, administrator <IXOYE><
http://galis.org/ cell:646-331-2027 mailto:[EMAIL PROTECTED]
