tags 454595 + confirmed - unreproducible
thanks
Hello,
I'm using version 3.3.1-1 and the bug still appends (some times ago, it
worked on etch for sure and maybe lenny):
I currently have the following config:
A dedicated user for spamassassin and a dedicated directory:
mkdir -p /var/lib/spamassassin/users
useradd spamassassin
usermod -d /var/lib/spamassassin spamassassin
chown -R spamassassin. /var/lib/spamassassin
In /etc/default/spamassassin:
ENABLED=1
OPTIONS="--create-prefs -x --max-children 5
--helper-home-dir=/var/lib/spamassassin
--virtual-config-dir=/var/lib/spamassassin/users/%u -u spamassassin"
If I quote the man page of spamd:
--virtual-config-dir: [...] This path must be a writable directory. It
will be created if it does not already exist.
The directory should be created but unfortunately, it's not :/.
Everything works if I create by hand the directory but it's not quite
simple when using virtual users ...
As you suggest, I also tried with
virtual-config-dir=/var/lib/spamassassin/users/%u/spamassassin and
created /var/lib/spamassassin/users/test (with spamassassin as owner)
but spamd doesn't create the folder work neither.
For my test, I used (on the spamd host) the following protocol:
spamc -d 127.0.0.1 -u test <<EOF
From: test
To: test
Subject: test
test
EOF
The mail.log tells me:
# First case
spamd[24346]: spamd: using default config for test:
/var/lib/spamassassin/users/test/user_prefs
# Second case
spamd[2494]: spamd: using default config for test:
/var/lib/spamassassin/users/test/spamassassin/user_prefs
This also make per-users bayes DB unusable (the bayes plugin scream that
it can't create the lock (in the nonexistent folder))
Feel free to contact me if you need further informations.
Regards,
Damien
