Differences

This shows you the differences between two versions of the page.

--- bind_-_senderid:senderid_introduction [2016/11/29 12:15] – peter
+++ bind_-_senderid:senderid_introduction [2020/07/15 09:30] (current) – external edit 127.0.0.1
@@ Line 40: / Line 40: @@
 Sender ID addresses a very different problem than SPF.
+  * SPF validates the HELO domain and the MAIL FROM address against the policies published via DNS (SPF record).
+  * Sender ID validates one of the message's address header fields defined by [[http://tools.ietf.org/html/rfc2822|RFC 2822]].  Since it was derived from SPF, Sender ID can also validate the MAIL FROM.  But it defines the new PRA identity to validate, and defines new sender policy record tags that specify whether a policy covers MAIL FROM (called MFROM by Sender ID), PRA, or both.
 Unlike SPF which validates against the envelope’s return-path address which is the root or subdomain, Sender ID validates based on the PRA and uses the header field with the email address to identify the visible sender of the message. Since headers are not required by the SMTP protocol, Sender ID uses the content of the message to provide an extra layer of protection against spammers and phishers that is very different from SPF which validates on the domain or connection level.
 Sender ID and SPF should both be adopted along with DKIM.  These methodologies complement each other and in doing so, provide the best protection against phishing.
+Neither is better because they solve different problems:
+  * SPF can be compared to other SMTP layer protocol like CSV/CSA.
+  * Sender ID can be compared to other RFC 2822 layer protocols like DomainKeys IM(DKIM)