Personally I am not a fan of the new website deaign, it looks like it was redesigned with "claude, make me a new website" and it doesnt look like the professional version any more.
Also, are lifetime plans no longer available for purchase?
Hi!
Some of my systems are IPv6 only. They cannot connect to MXroute because their servers, such as shadow.mxrouting.net, are IPv4 only. Is there a plan to enable IPv6 for client connections, at least?
Thanks!
I have a lifetime MXroute account that I've barely used for the last few years. I mostly keep it around to host emails for my parents to save them from ridiculous ISP fees and for various homelab services that need SMTP. I also have a habit of buying cheap novelty domains, sometimes gifting them to nerdy friends along with a working email address.
The problem is that at least once a week, I get a message from my parents or friends asking me to reset their passwords. Because MXroute is incredibly reliable, it is mostly "set it and forget it," meaning I never remember my own admin password when I need to help them.
To fix this, I spent a few late nights hacking away with Cursor and the API docs. Things snowballed, and now I have a complete self-hostable panel: MXroute-manager.
Link:https://github.com/t0msh/mxroute-manager
It covers most of the things you can do with the MXroute API, but I added some extra features to make managing users and domains a lot easier:
I make no secret of the fact that this was heavily AI influenced during development. It started as a fun project to help me learn more about coding and building tools for my own stack, but I figured I would share it here in case anyone else finds it useful.
Let me know what you think!
As many of you have no doubt noticed, the servername.mxrouting.net/webmail instances go down every time someone adds a domain, every time someone requests an SSL certificate, every time the system renews someone's SSL certificate. This is an old problem that has reached critical mass with our growth this year. Basically, Apache config reloads cause brief outages. With DirectAdmin still running as our backend (for now), every user has their own httpd.conf include that has to be loaded on every config reload. The more users we have, the longer that takes. The longer it takes, the more likely you notice the webmail go down.
Ultimately, our plan isn't to scale these webmail instances. Our plan is to replace them. But right now they drive your custom webmail.yourdomain.tld URLs, and they serve the one-click webmail login from the control panel.
Tonight, all servers are being upgraded to Litespeed to resolve this.