chore(Amavis): only add configuration to Postfix when enabled#3046
chore(Amavis): only add configuration to Postfix when enabled#3046georglauterbach merged 6 commits intomasterfrom
Conversation
Since I am running Rspamd nowadays, I noticed there still are ports open that belong to Amavis. This is because the Amavis configuration is a fixed part of Postfix's `master.cf`. I changed that. Now, the Amavis section is added when Amavis really is enabled. I took the chance and added proper indentation to `master.cf`; hence the diff is a bit fuzzy. **But**, only the Amavis part was adjusted, the rest is just styling.
polarathene
left a comment
There was a problem hiding this comment.
Not really sure about storing the config in /etc/amavis within the container, but otherwise no other concerns 👍
Might be worth doing similar for the other 3 additions we have, but these are all default and not configurable I think. pickup in particular is modifying the original pickup config.
If I get around to refactoring the relay feature support, it'd be taking a similar approach to this Amavis appending. So I'm a bit more swayed towards a common location in the container (/etc/dms/postfix/master.d?)
|
I updated the file location inside the container (to |
|
@georglauterbach I noticed this: docker-mailserver/target/postfix/main.cf Lines 88 to 89 in 9e9f802 It's removed if docker-mailserver/target/scripts/startup/setup-stack.sh Lines 73 to 82 in 9e9f802 |
* improve Amavis setup routine see #3046 (comment)
Description
Since I am running Rspamd nowadays, I noticed there still are ports open that belong to Amavis. This is because the Amavis configuration is a fixed part of Postfix's
master.cf. I changed that. Now, the Amavis section is added when Amavis really is enabled.I took the chance and added proper indentation to
master.cf; hence the diff is a bit fuzzy. But, only the Amavis part was adjusted, the rest is just styling.Type of change
Checklist:
docs/)