From efd10c33bec7999e3eb9e2aa2c3d5efa21be61ba Mon Sep 17 00:00:00 2001 From: Dennis Baaten Date: Mon, 20 May 2019 14:51:52 +0200 Subject: [PATCH] Updated SPF how to (markdown) --- SPF-how-to.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SPF-how-to.md b/SPF-how-to.md index 0741702..4b7f089 100644 --- a/SPF-how-to.md +++ b/SPF-how-to.md @@ -8,7 +8,7 @@ SPF is short for "**S**ender **P**olicy **F**ramework" and is described in [RFC Our current e-mail infrastructure was originally designed for any mail sending host to use any DNS domain name it wants. The authenticity of the sending mail server cannot be deterimined, which makes it easy for random third parties to make use of a domain name with possibly a malicious intent. This increases the risk of processing e-mail since the intentions of the sender (host) are uncertain. SPF can help the fight against spam and other kinds of unwanted e-mail be offering a way of authenticating the sending mail server. # Tips and tricks for implementation -to-do +* The sender address shown to the user ("5322.From header") is not used when authenticating. SPF uses the invisible "5321.From header". Combining SPF with DMARC removes this disadvantage. # DNS records (outbound e-mail traffic) SPF for outbound e-mail traffic is limited to publishing an SPF policy as a TXT-record in a domain name's DNS zone. This enables other parties to use SPF for validating the authenticity of e-mail servers sending e-mail on behalf of your domain name.