SPF tells you that the email really came from my server. That the email really came from my server tells you that it's really me, as sending through my server requires a password.
Sadly SPF is grossly underused.
SPF tells you that the email really came from my server. That the email really came from my server tells you that it's really me, as sending through my server requires a password.
Sadly SPF is grossly underused.
Seems simple:
If your mail/DNS is setup to support either of these, then cool you don't need to confirm.
Else, you must "ok" each post.
DONE
Very few mail servers allow you to that. Once you add sender authentication, it generally comes with sender authorization.
>Besides, the fact that your domain requires a password is only meaningful to you
Almost all SMTP servers are locked down now, most requiring authentication. Those that aren't get blacklisted pretty quickly.
SPF tells you that the sender is authorized to send on behalf of that person.
It solves 99.9% of the issue.
B566EA61026F474BA8ADB877FF765087@postereous.com
If you're on another device just email whoami@postereous.com and it responds with with your GUID post address. Of course email is hardly confidential, and it would be sent in the clear, but it's a heck of a lot more powerful than simply looking at a from address.