Repository navigation
Feature request: JSON config format #548
Description
Use case
Maddy's uses a custom config format. This makes it hard to integrate maddy with solutions for automatic configuration management (both generating maddy config or parsing maddy config). NixOS for example can very easily generate JSON from it's structured module system, but it is much harder to generate the current maddy config format in a meaningful way from nix.
Your idea for a solution
I propose to introduce a canonical JSON representation of the configuration and a way to convert from the current configuration format to the JSON format (similar to how Caddy uses the human readable Caddyfile format and a machine readable JSON format). This also makes it easier to write various adapters that can translate from other mailserver config (e.g. dovecot) to the equivalent maddy config on a best effort basis (similar to how Caddy has adapters e.g. for nginx).
- I'm willing to help with the implementation
Activity
vtolstov commentedon Oct 28, 2022
I'm not agree with json. Yaml more suitable for config file
Sohalt commentedon Oct 28, 2022
The goal is not to write JSON by hand, but to have a widely used format that's easy to parse and generate from various tools to build automation around maddy config. Also since YAML is a superset of JSON, any valid JSON is also valid YAML (but not the other way around).
foxcpp commentedon Oct 28, 2026
That would require major refactoring for 2 reasons:
I already plan to do 2 to reduce amount of ugly configuration reading code. I will keep this open with
blocked- when such refactoring is completed, we can go back to considering JSON config as an alternative format.