Kinda the same as #1110. I'd like to enable mailserver administrator to configure accounts/aliases from web interface like postfixadmin (docker link)
Reason - mailserver administrators don't want to SSH to the server and run the scripts every time they need something
Would be great either to have it integrated out-of-the box or have some manual how to add it to existing docker-compose
Postfixadmin is a great way to manage users, aliases and domains. You got my vote!
Postfixadmin requires a database and this image is not using any SQL.
Web interfaces tend to increase the surface attack for potential vulnerabilities (XSS, bruteforce, RCE etc. https://www.cvedetails.com/product/27345/Postfix-Admin-Project-Postfix-Admin.html?vendor_id=13213)
That said, you can tweak this image to your needs, setup postfix with a database (some users already done that; https://github.com/julianhille/docker-mailserver/tree/dovecot-mysql) and use postfixadmin as a companion service.
I don't really mind adding database, it's not a big deal at all.
https://github.com/julianhille/docker-mailserver/tree/dovecot-mysql)
Wow, that looks exactly what I was looking for (and implemented partially by myself already). But why isn't it merged yet? Are there any objections for this feature?
Without using a database, it would manipulate files, I don't know if this kind of web manager exists but it's sounds dangerous :skull_and_crossbones:
_I would recommend you to use a deployment tool such as Ansible and you will never go back to web managers ;)_
Are there any objections for this feature?
It would imply an important breaking change and it's not the "philosophy" of this project, according to Thomas:
I had a look to some docker images, but most of them where more complicated than I expected, and also using *SQL databases.
I wanted something:
simple to install
versionable, only based on config files that can be pushed into my git repository
easy to deploy using a single command line
https://tvi.al/simple-mail-server-with-docker/
@okainov there are indeed objections. There has been issues and PRs about this before, some have been answered by @tomav himself and as @youtous writes it goes against the basic goals of this project. There is nothing wrong with having a database and a GUI, but there are other projects that do that and we don't. Simple as that.
You could of course put a custom GUI (that manipulates files directly or using the setup script) in a companion container, but I would not recommend it. I think you are better off finding a project that uses a database with a GUI from the outset where it is supported and configured out of the box. There should be no shortage of those.
In case that somebody lands here we've just created a docker image merging dovecot-mysql branch with current tomav/docker-mailserver, here the code.
Cheers.
@erik-wramner I not quite sure I understand why the work of @keducoop should not fit into this project. It is merely a configuration option to be able to utilize mysql backend - it does not involve including the sql-database server in the project.
I think the "wontfix" should be reconsidered