3 ms·
SPF/DKIM are not intended to prevent people from sending spam. They are intended to let a domain owner tell other email providers what servers have the right t
by rsyring 4y ago
SPF/DKIM are not intended to prevent people from sending spam.
They are intended to let a domain owner tell other email providers what servers have the right to send email from that domain (and sign email).
I can send email all day from joboffers@google.com. But most email providers will check SPF and see that my VPS IP is not authorized by google.com to send email, and it will go to spam.
Those standards wouldn't keep me from registering example.com, setting up SPF correctly, and then spamming. There are other techniques to filter out that kind of behavior.
- Symbiote 4y ago> I can send email all day from joboffers@google.com. But most email providers will check SPF and see that my VPS IP is not authorized by google.com to send email, and it will go to spam. Actually, it will be discarded completely. Google's DMARC policy is for mail from unrecognized origins to be rejected: host -t txt _dmarc.google.com _dmarc.google.com descriptive text "v=DMARC1; p=reject; rua=mailto:mailauth-reports@google.com" p=quarantine would send it to spam.