Comment on Email for self hosted services? (Not personal email)
axum@lemmy.blahaj.zone 2 days agoAh yes. Fuck with dns, reverse dns/ptr records, dmarc, dkim, spf, verify server is not on a blacklisted ip in spamhaus, stand up a server, then implement anti spam filters, and hope anything you send doesn’t end up in someone else’s spam filters, as well as monthly checks to make sure no spam lists have sudddenly added your domain/ip to said lists.
But hey easy right?
Theoriginalthon@lemmy.world 1 day ago
Actually yes, if you take each piece one step at a time it’s not that bad, as long as you are not expecting a fully functioning mail server on day 1 it’s relatively easy.
Dultas@lemmy.world 1 day ago
Yeah, this is self hosting after all. If you don’t expect some challenges to work though then you’re not gonna not have a good time.
Theoriginalthon@lemmy.world 1 day ago
The crazy thing is I can do a mail server easily, but I always get stuck or annoyed with docker, everyone says docker is easy 🤷
Dultas@lemmy.world 23 hours ago
Yeah that’s going to depend a lot on the images you’re running. If it’s a published one the likely it’ll have a compose or at least a one liner to get it running. But yeah there can always be issues with hard coded IDs and if you want to give the host folders 777 or limit them. Are you running selinux and that’s going to get in the way. Did they not mention capabilities that needed to be added?
And if you’re building your own or extending that a whole other ball of wax.
And I typically run on k8s so that adds a whole other layer of complexity. But I’ve been using it for years and I’m actually more comfortable with it than just docker or podman.