←back to thread

429 points pabs3 | 1 comments | | HN request time: 0s | source
Show context
upofadown ◴[] No.43470130[source]
SPF/DKIM is really about mail server reputation. So it mostly benefits larger servers like the ones run by Google, Microsoft and Yahoo. Unfortunately, that means that attempts by those larger providers to combat spam using such reputation will naturally hurt smaller providers. So the actual effects of SPF/DKIM are on the whole negative.

The root problem is that we don't actually need to keep track of email server reputation. No one says to themselves "Huh, this is from a Gmail address, it must be legit". We really want to keep track of sender reputation. We need to be able to treat anonymous email differently than email from people we actually know. That implies that we have some work to do on the problem of identity. As it is, there is not even a way for a known email sender to securely introduce an unknown email sender. You know, the way that regular human people normally are able to transfer identities from one to the other.

replies(10): >>43470222 #>>43470231 #>>43470355 #>>43470363 #>>43470411 #>>43470421 #>>43470529 #>>43470539 #>>43470682 #>>43471471 #
dig1 ◴[] No.43470355[source]
> That implies that we have some work to do on the problem of identity. As it is, there is not even a way for a known email sender to securely introduce an unknown email sender.

There is: gpg/pgp signature, but many people find it complicated, primarily because they are reluctant to read the documentation. And it’s popular to criticize it, especially here on HN, in favor of various half-baked alternatives.

replies(3): >>43470420 #>>43470599 #>>43470634 #
1. ChrisMarshallNY ◴[] No.43470599[source]
> many people find it complicated

That's what kills a lot of these "perfect" implementations.

HN members tend to be nerds, and we don't really have an issue with setting stuff up (many HN IDs, for instance, have Keybase auths).

Most non-HN types have no patience for that stuff. Security needs to be made accessible and easy-to-use, before the vast majority of folks will implement it. That's the single biggest conundrum, IMNSHO.