Support
Where to send it.
One address for anything to do with a licence or a payment, GitHub for anything to do with the software. The two most common requests answer themselves in less time than an email takes, so they come first.
Lost or missing key
- Instant and self-service — no reply to wait for
- Keys are only ever emailed to the address that bought them, and never shown in a browser
- Three requests an hour, per address and per network
Billing, card, cancellation
- Stripe’s billing portal handles the card on file, invoices and cancelling
- Ask for it on the same page with Manage subscription; the link is emailed to the purchase address
- There is no login here — this service holds no password of yours, so the mailbox is the proof
Email support@mimux.dev
Licences, payments, invoices, and anything above that did not do what it should have: support@mimux.dev.
Include these, so the first reply can be the useful one:
- The licence id (
lic_…, listed in the mail /retrieve sends) or the address you paid with - The version:
mimux -version - For a licence problem, what
mimux licence statusprints — it says which key is in use, where it was read from, and what the build makes of it
No ticketing system, no queue position, no promised response time. Email support is the thing a pro licence buys; GitHub issues are read as time allows.
Bugs and feature requests
These go to
GitHub issues, not to
the support address — a bug in the open is a bug other people can find.
Read
CONTRIBUTING.md
first: the policy is issues yes, pull requests usually no, and it lists what a
report needs (the version, how you run it, which IMAP provider, and the output
of make diagnose, which is sanitised).
Security reports
Not in a public issue. Open a private GitHub security advisory, or email security@mimux.dev if you would rather not use GitHub. SECURITY.md has the scope, the known design tradeoffs that are decisions rather than bugs, and what to expect back.
What the licence covers
Short version, since it is what most licence mail turns out to be about. A perpetual key never expires and covers every build released within a year of the purchase; those builds keep working forever, and a build released after that year needs a new purchase. An annual key runs for a year and renews, with a 45-day grace period after expiry so a failed card is a nuisance rather than an outage. With no key at all there is a 14-day trial from the first boot of a pro build.
Whatever the state of the licence, only the automation layer stops — the REST API and the MCP server. Sync, send, search and the mail client itself are AGPL code that has no idea a licence exists, and never stop. The docs have the detail; the pricing page has the comparison.