On 11-10-16 03:12 PM, RW wrote: > > Not if you set --virtual-config-dir.
Right. But such a change (i.e. a different $HOME on the server than on any other machine) is still on the "transparent to users" change that I am looking for -- the change that requires no user re-training and no increase in help desk calls. It really doesn't seem like it should be so difficult to point spamassassin to a directory structure other than $HOME to find the user_state directories. I'm quite surprised that I am the first person who wants to be able to do this. Or rather achieve this kind of configuration. If in fact there is another way to achieve it than using the --virtual-config-dir than I am open to suggestions. To recap, I simply want to have the user_state (i.e. typically ~/.spamassassin) dirs somewhere other than $HOME on the server but have those dirs and their files owned by their respective users and therefor need to have spamd run as the recipient in order to be able to read (and write in the case of the bayes and autowhitelist, etc. files) them while allowing the users to read/write them also. Is this in fact impossible to do? Cheers, b.
signature.asc
Description: OpenPGP digital signature
