Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

auto-whitelist ended up being owned by root #40

Open
realsimix opened this issue Feb 10, 2023 · 0 comments
Open

auto-whitelist ended up being owned by root #40

realsimix opened this issue Feb 10, 2023 · 0 comments

Comments

@realsimix
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant