amavis: fix config permission#1435
Merged
erik-wramner merged 1 commit intodocker-mailserver:masterfrom Apr 5, 2020
Drakulix:master
Merged
amavis: fix config permission#1435erik-wramner merged 1 commit intodocker-mailserver:masterfrom Drakulix:master
erik-wramner merged 1 commit intodocker-mailserver:masterfrom
Drakulix:master
Conversation
Contributor
|
The tests say they haven't completed but in Travis they are green. I'll merge this anyway. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When running docker-mailserver in podman (which works nicely otherwise), I am getting this warning from amavis in my log:
It then restarts over and over. From what I gathered, the file should be read-only.
So doing
podman exec mail.service chmod 444 /etc/amavis/conf.d/61-dms_auto_generatedinstantly fixed the problem and the server starts up without a problem.From that I created this quick patch, which should hopefully fix this issue.
I have no idea, if this is a podman-specific thing or if it also happens in docker. But I guess it cannot cause any issues for docker installs.