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

Backup MX #591

benyanke opened this Issue Sep 15, 2018 · 3 comments


4 participants
Copy link

benyanke commented Sep 15, 2018

Is there an official Mailu way of running a backup MX? If not, would you accept an alternate docker-compose file and configuration options to run a similar easily-configured backup MX?


This comment has been minimized.

Copy link

hoellen commented Sep 16, 2018

I believe you want something like #177


This comment has been minimized.

Copy link

kaiyou commented Sep 19, 2018

Also, I agree about providing an alternate compose file for running a backup MX. My initial idea on the matter was providing a separate Postfix image with a special configuration and startup script, that given an api token would lookup the list of domains from the primary MX and serve these automatically.

This will become really easy to setup once we have a proper api. Until then, maybe we can have an IP based authentication and an env variable for authorizing backup MX.


This comment has been minimized.

Copy link

muhlemmer commented Oct 13, 2018

Why want a backup MX? You'll expose yourself to high levels of spam. Some (or most?) spammers tend to skip the primary MX record and go straight for the secondary. Secondly, if it does happen your single MX is down, mails are just hold in a queue at the sender's side until available again.

I've read this article in the past, and I do feel they are right.

On the modern internet there are more elegant solutions available for failover /HA. (Swarm, kubernetes, rancher). See also #177.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment