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
Run in parallel with mailcow-dockerized #403
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
@strarsis, yes is possible. Actually i configured a volume to have access to the regexp lists on postfix container as well as on mailman-core container. Furthermore it was necessary to overwrite the mta configuration in order to force the STARTTLS. Also i needed to work with the vmap from mailman to got it proper configured, but in my test it finally worked. At https://github.com/Shadowghost/mailcow-mailman3-dockerized there is a try to combine both projects. I didn't tested it out yet, working on my own compose. For web it is strongly recommended to have a reverse proxy in front of it. |
@monofox: Would it be worth the extra costs of a separate server/cloud instance just for the mailer/newsletter/newsgroup daemon? OTOH, mailcodw already ships with extra web services like SOGO. |
@strarsis In regular cases for small usage not required from my point of view. Mostly depends on the host systems capabilities and resources. |
@monofox: There are also other services like mailmonk for newsletters/mailing lists. Any recommendations? |
I wrote a guide to install and config mailcow-dockerized with docker-mailman. It's now in a kind of beta state, but may help to get it working. Help and bug reports are appreciated. |
This issue has not been updated for more than 1year |
Not stale! |
This issue has not been updated for more than 1year |
Is it possible to run docker-mailman in parallel with mailcow-dockerized?
The main issue that comes to mind is the web frontend that has to be passed through by a reverse proxy?
The text was updated successfully, but these errors were encountered: