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
Wrong owner of some rspamd config files #5864
Labels
Comments
You are able to change such files via mailcow interface, but when you change the owner you won't able to do that anymore I guess |
But I can't edit them in the rspamd UI. I think it'd be better to set ACL for rspamd as well so that both users can edit them. Or run rspamd as the same user. Or set the owner/mod only for the files that can be changed in mailcow UI, not all of them. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Contribution guidelines
I've found a bug and checked that ...
Description
In
mailcow-dockerized/data/Dockerfiles/rspamd/docker-entrypoint.sh
Line 116 in 36b5ccc
If I chown them to 101:101 (the user that rspamd runs as) the files become available for editing and save normally. However, since this 82:82 chown is in the entrypoint script, restarting rspamd causes the files to become read only again. I'm not sure if it's some design decision I don't understand or a bug but it's pretty inconvenient because it becomes impossible to change the white/blacklists from the UI without changing the access rights via ssh first. The behavior is exactly the same on two separate instances I maintain (work and personal servers).
Logs:
Steps to reproduce:
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Debian 12.5
Server/VM specifications:
VDS, 8 GB RAM, 4 CPUs
Is Apparmor, SELinux or similar active?
Apparmor is active
Virtualization technology:
KVM
Docker version:
20.10.24+dfsg1
docker-compose version or docker compose version:
v2.26.1
mailcow version:
2024-04
Reverse proxy:
Caddy
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check:
The text was updated successfully, but these errors were encountered: