Incoming mail is very doable.
Outgoing mail is hard because no one will your trust your server, the easy way is let someone else send your mail.
People get stressed about your receiving server being down sometimes, but this actually not a big deal. Mail senders typically will try for 48 hours or so to deliver mail, and if it doesn't get delivered it will be sent back to the sender with a "could not be delivered" message. Very little gets actually lost.
The thing that got me to pay someone else to host my mail is having outbound blocked by google/Microsoft all the time for no reason.
There are reasons, and you can fix them if you know what you're doing. That's what DMARC reports are for.
I do, a bit differently from what’s been mentioned here so far:
I actually host my server at home, running mailcow as my email-server-software of choice, and incoming emails do get delivered directly to my ISP-assigned IP via dynamically updated DNS records.
However: Outgoing email is delivered via an SMTP relay service, specifically Mailgun (I like them because for normal everyday email volume it’s free), because even when I was hosting the email server in a datacenter, it was impossible to not encounter deliverability issues.
I host my own, on a server in a data center on IP space owned by a friend of mine. I use mailcow for software.
I do, Postfix and Dovecot. Mine's got 10 years of history so I've been spared being blocked everywhere.
Most will tell you the software side is not too bad these days but the constant fighting to get your emails through can be really rough.
Personally I find it useful if only for the sake of just registering every service to its own unique email address so I can track who got my data where, and I get the privacy of Google not knowing every site I'm registered with. I still use my Gmail when I want to be sure it goes through.
I really don't send that many emails so it works pretty well for me.
I did for a while but stopped because it’s a massive pain and far easier to just use proton or something.
Exim and Dovecot. With a clean IP on a VPS and SPF, DKIM and DMARC I haven't really encountered any problems yet. Though I'm only doing it for about 2 years.
This is the way. Exim is far easier to config than Postfix, which is what I'm using now. I'd run Exim before for years, but thought I'd try Postfix since it's the popular kid. It was a mistake, but everything is running and stable, and... well, sunk costs is keeping me from reconfiguring my set-up.
It's a bit of effort to get everything configured correctly in any case, because of the number of moving parts. SPF and DMARC on the DNS entries, dovecot, Postfix or Exim, and a spam manager. Spam management consumes a huge amount of resources.
It really is the only way, though.
I self host it on my Synology NAS at home, using their MailPlus server and clients. It definitely took some time to get it up and running, but now it works without issue and very little maintenance required. My domain provider also acts as backup mx (for when the NAS is offline) and SMTP relay (for sending IP reputation), and the NAS does a daily encrypted cloud backup so nothing can be lost.
The one pain point I have is spam blocking. It does a good job blocking most of the spam, but it's not as good as something like Gmail unfortunately. I have to add custom keyword filters from time to time, and I still get 1-2 spam mails every day that make it past the spam filter. There are paid services to filter out spam, but I think it's not really worth it in my case.
Here is a breakdown of the costs I posted the other day. I'd pay for the NAS, domain and backup service anyway, so the email self hosting is basically free.
I run iRedMail (a collection of dovecot, postfix etc, plus sogo and roundcube web clients and managed by a nice web frontend, all open source and runs on any linux.
I've run for about 8 years, no dramas other than my isp technocally doesnt allow it. But they don't block anything and occasionally they submit their ip ranges for customers to places like spamhaus, so i just script check every month to see if they added my ip back, then i just submit removal, it takes all of 30sec. (IP is semi static, probably changes once every 9 months or so, so not a drama to update dkim on my domain registrar.)
Same here, IRM for 3 years. It's not as difficult as so many make it out to be. As long as your ISP allows port 25 and you're not blacklisted, you're good to go.
I use Mailcow Dockerized with no issues. But I've also ran email servers for 3 decades personally and professionally. If you try it, I would start out with a completely different domain and be prepared to be down for a long time while you figure out how to appease the anti-spam gods with things like SPF, DKIM, DMARC and DNS issues.
I ran my own email server about 10-ish years ago for a while on a Linode using Postfix and Dovecot similar to what others have mentioned. Took some effort to prevent GMail from just flagging everything I sent as spam, but I was eventually able to do it. I remember having to configure something particular with DNS records. (An SPF TXT record, probably?)
I didn't end up using it very much and shut it down after a couple years, but it was a good exercise and I learned a lot from doing it.
Yes, self-hosting my email server since 2 years without issues so far. I only send a handful of emails per month but haven't stumbled into any issues of being blocked by any big provider, even the ones that are known to block small email servers here in Germany. I enjoy the flexibility of as many aliases and distribution groups as I want for the family and being able to configure the anti-spam-component the way it works best for us.
I run everything on a small VPS at a known provider and checked the IP against block lists. It was indeed listed on one but I never had issues and when checking again a few days ago it wasn't listed on any list anymore.
First I tried the available all-in-one solutions but troubleshooting is hard if you don't know each component.
So, I followed this guide but moved all components in their own docker containers instead of installing natively to be more failsafe regarding system upgrades:
https://workaround.org/ispmail-bullseye/
Everything is running fine and in case of issues I know exactly how each component is set up and can troubleshoot quickly.
I run postfix and dovecot at a server at home with no issues for a few years now.
Pretty much the same here, but in a linode vps that hosts a few other things as well.
My ISP blocks the email protocol ports inbound to me so I whilst I have my own domain and email server, I can't actually use it.
Can't wait to get off this body-corporate mandated internet, I'd go with another provider but I don't have any other choice.
I used to use postfix, dovecot, spamassassin. I then moved from dovecot to exchange for better web client and sharing capabilities. I got fed up with the constant chasing of patches for Exchange that needed more than just an installer, they needed reg fixes, DNS updates, certificate changes etc. I ended up moving my family to 365 with free licenses to spare me the hassle.
Yes, although like someone else mentioned - I don't, and ever wouldn't try to host it at home, but on a server at a data center. The network is operated by a person I know and trust.
No IP reputation issues that I've run into, but even going in I knew that its very rare I send emails so it probably wasn't going to be an issue either way. I've only had it running for about two years now, but in that time frame I've sent one email out where I "started the conversation", and three emails where I was replying back to someone who already had my email in their address book.
I use Mail-in-a-Box on a VM at home. Static IP from my ISP. Been working well for years now. I recommend it.
If your IP isn't trusted you could always use an SMTP relay somewhere else.
Been hosting my own email in my home with Exchange Server for almost 2 decades. I don’t recommend it unless you have experience and a MSDN account though.
Email used to be easy, but with all the anti spam and trust setup required these days it’s a bit more difficult for the inexperienced. You’re going to need to know DNS, SMTP, certificates, and have a plan for message hygiene (anti spam / anti malware).
That said, if you want to do it and can suffer some issues while you’re learning, go for it. That’s how you get experience. :)
Too much responaibility in case of downtime. I will rather pay.
Movies on the other hand...