[mjl-]

I'm hoping to make this easier in the future, more often automatically taking care of updates. In the past, you've had to run a command/script here or there to fix up date, but that should all be done automatically.

My talk at FOSDEM was about this for a good part, https://fosdem.org/2025/schedule/event/fosdem-2025-5364-mox-....

If you have suggestions on how to make it less choreful to maintain, I'm interested in hearing it! Also if you had specific issues about maintenance/updates.

[dwedge]

I love mox and was at your talk. I've been using it for a year. If I could make a few small feature requests (which may already exist) - I'd love to be able to use my external spamassassin with it instead of (or even in addition to) the built in one.

Secondly the documentation/instructions could be clearer for non-typical use cases, for instance catch-all emails. I have an Exim server with two domains pointing to it, I have catch alls on both, but the second domain is delivered into a folder in the first (it's used similar to SimpleLogin - for signing up to services). I assume this is possible with Mox but I'm not sure.

Having said that, I love Mox and I'm slowly moving all the email I host for other people onto it because it just seems to work.

[mjl-]

> (which may already exist) - I'd love to be able to use my external spamassassin with it instead of (or even in addition to) the built in one

This isn't possible yet. For me, the builtin filtering has been enough. But it's worth investigating what it takes to ask spamassassin for a classification. Could you open an issue at github for this?

> the documentation/instructions could be clearer for non-typical use cases, for instance catch-all emails

Agreed, documentation is in need of improvement. So far I'm often pointing people at https://www.xmox.nl/config/. Searching there typically pops up a config option. But it's not the easiest to find functionality that way. The admin web interface also needs to be made less spartan.

The catchall is possible, by configuring an address "@$yourdomain" with an account.

> because it just seems to work

This is certainly the goal. And I think we'll only get better over time!

[reidrac]

Thank you, this is essential!

Reading mox FAQ, it looks close enough to the ideal: https://www.xmox.nl/faq/#hdr-how-do-i-stay-up-to-date

I'm currently running a more classic setup with postfix and dovecot, because the updates and security fixes are managed by Debian. Once things are configured, I don't need to do anything using unattended upgrades (other than upgrade Debian itself when the LTS version goes out of support, that is!).

At this point it is easier for me to not touch what I have, but in my next mail server I will consider mox!

[mjl-]

> because the updates and security fixes are managed by Debian. Once things are configured, I don't need to do anything using unattended upgrades

This is a good point. It would be great to have mox packaged in more distributions. I spoke with a package maintainer about this. They understandably need to be able to upgrade unattended from old versions to a new version. In the past year, admins have had to run an upgrade command here and there (e.g. to reparse all the messages after the parsing code changed). I hope to make all this more automatic this year. That should make it more appealing for packagers (and for all non-distro-using admins too!).

I think a new debian LTS release will be coming up soonish, we probably won't make that.