Sender ID: Difference between revisions
Page doesn't excists |
clean up, typo(s) fixed: Indeed → Indeed,, However → However, using AWB |
||
| 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# | 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. | ||
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: | ||
| Line 17: | Line 17: | ||
In practice, the ''pra'' scheme usually only offers protection when the email is legitimate, while offering no real protection in the case of spam or phishing. The ''pra'' for most legitimate email will be either the familiar From: header field, or, in the case of mailing lists, the Sender: header field. In the case of phishing or spam, however, the ''pra'' may be based on Resent-* header fields that are often not displayed to the user. | In practice, the ''pra'' scheme usually only offers protection when the email is legitimate, while offering no real protection in the case of spam or phishing. The ''pra'' for most legitimate email will be either the familiar From: header field, or, in the case of mailing lists, the Sender: header field. In the case of phishing or spam, however, the ''pra'' may be based on Resent-* header fields that are often not displayed to the user. | ||
To be an effective anti-phishing tool, the MUA (Mail User Agent or Mail Client) will need to be modified to display either the ''pra'' for Sender ID, or the Return-Path: header field for SPF. | To be an effective anti-phishing tool, the MUA (Mail User Agent or Mail Client) will need to be modified to display either the ''pra'' for Sender ID, or the Return-Path: header field for SPF. | ||
The ''pra'' tries to counter the problem of ''phishing'', | The ''pra'' tries to counter the problem of ''phishing'', | ||
| Line 41: | Line 41: | ||
== Intellectual property == | == Intellectual property == | ||
The Sender ID proposal was the subject of controversy regarding [[intellectual property]] [[licensing]] issues: [[Microsoft]] holds [[patent]]s<ref>http://www.imc.org/ietf-mxcomp/mail-archive/msg04844.html </ref><ref> http://www.internetnews.com/dev-news/article.php/3409971/Exposed+Sender+ID+Patents+Up+Debate.htm </ref> on key parts of Sender ID and used to license those patents under terms that were not compatible with the [[GNU General Public License]] and which were considered problematic for [[free software]] [[implementation]]s in general. On October 23, 2006, Microsoft placed those patents under the [[Open Specification Promise]], which is compatible with free and open source licenses, but not with the most recent version of the GPL license, version 3.x. | The Sender ID proposal was the subject of controversy regarding [[intellectual property]] [[licensing]] issues: [[Microsoft]] holds [[patent]]s<ref>http://www.imc.org/ietf-mxcomp/mail-archive/msg04844.html</ref><ref>http://www.internetnews.com/dev-news/article.php/3409971/Exposed+Sender+ID+Patents+Up+Debate.htm</ref> on key parts of Sender ID and used to license those patents under terms that were not compatible with the [[GNU General Public License]] and which were considered problematic for [[free software]] [[implementation]]s in general. On October 23, 2006, Microsoft placed those patents under the [[Open Specification Promise]], which is compatible with free and open source licenses, but not with the most recent version of the GPL license, version 3.x. | ||
==See also== | ==See also== | ||