for a long time it hasn't been a software problem. It's been a reputation problem, the only recent change is we're more interested in the domain then the IP now.

There's some online tools out there, and an OSS project that'll scan DKIM reports for you - but this was all I could find. Beyond this, there's commercial tooling / services. I may implement something that keeps a tab on things if I come across any issues.

Please elaborate on this, as I'm not exactly sure what you mean. The email deliverability problem is a side effect of false positives in spam filtering. Unless you have a proposal to completely eradicate false positives?

What do you mean by the email delivery problem? Do you mean setting up DKIM, SPF, and DMARC? It's not that hard, compared to setting up an email server in the first place.

> Isn't there any open source project that solves the e-mail delivery problem?

Aplogies if you do, but it sounds like you misunderstand how email works.

The problems are stricly in policy, not in software. So there is nothing an open source project can do. The problem is that "too big to fail" megacorporations like microsoft just randomly decide to block incoming email from most of the Internet.

If email was fully decentralized (everyone runs their own server) this centralized power could not exist and there wouldn't be any problem.

(That all said, I run my own email infrastructure since long ago and it works fine. But I know some people struggle, which is contrary to the intent of the Internet.)

> If email was fully decentralized (everyone runs their own server) this centralized power could not exist and there wouldn't be any problem.

You would have different problems though. Spam would still be hard, or arguably even harder, because you would have lots of small mail servers with no idea if they are trustworthy or not. Is this uncle Bob, who I havent spoken to for 30 years, sending me a heartfelt message about the family? Or is it a scammer trying to cream some cash out of me?

> Spam would still be hard, or arguably even harder

Doesn't make any difference. The major sources of spam today are places like gmail and outlook servers. You have to run some message classification regardless of where it came from.

> The major sources of spam today are places like gmail and outlook servers.

By volume perhaps, but is that true as a proportion of all mail that was sent via these services? I'd be surprised, though I'd be very interested if there where any numbers publicly available.

> By volume perhaps, but is that true as a proportion of all mail that was sent via these services?

Would you care? I can say that I don't care (as someone running my own email infrastructure).

I run filtering on all incoming email, I don't assign any weight to which email server it came from because it's not a useful factor.

The spam situation could also be better if we had designed into that space. Want to send a single email to a sender that you don't have an existing relationship with? Hashcash. Have a web service that sends lots of emails? Get user consent beforehand with e.g. an oauth token to bypass or lower hashcash difficulty.

the centralized power doesn't exist, but then you run into every misconfiguration possible. is it better? maybe.

Yes, it is better. The reason is that when every email operator is small, the overall email community can pressure them to go fix things. You start by sending notes to postmaster@... with problem reports. If things go ignored you start blocking them and then they wake up fast.

In today's world when microsoft or gmail or yahoo start misbehaving in email handling, what are you going to do? It is impossible to reach them and while you could block them, they will never notice and you're only hurting yourself.

It is the classic problem of centralized power which hurts everyone except the (near-)monopolists.