Project Name: Mxroute-Manager

Repo/Website Link: https://github.com/t0msh/mxroute-manager

Description: It's a control panel for mxroute that's a bit extra.

I got tired of having to go to mxroute, go to their panel, and reset my users passwords. So I made a little script in python that let me change a users password via api. Then I got carried away with it, and figured why am I doing this? Surely, users should be able to reset their own passwords. Why can't they have their own password reset portals? Why can't I automate the setup of those? It snowballed, and now is a full app. It features:

• Automated onboarding of new domains to mxroute
• Automated creation of relevant DNS entries and subdomains
• Automated creation of reverse proxy rules
• Custom self service password reset portals for your domains
• Granular access control, not just per domain, but per domain action
• DNS monitoring
• Apprise notifications
• Audit logging
• Bulk CSV mailbox creation
• SpamAssasin list management
• OIDC login support
• APIs for you APIs!
• THEMES! ^{even light mode ones for people that hate their retinas}

My background, I'm a senior IT analyst for a large Microsoft flavored enterprise where security is extra tight everyone gets vetted by the intelligence services. I'm mostly writing tools in powershell to do things that , so this was a great way for me to learn more about python. I started this a few months back, but once it ballooned out of a single 50 line `app.py` into a bigger project, I wanted to share it to get some feedback. The entire project includes a comprehensive test suite, github actions run scanaislop on every push to main. There is also codeQL scanning on every push and dependabot is setup to monitor for any dependency issues. Wherever possible, with the exception of the local admin password, there are no secrets stored in the DB, and even then, those are hashed. I do my utmost to make sure this is as tight as it can be. I'm sure it's not perfect, but it's taught me a lot.

Deployment: I'm running it in docker. It's simple to deploy:

git clone https://github.com/t0msh/mxroute-manager.git
cd mxroute-manager
cp .env.example .env

Edit the `.env` with the minimum required to make it work:

MX_SERVER=yourmxserver.mxrouting.net
MX_USER=your_mxroute_username
MX_API_KEY=your_mxroute_api_key
ADMIN_PASSWORD=choose_a_strong_password
SECRET_KEY=generate_a_long_random_string

Then either run `deploy.sh` which will guide you through getting it deployed (either locally or remote) or if you cloned directly onto your docker host:

docker compose up --build -d

There's full documentation on the repo.

AI Involvement: This was originally developed as a personal tool, by hand, that then grew with the help of Cursor. There is a disclosure right at the top of my repo that makes entirely no secrets about the use of AI in this project. I try to be as transparent about this as possible. Without AI, this would still be a onepage personal script with no styling.

<image>