Hi Maxim,
I've just discovered something strange: I wanted to change my SA config to use AWL instead of TxRep for some reason. Therefore I've modified the SA config and restarted spampd.
Then when checking the homedir of spampd, I found these two new files being owned by root
/var/spool/spampd/auto-whitelist
/var/spool/spampd/auto-whitelist.mutex
Of course this didn't work and I had to manually change ownership of the files to spampd to make it work.
This happens when starting spampd like so as root: spampd --user=spampd --group=spampd...
I guess that there is something initializing SA on startup before the UID/GID change happens.
If there is an easy fix I'd like to fix it, otherwise it's not really a deal breaker. Any ideas where exactly it goes wrong?
Thanks,
Simon
Hi Maxim,
I've just discovered something strange: I wanted to change my SA config to use AWL instead of TxRep for some reason. Therefore I've modified the SA config and restarted spampd.
Then when checking the homedir of spampd, I found these two new files being owned by root
Of course this didn't work and I had to manually change ownership of the files to spampd to make it work.
This happens when starting spampd like so as root:
spampd --user=spampd --group=spampd...I guess that there is something initializing SA on startup before the UID/GID change happens.
If there is an easy fix I'd like to fix it, otherwise it's not really a deal breaker. Any ideas where exactly it goes wrong?
Thanks,
Simon