Sender ID: Difference between revisions

Rescuing 3 sources and tagging 0 as dead. #IABot (v1.6.5)
Corrected mistakes.
Line 5: Line 5:
Sender ID is heavily based on [[Sender Policy Framework|SPF]], with only a few additions. These differences are discussed here.
Sender ID is heavily based on [[Sender Policy Framework|SPF]], with only a few additions. These differences are discussed here.


Sender ID tries to improve on a principal deficiency in SPF: that SPF does not verify the [[Email#Message header|header]] addresses that indicates the sending party. Such header addresses are typically displayed to the user and are used to reply to emails. Indeed, such header addresses can be different from the address that SPF tries to verify; that is, SPF verifies only the "MAIL FROM" address, also called the envelope sender.
Sender ID tries to improve on SPF: SPF does not verify the [[Email#Message header|header]] addresses (of which there can be more than one) that indicate the claimed sending party. One of these header addresses is typically displayed to the user and may be used to reply to emails. These header addresses can be different from the address that SPF tries to verify; that is, SPF verifies only the "MAIL FROM" address, also called the envelope sender.


However, there are many similar email header fields that all contain sending party information; therefore Sender ID defines in RFC 4407 a Purported Responsible Address (PRA) as well as a set of heuristic rules to establish this address from the many typical headers in an email.
However, there are many similar email header fields that all contain sending party information; therefore Sender ID defines in RFC 4407 a Purported Responsible Address (PRA) as well as a set of heuristic rules to establish this address from the many typical headers in an email.


Syntactically, Sender ID is almost identical to SPF except that <tt>v=spf1</tt> is replaced with one of:
Syntactically, Sender ID is almost identical to SPF except that <tt>v=spf1</tt> is replaced with one of:
* <tt>v=spf2.0/mfrom</tt> - meaning to verify the envelope sender address just like SPF.
* <tt>spf2.0/mfrom</tt> - meaning to verify the envelope sender address just like SPF.
* <tt>v=spf2.0/mfrom,pra</tt> or <tt>spf2.0/pra,mfrom</tt> - meaning to verify both the envelope sender and the PRA.
* <tt>spf2.0/mfrom,pra</tt> or <tt>spf2.0/pra,mfrom</tt> - meaning to verify both the envelope sender and the PRA.
* <tt>v=spf2.0/pra</tt> - meaning to verify only the PRA.
* <tt>spf2.0/pra</tt> - meaning to verify only the PRA.


The only other syntactical difference is that Sender ID offers the feature of ''positional'' modifiers not supported in SPF. In practice, so far no ''positional'' modifier has been specified in any Sender ID implementation.
The only other syntactical difference is that Sender ID offers the feature of ''positional'' modifiers not supported in SPF. In practice, so far no ''positional'' modifier has been specified in any Sender ID implementation.