upvote
There was no chance that everyone would be running their own email server, but if it wasn't for the lack of IPv6 adaptation a plug and go home email server solution would probably see a decent amount of use. I'd bet we'd already be seeing it as a feature in most mid-ranged home routers by now.
reply
The mail server in a router is easy to host, the problem is:

1) Uptime (though this could be partially alleviated by retries)

and most of all:

2) "Trust"/"Spam score"

It's the main reason to use Sendgrid, AWS, Google, etc. Their "value" is not the email service, it's that their SMTP servers are trusted.

If tomorrow I can just send from localhost instead of going through Google it's fine for me, but in reality, my emails won't arrive due to these filters.

reply
Trust / spam score is the largest one I think, second to consumer ISPs blocking the necessary ports for receiving mail.

Even if your "self hosting" is renting a $5/month VPS, some spam lists (e.g. UCEPROTECT) proactively mark any IP ranges owned by consumer ISPs and VPS hosting as potential spam. I figured paying fastmail $30/yr was worth never having to worry about it.

reply
For "Trust", I believe patio11 described this system as the "Taxi Medallion of Email".

e.g. you spend a lot of money to show that you are a legitimate entity or you pay less money to rent something that shows you are connected to said entity.

reply
The specific concern around uptime & reliability was baked into email systems from almost the start - undeliverable notifications (for the sender) and retries.

But yes, the “trust / spam score” is a legit challenge. If only device manufacturers were held liable for security flaws, but we sadly don’t live in that timeline.

reply
Its not a device/MTA issue, SMTP just is not a secure protocol and there is not much you can do in order to 'secure' human communication. Things like spoofing or social engineering are near impossible to address within SMTP without external systems doing some sort of analysis on the messages or in combination with other protocols like DNS.
reply
SMTP isn't at fault, the social ecosystem is at fault. Every system where identities are cheap has a spam problem. If you think a system has cheap identities and no spam, it probably doesn't have cheap identities — examples are HN or Reddit.
reply
Not to detract from your wider point, but there's a few ISPs which own IP blocks which aren't blacklisted.

I had quite a bit of success with it and of course, DKIM and the other measures you can take some years back.

For personal emails, I don't think I had any which fed straight into spam.

reply
If everyone ran a mail server at home spam scores wouldn't be so strict
reply
> "Trust"/"Spam score"

See jwz's struggles with hosting his own email. (Not linking to his blog here with HN as the referrer...)

With email, the 800 lb gorillas won, and in the end it didn't even solve the spam problem.

reply
3) Upgrades suck. Admin also sucks

Maintenance is probably my number one reason for giving up on projects where I'm responsible for feeding the pet.

reply
For one, if my power goes out for an extended period of time I'd still like to be able to access my email. Communications really can't be hosted locally.
reply
What a weird take. I was running my own email server 25 years ago on a 512 kbit ADSL line. No problem at all, would even be enough bandwidth today for most messages.

(Back then email still worked from residential IP addresses, and wasn't blocked by default)

reply