Selfhosted

I don't. But I do have my domain and use a hosted solution, so I'm kind of independent and own my data.

I feel like I'll eventually have to... mailbox.org upped their prices from 1 EUR/mo to... whatever they are right now, and on top of that I'll still need a VPN to access heinous sites such as pastebin (welcome to Turkey), which is another 5 EUR/mo.

For that money I could get an alright enough VPS from Hetzner and spend some time getting everything configured properly, and have bonus flexibility in terms of hosting anything else I might want to host.

The problem with this ofc is that no "turnkey" mail bundle seems to give a shit about resource usage as far as I'm aware, and I'm worried they'll end up hogging all the server resources for themselves.

Yes, with mailcow.email and a catchall and random email system with Anonaddy.

Very interesting. Thanks for the follow up.

@DidacticDumbass@lemmy.one I do, it is a pain and I understand why it is not worth for some people.

I used to run my own mail server about 2 years ago but unfortunately the spam got so bad I didn't have the time to manage all the filters. I moved over to ProtonMail since I can still use my own domain there. So I guess I would say it's not really worth it also it really sucks if your power is out and not having access to sent your power company a strongly worded email.

I run a complete ISP style setup with multiple domains. I run it from a rented server at Hetzner, so i don't have problems with being black listed for sending from a consumer IP.

I did for a couple years, but moved to mailbox.org a while ago. The effort was much to high to save a few bucks and there is no real upside to it. E-Mail is a troublesome mixture of different protocols from the internet stone age held together by chewing gum (SMTP, POP3, IMAP, DNS, database or file storage, maybe ActiveSync, Web-Mailer, ...)

Even when everything is up and running there is always maintenance to keep your SSL certificates up to date, update your incoming spam filter technique, keep other mail providers assured that you are not spamming (DKIM, etc.), keep all the different system services (see above) up to date and interoperable, etc. and every few years when you want to move to a new server, provider or Linux distro you start it all over again.

there are many replies saying similar things, but don't be discouraged from try it out. i host my own with mailinabox on a vm from a cloud provider. no spam issues. the only wildcard was spending a few months getting my ip address off google's spam filters. it is so worth it, i own my own email/calendar/contacts/notes/todo list/ AND website solution. all with mailinabox. completely disconnected from google etc.

I used to run an OpenBSD mailserver for my personal email address for a few years. It wasn't that difficult to setup, more tedious and annoying than anything. I stopped doing it when I started searching for a job as I was too paranoid about my emails getting rejected without me knowing about it. I don't send many emails, but when I do send them I want to know they are getting to where they need to go. I know I was never blocked by gmail, but I couldn't be sure about other providers.

Now I just use my domain name as a catchall on mailbox.org and access it using offlineimap. All my emails are saved and backed up, so switching providers is no problem at all.

I used to. I had a docker-mailserver. It was good. But I moved house and changed ISP. I couldn't set up the reverse DNS on my address, and Gmail was blocking me, so I had to switch to a hosted mail server (namecheap private email).

It's a shame, syncing is noticably slower, and I only get one mailbox, but oh well. Just keep on using GPG.

Running a mail server these days is not that difficult. While using pre-assembled stacks like mailcow only the DNS entries needs to be done. If you want to run it at home you should do some research on routing all the traffic through a wireguard tunnel to preserve a public IP other mail instances will accept

I've thought about rolling my own email service, but I'm hesitant given the risk of it inadvertently nuking the rest of my network. There's a lot of work needed to keep the thing secure, and even if you do everything right there's a good chance you get SMTP traffic blocked because other services are worried about unknown accidentally hosting spammer networks.

Plus given my prior track record, there is a $1000% chance I screw up the DNS entries for any mail servers I set up.