We know when you lie. We can see uptime stats.
We know when you lie. We can see uptime stats.
And it took a lot of hard work by a lot of people to adopt new date standards to avoid that problem. Now it’s time to adopt new IP standards, and it’s going to take a lot of hard work by a lot of people.
You know, I’m sure I came across one earlier, but I can’t find it now. I did find https://git.sr.ht/~kline/firebee now though, but I don’t think that’s what I had found before.
As someone who works with small businesses, most of whom run their own internal email server, I completely disagree. Yes, it does take some knowledge of DMARC, DKIM, SPF, and DNS, but any well-managed server would have those set up properly anyway. GMail has no issue accepting email from a correctly set up server.
AOL servers, on the other hand, are a massive PITA.
I’ll be honest with you, I would rather have the ban lists than not. No server is required to use them, and the amount of spam and fraud they filter out is enormous. If someone gets on an IP blocklist because they either can’t or don’t know how to secure their system, then no one should trust anything from them. Having a way to identify them before they cause a problem is enormously helpful.
There is already a project underway to identify federated servers that just spew spam, and I am all for it.
The metrics are the only important part! How else are we supposed to know how good the line is unless we constantly stress test the line by collecting data? Your ability to use the line is not a useful metric, so we don’t worry about that.