Hi KumoMTA Team , I’m very grateful to have such an excellent product.
I have a question. I’m a Momentum user, and we have a cluster deployment. Momentum provides the SVN synchronization function. We can use the version control (SVN) function to make edits in a customized web system and synchronize them to Momentum for effect after review. I’d like to ask if KumoMTA has a similar function? Or KumoMTA has Web UI to manage queue, source ,ip pool ? thanks
Back when Momentum was made there was not the diversity of config management tools that there are today, so SVN was directly implemented. This was also needed because Momentum didn’t use lazy loading and cacheing of config and needed a config reload on config change.
As KumoMTA is much more modern, we didn’t want to lock users into any given approach, and so we leave it to the user to select the configuration management system that works for them.
Thank you for your reply. May I ask what configuration management systems are currently recommended? It can be for the email industry or other industries. For example, if we are familiar with Java development, SpringCloud config Eureka is a good choice. As far as I know, Kumomta focuses on email sending. Are there any articles introducing its peripherals, such as using haproxy or nginx for email inbound and using prometheus for monitoring?
For now our focus is on documenting KumoMTA itself, but there’s plans to expand things to cover what goes around KumoMTA. We generally use Git for our test servers, and because it’s config as code you can do things like database or API queries to get configuration data. For that matter you could keep things as simple as using rsync, it’s really quite flexible.
OK. Around KumoMTA is really great. Sometimes when we do POC and recommend tools to the company, if we tell the boss that the tool itself is very powerful, but the learning curve is very steep and there are no peripheral facilities for some best practices, it will largely hinder the process of replacing the existing software.
I’m quite interested in the git approach. I’ll study it later.
I currently deploy KumoMTA configs using ansible to the servers… And then actually the ansible code is in git. So it depends how you want to appreach the configuration. If you wanna do it from a generic server deployment standpoint or only do it for the KumoMTA configuration.
Both ways are fine, but for me ansible was the way to deploy stuff on servers anyway, which made the ansible deploy route pretty obvious.