After a couple of years self hosting my email server with #Mailu I'm trying #Purelymail for my email accounts. It allows me to use my domain name, is extra cheap, and promises me not to have to worry about deliverability (people occasionally find the emails I send them to their junk folder).

It should be much cheaper, and more efficient, than running a dedicated VPS for the only purpose of hosting a couple of Docker containers.

Mailu 1.9 kann nicht mehr updated werden. Deshalb auf 2.0 upgraden. #mailu #mailserver #docker

@Norore
Sans doute serai-je légèrement à coté de la plaque mais je vais décrire ma situation perso :
- un VPS chez OVH à 5€/mois
- #Mailu installé dessus
- toutes les data sur du #btrfs chiffré avec LUKS/cryptsetup
- un p'tit cronjob pour faire snapshots et sauvegardes régulières vers un autre serveur
- mon propre nom de domaine, 15€/an
Et tout marche nickel, depuis plus d'un an.
https://mailu.io

Still torn between #mailu or my own stuff. The major advantage of my own stuff is that I know how it works, and I can set it up from scratch, certificates and whatnot included.

Mailu would need a lot more experimenting, and it'd require me to figure out how to handle the cert situation. As in, I don't want Mailu to try and manage them, I'd do it myself, and let Mailu use them.

The documentation is... a bit lacking in a few ways.

Mkay. Setting up #mailu is proving to be... difficult. I'm starting to think I should just go with what I used for my current mail setup, except containerized better.

Gives me more flexibility, but I lose the nice admin UI. Not like I'd use the admin UI much after initial setup, so no big deal, I guess?

Hrm. Getting started with #Mailu ain't as easy as I had hoped.

Migrating mail it is. But that presents a problem: I'm going to use #mailu, but the setup guide assumes I'm setting up a completely new domain - I'm not. I'll need to pull mail over.

So I guess the plan is to set up Mailu to handle my primary domain, migrate the users, flip the records, and then start importing mail from the old.

And that presents another problem! My primary domain is what I want to migrate last. On the other hand, that "primary" isn't all that primary anymore.

There's also a chance that I can make the forwarding work without a dummy user, if I use the CLI rather than the web-based admin ui. I haven't checked that out....

Or perhaps I can directly interfere with routing, and override it with my custom routing?

But those are advanced stuff. The goal was to check if #Mailu can do what I need, and it can. If I can find a better way than what my quick test found, great. But I'm ok with the workaround too.

Took them all for a test drive, and I'm settling on #Mailu. There are a few shortcomings I need to work around, but everything I want to do with it seems doable.

The first shortcoming I ran into is that I want *@$user.$domain to be forwarded to $user+*@$domain. For that to work, I need to set up a separate domain for each user, and for each domain, have a dummy user so I can set up the catch-all alias. The dummy user does not seem to get caught, so will have to choose carefully.

TOTAL FAIL, switching back to 1.7
#mailu.io

Upgrading my email server (#Mailu 1.7 -> 1.9)
Wish me luck!

@agarwaen 2 ou 3 petites choses quand même :
- Il manque des infos dans la doc pour tout ce qui concerne le DNS (DMARC, DKIM, SPF, etc.)
- Il y a des erreurs dans le docker-compose généré pour la version stable (1_7 au lieu de 1.7 pour la version des images)
- Roundcube dans la version stable ne permet pas de synchroniser un carnet d'adresses distant via CardDav : j'ai modifié le docker-compose pour utiliser une version plus récente.
#mailu

@agarwaen Bon matin ! Retour de mes expériences d'auto-hébergement d'un serveur de mail.
J'ai testé plusieurs solutions sur un VPS 1er prix chez OVH (1 CPU 2 Go RAM 20 Go HDD).
Eh bien je suis bluffé par https://mailu.io
L'antivirus est trop gourmand pour cette petite config et fait vautrer tout le serveur. Mais le reste de la solution est top !
Et l'installation est très aisé grâce à leur générateur de docker-compose : https://mailu.io/1.7/compose/setup.html
#mailu

Changed my mail setup to use #mailu. I like it, but kinda frustrating losing some flexibility you have with using a DIY #postfix/#dovecot setup vs something ready made.

@nezhac@mastodon.social I am planning to install #prosody, I didn't know snikket so I'll have a look at it, thx!
For emails I use #mailu, that is quite simple.

@Matter @jamie you're right about resiliency, but it's still annoying if you can't access them and you need to go home to restart the machine (still need to learn how to efficiently use VMs 😅).

How do you mean "wish it was possible"? It's just a few lines of code for #mailcow, let's not forget #mailu is also a great email package out there!

More people should definitely do it! Unless... You're fine with a single mailbox and a few aliases, then go with #tutanota, #protonmail, etc...