hi sidney,
thx for the reply ...
Suggestions:
1) Please ask about configuration problems in the SpamAssassin users
mailing list where people who use the program on different platforms
discuss such things. Use this list for development related things.
tho my track record for getting questions answer on user- has suffered a bit
... fair nuf, i'll 'stay there'. =)
2) The error message says that it can't find the home directory for the
user 'maildaemon', which is the username you specified spamd should run
as. Did you in fact create a user named maildaemon
yes
and if so, did you give it a home directory?
no, purposefully.
i'd (mis?)understood from the docs that by spec'ing @ launch:
spamd ... \
--username=maildaemon \
--daemonize \
--nouser-config \
--siteconfigpath=/path/to/A \
--configpath=/path/to/B \
...
no user-specific data would be used/written, rather into
'configpath/.spamassassin', and therefore no '$home' req'd ...
as i thought using the What does grep maildaemon /etc/passwd show?
as above, no home_dir at the moment ...
3) Even though you tell spamd not to read configuration information from
the home directory, spamd still makes other use of some files in the
home directory.
hmmm ...
is there a spec'n of what particular files are written/used there, rather thatn
in /tmp or config/siteconfig? i've obviously missed it ...
4) spamd is designed to run either as root and then setuid to a user
when it is called to process an email for that user, or else to always
run as the user that you want it to process all email for. I doubt that
you really want it to run as a non-user non-root daemon account, unless
you have carefully thought through the implications and that is what you
want to do. But it will still need its own home directory.
i'd *had* spamd running as root --> setuid (exim user), but was having
permission/lock issues on bayes.mutex that i was trying to resolve ....
sounds like i'm barking up the wrong tree ...
thx 4 the reply!
richard
