Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: Docker Mailserver #37

Open
vanekj opened this issue Mar 17, 2019 · 2 comments
Open

Suggestion: Docker Mailserver #37

vanekj opened this issue Mar 17, 2019 · 2 comments

Comments

@vanekj
Copy link
Contributor

vanekj commented Mar 17, 2019

https://hub.docker.com/r/tvial/docker-mailserver

Problems

  • requires some ignored docker-compose fields: hostname, domainname, cap_add
  • Let's Encrypt certificate for emails
@githubsaturn
Copy link
Collaborator

I think hostname and domainname aren't really needed. According to their docs, they can also be set via env vars: OVERRIDE_HOSTNAME and SRS_DOMAINNAME

But cap_add is not even supported in Docker swarm yet
😞

moby/moby#25885

@tuefekci
Copy link

tuefekci commented Mar 31, 2019

Im not sure what SYS_PTRACE is used for, but not setting NET_ADMIN is possible cause it is only used for fail2ban which can be disabled in the configuration file.

I still dont see much use in a one-click-app because docker-mailserver does not have an user interface so for creating accounts etc. you still would need to login via ssh?

Edit:
It looks like SYS_PTRACE (docker-mailserver/docker-mailserver#1057) is also not really needed i will setup a oneclick installer and do a test run if everything works out i will add it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants