Jump to content

Sender ID: Difference between revisions

From IdeaWazaWiki
Cleanup: remove deletion notice and missing templates
 
(70 intermediate revisions by 51 users not shown)
Line 1: Line 1:
'''Sender ID''' is an anti-[[E-mail spoofing|spoofing]] proposal from the former [[MARID]] [[IETF]] working group that tried to join [[Sender Policy Framework]] (SPF) and Caller ID. Sender ID is defined primarily in Experimental RFC 4406, but additional parts in RFC 4405, RFC 4407 and RFC 4408.
{{Primary sources |date=May 2024}}
'''Sender ID''' is an historic<ref>{{cite web| url=https://datatracker.ietf.org/doc/status-change-change-sender-id-to-historic/| title=Moving RFC 4405, RFC 4406, RFC 4407 (Sender-ID) to Historic| author=Alexey Melnikov| date=7 February 2020| website=[[Internet Engineering Task Force|IETF]]}}</ref> anti-[[E-mail spoofing|spoofing]] proposal from the former [[MARID]] [[IETF]] working group that tried to join [[Sender Policy Framework]] (SPF) and Caller ID. Sender ID is defined primarily in Experimental <nowiki>RFC 4406</nowiki>,<ref>{{Cite IETF|last1=Wong|first1=Meng Weng|last2=Lyon|first2=Jim|title=Sender ID: Authenticating E-Mail|RFC=4406}}</ref> but there are additional parts in <nowiki>RFC 4405</nowiki>,<ref>{{Cite IETF|last1=Katz|first1=Harry|last2=Allman|first2=Eric|title=SMTP Service Extension for Indicating the Responsible Submitter of an E-Mail Message|rfc=4405}}</ref> <nowiki>RFC 4407</nowiki><ref name=":0">{{Cite IETF|last=Lyon|first=Jim|title=Purported Responsible Address in E-Mail Messages|rfc=4407}}</ref> and <nowiki>RFC 4408</nowiki>.<ref>{{Cite IETF|last1=Schlitt|first1=Wayne|last2=Wong|first2=Meng Weng|title=Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1|rfc=4408}}</ref>


== Principles of operation ==
== Principles of operation ==


Sender ID is heavily based on [[Sender Policy Framework|SPF]], with only a few additions.  This article will mostly discuss just these differences.
Sender ID is heavily based on [[Sender Policy Framework|SPF]], with only a few additions.


* They both use TXT records published by the [[Domain Name System|DNS]] servers of a domain name.
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.
* They both give rules that the owner of this domain name intends to respect in all headers of his genuine outbound messages.
* They differ on what rules they apply to what fields contained in the message header.
* They both are intended for use by [[E-mail client|mail clients]] and [[Web-based email|web mail servers]] (and some [[Mail transfer agent|MTA]] servers) to distinguish good mail from junk by helping to authenticate the sender.


Syntactically, SPF and Sender ID are almost identical:
However, there are many similar email header fields that all contain sending party information; therefore Sender ID defines in <nowiki>RFC 4407</nowiki><ref name=":0" /> 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.
Replacing the string <tt>v=spf1</tt> in a valid SPF
policy by any of the following yields a syntactically valid Sender ID policy, and
vice versa:
* <tt>spf2.0/mfrom</tt>
* <tt>spf2.0/mfrom,pra</tt>
* <tt>spf2.0/pra,mfrom</tt>
* <tt>spf2.0/pra</tt>
The evaluation of SPF and Sender ID policies
follows the same general rules. The core Sender ID
specification has a normative reference to the SPF
specification and thereby inherits exactly the same error
handling, the same processing limits, and the same syntax
details as SPF.


Semantically, there are only two differences: 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.
Syntactically, Sender ID is almost identical to SPF except that <code>v=spf1</code> is replaced with one of:
* <code>spf2.0/mfrom</code>{{Snd}}meaning to verify the envelope sender address just like SPF.
* <code>spf2.0/mfrom,pra</code> or <code>spf2.0/pra,mfrom</code>{{Snd}}meaning to verify both the envelope sender and the PRA.
* <code>spf2.0/pra</code>{{Snd}}meaning to verify only the PRA.


Except for this detail, <tt>spf2.0/mfrom</tt> is semantically
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 same as SPF: ''mfrom'' stands for MAIL FROM, the checked
identity in SPF. Because SPF is more widely deployed than the later
proposed <tt>spf2.0/mfrom</tt>, publishers of sender policies
wishing to protect their address in MAIL FROM [[Return-Path]]s
generally prefer the classic <tt>v=spf1</tt> format.


Both <tt>spf2.0/mfrom,pra</tt> and <tt>spf2.0/pra,mfrom</tt>
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|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.
have the same meaning. They introduce a policy that can be
used to check the ''mfrom'' as well as the ''pra'' identity.


Last but not least, <tt>spf2.0/pra</tt> introduces policies
The ''pra'' tries to counter the problem of ''phishing'', while SPF or ''mfrom'' tries to counter the problem of spam bounces and other auto-replies to forged Return-Paths. Two different problems with two different proposed solutions. However, Sender-ID and SPF yield the same result in approximately 80% of the cases, according to a billion message analysis.<ref name=rfc6686>{{cite IETF |title=Resolution of the Sender Policy Framework (SPF) and Sender ID Experiments |rfc=6686 |author=[[Murray Kucherawy]] |year=2012 |publisher=[[Internet Engineering Task Force|IETF]]}}</ref>
checked only with the ''pra'' identity.  At this time it is
not specified how SPF's <tt><nowiki>%{h}</nowiki></tt> macro
for the HELO identity should be handled in ''pra'' checks,
Sender ID implementations could handle it as syntax error.
 
The Purported Responsible Address or ''pra'' is determined by a tricky evaluation of four mail header fields—''From'', ''Sender'', ''Resent-From'', ''Resent-Sender''—resulting either in one address—the ''pra''—or an error for illegal combinations as explained in RFC 2822. Simplified, the rules are: <tt>Sender</tt> beats <tt>From</tt>
and <tt>Resent-</tt>* beats <tt>Sender</tt>. Note that it's illegal to have more than one <tt>From</tt>-address without a single <tt>Sender</tt>-address.
 
This ''pra'' scheme has the theoretical advantage of dealing with addresses
in header fields that are often displayed by MUAs (Mail User Agents),
unlike SPF's Return-Path header field or ''mfrom'' in Sender ID terminology.
 
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 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'',
while SPF or ''mfrom'' tries to counter the problem of spam
bounces and other auto-replies to forged Return-Paths. Two
different problems with two different proposed solutions.


==Standardization issues==
==Standardization issues==
The ''pra'' has the disadvantage that forwarders and
The ''pra'' has the disadvantage that forwarders and mailing lists can only support it by modifying the mail header, e.g. by inserting a <code>Sender</code> or <code>Resent-Sender</code>. The latter violates <nowiki>RFC 2822</nowiki><ref name="rfc2822">{{Cite IETF|last=Resnick|first=Peter W.|title=Internet Message Format|rfc=2822}}</ref> and can be incompatible with <nowiki>RFC 822</nowiki>.<ref>{{Cite IETF|last=Crocker|first=D.|title=STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES|rfc=822}}</ref>
mailing lists can only support it by modifying the mail header,
e.g. insert a <tt>Sender</tt> or <tt>Resent-Sender</tt>. The
latter violates RFC 2822 and can be incompatible with RFC 822.
 
With SPF, mailing lists continue to work as is.  Forwarders
wishing to support SPF only need to modify SMTP MAIL FROM
and RCPT TO, not the mail. That's no
new concept; with the original RFC 821 SMTP forwarders always
added their host name to the reverse path in the MAIL FROM.


The most problematic point in the core Sender ID specification
With SPF, mailing lists continue to work as is. Forwarders wishing to support SPF only need to modify SMTP MAIL FROM and RCPT TO, not the mail. This concept is not new: with the original <nowiki>RFC 821</nowiki><ref>{{Cite IETF|last=Postel|first=J.|title=Simple Mail Transfer Protocol|rfc=821}}</ref> SMTP forwarders always added their host name to the reverse path in the MAIL FROM.
is its recommendation to interpret <tt>v=spf1</tt> policies like
<tt>spf2.0/mfrom,pra</tt> instead of <tt>spf2.0/mfrom</tt>.


This was never intended by all published SPF drafts since 2003,
The most problematic point{{According to whom|date=March 2021}} in the core Sender ID specification is its recommendation to interpret <code>v=spf1</code> policies like <code>spf2.0/mfrom,pra</code> instead of <code>spf2.0/mfrom</code>. This was never intended by all published SPF drafts since 2003, and for an unknown large number of <code>v=spf1</code> policies an evaluation for ''pra'' could cause bogus results for many cases where ''pra'' and ''mfrom'' are different. This problem was the basis of an appeal to the [[Internet Architecture Board|Internet Architecture Board (IAB)]]. In response to another prior appeal the [[IESG]] already noted that Sender ID cannot advance on the [[IETF]] standards track without addressing the incompatibility with a MUST in <nowiki>RFC 2822</nowiki>.<ref name="rfc2822" />
and for an unknown large number of <tt>v=spf1</tt> policies an
evaluation for ''pra'' could cause bogus results for many cases
where ''pra'' and ''mfrom'' are different.


This technical problem — in fact only four characters <tt>,pra</tt>
Various surveys performed in 2012, when SPF turned from experimental to proposed standard, showed that fewer than 3% of mail domains published specific requests for using the ''pra'', compared to some 40~50% of mail domains using SPF.<ref name=rfc6686/>
in the core Sender ID specification — was the base of an appeal to
the [[Internet Architecture Board|Internet Architecture Board (IAB)]].
In response to another prior appeal the [[IESG]] already noted that
Sender ID cannot advance on the [[IETF]] standards track without
addressing the incompatibility with a MUST in RFC 2822.


== Intellectual property ==
== Patents ==
   
   
The Sender ID proposal was the subject of controversy regarding [[intellectual property]] [[licensing]] issues: [[Microsoft]] holds [[patent]]s {{Fact|date=April 2008}} 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 [[licensing]] issues: [[Microsoft]] holds [[patent]]s<ref>{{cite mailing list |url=http://www.imc.org/ietf-mxcomp/mail-archive/msg04844.html |title=FW: Microsoft's Updated Statement about IPR Claimed in <draft-ietf-marid-core-03.txt> and <draft-ietf-marid-pra-00.txt> in Combination |mailing-list=IETF MARID List |access-date=2011-12-20 |url-status=dead |archive-url=https://web.archive.org/web/20120414184741/http://www.imc.org/ietf-mxcomp/mail-archive/msg04844.html |archive-date=2012-04-14 }}</ref><ref>{{Cite web|url=http://www.internetnews.com/dev-news/article.php/3409971/Exposed+Sender+ID+Patents+Up+Debate.htm|title=Exposed Sender ID Patents up Debate|date=20 September 2004}}</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 some free and open source licenses, but not with the most recent version of the GPL license, version 3.x.{{Citation needed|date=March 2021}}


==See also==
==See also==
* [[:Category:E-mail authentication]]
* [[:Category:Email authentication]]
* [[E-mail authentication]] overview
* [[E-mail authentication]] overview
* [[MARID]] (IETF WG in 2004)
* [[MARID]] (IETF WG in 2004)
* [[DKIM]]
* [[DKIM]]
* [[DomainKeys]]
* [[DomainKeys]]
==References==
{{reflist}}


==External links==
==External links==
* [http://www.microsoft.com/mscorp/safety/technologies/senderid/default.mspx ''Sender ID Framework''] [[Microsoft|Microsoft Corporation]]
* http://www.microsoft.com/senderid " SIDF resources and tools including SPF wizard.
* [http://www.apache.org/foundation/docs/sender-id-position.html ''ASF Position Regarding Sender ID''] statement from the [[Apache Software Foundation]]
* [http://www.apache.org/foundation/docs/sender-id-position.html ''ASF Position Regarding Sender ID''] statement from the [[Apache Software Foundation]]
* [http://www.iab.org/appeals/2006-02-08-mehnle-appeal.html IAB appeal] about Sender ID's reuse of <tt>v=spf1</tt> for PRA from the [http://new.openspf.org/ SPF project] (2006).
* [http://www.iab.org/appeals/2006-02-08-mehnle-appeal.html IAB appeal] {{Webarchive|url=https://web.archive.org/web/20110530023347/http://www.iab.org/appeals/2006-02-08-mehnle-appeal.html |date=2011-05-30 }} about Sender ID's reuse of <code>v=spf1</code> for PRA from the [https://web.archive.org/web/20060702025443/http://new.openspf.org/ SPF project] (2006).
* [http://www.debian.org/News/2004/20040904 ''Debian project unable to deploy Sender ID''] statement by the [[Debian]] project
* [http://www.debian.org/News/2004/20040904 ''Debian project unable to deploy Sender ID''] statement by the [[Debian]] project
* [http://slashdot.org/article.pl?sid=04/09/13/1317238 ''IETF Decides on SPF / Sender-ID issue''] coverage and discussion on [[slashdot]]
* [http://slashdot.org/article.pl?sid=04/09/13/1317238 ''IETF Decides on SPF / Sender-ID issue''] coverage and discussion on [[slashdot]]
* [http://www.groklaw.net/article.php?story=20040908180737547 ''Is Sender ID Dead in the Water? - No MARID Working Group Consensus''] coverage and discussion on [[groklaw]]
* {{usurped|1=[https://web.archive.org/web/20100505084303/http://www.groklaw.net/article.php?story=20040908180737547 ''Is Sender ID Dead in the Water? - No MARID Working Group Consensus'']}} coverage and discussion on [[groklaw]]
* [http://www.moongroup.com/index.php?option=content&task=view&id=26&Itemid=2 MARID Co-Chairs Clarify Consensus Statement]
* [http://www.moongroup.com/index.php?option=content&task=view&id=26&Itemid=2 MARID Co-Chairs Clarify Consensus Statement]
* [http://www.imc.org/ietf-mxcomp/mail-archive/msg05054.html ''MARID to close''] mailing list thread.
* [https://web.archive.org/web/20040929020641/http://www.imc.org/ietf-mxcomp/mail-archive/msg05054.html ''MARID to close''] mailing list thread.
* [http://www.circleid.com/posts/sender_id_a_tale_of_open_standards_and_corporate_greed_part_i/ Sender ID: A Tale of Open Standards and Corporate Greed?]
* [http://www.circleid.com/posts/sender_id_a_tale_of_open_standards_and_corporate_greed_part_i/ Sender ID: A Tale of Open Standards and Corporate Greed?]
* [http://www.silicon.com/research/specialreports/thespamreport/0,39025001,39131378,00.htm ''Use Sender ID or we'll junk you, says Microsoft''] [[Hotmail]] and [[MSN]] to '[[Junk]]' mail without Sender ID
* [http://www.openspf.org/SPF_vs_Sender_ID "SPF: SPF vs Sender ID"] {{Webarchive|url=https://web.archive.org/web/20071102120517/http://www.openspf.org/SPF_vs_Sender_ID |date=2007-11-02 }}
* [http://www.openspf.org/SPF_vs_Sender_ID "SPF: SPF vs Sender ID"]
* [https://help.msg91.com/article/53-sender-id-in-various-countries "Sender Id Types in Different Countries"]
 
* [http://www.mysmsmart.com/ "Sender Id"]
[[Category:E-mail authentication]]
* [https://nrt.co.in/bulk-sms/ Sender IDs, SMS templates]
[[Category:Spam filtering]]
[[Category:Microsoft]]


[[de:Sender ID]]
[[Category:Email authentication]]
[[fr:Sender ID]]
[[Category:Anti-spam]]
[[pt:Sender ID]]
[[Category:Microsoft initiatives]]
[[ru:Sender ID]]

Latest revision as of 22:44, 3 November 2026

Template:Primary sources Sender ID is an historic[1] anti-spoofing proposal from the former MARID IETF working group that tried to join Sender Policy Framework (SPF) and Caller ID. Sender ID is defined primarily in Experimental RFC 4406,[2] but there are additional parts in RFC 4405,[3] RFC 4407[4] and RFC 4408.[5]

Principles of operation

Sender ID is heavily based on SPF, with only a few additions.

Sender ID tries to improve on SPF: SPF does not verify the 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[4] 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 v=spf1 is replaced with one of:

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.

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.

The pra tries to counter the problem of phishing, while SPF or mfrom tries to counter the problem of spam bounces and other auto-replies to forged Return-Paths. Two different problems with two different proposed solutions. However, Sender-ID and SPF yield the same result in approximately 80% of the cases, according to a billion message analysis.[6]

Standardization issues

The pra has the disadvantage that forwarders and mailing lists can only support it by modifying the mail header, e.g. by inserting a Sender or Resent-Sender. The latter violates RFC 2822[7] and can be incompatible with RFC 822.[8]

With SPF, mailing lists continue to work as is. Forwarders wishing to support SPF only need to modify SMTP MAIL FROM and RCPT TO, not the mail. This concept is not new: with the original RFC 821[9] SMTP forwarders always added their host name to the reverse path in the MAIL FROM.

The most problematic pointTemplate:According to whom in the core Sender ID specification is its recommendation to interpret v=spf1 policies like spf2.0/mfrom,pra instead of spf2.0/mfrom. This was never intended by all published SPF drafts since 2003, and for an unknown large number of v=spf1 policies an evaluation for pra could cause bogus results for many cases where pra and mfrom are different. This problem was the basis of an appeal to the Internet Architecture Board (IAB). In response to another prior appeal the IESG already noted that Sender ID cannot advance on the IETF standards track without addressing the incompatibility with a MUST in RFC 2822.[7]

Various surveys performed in 2012, when SPF turned from experimental to proposed standard, showed that fewer than 3% of mail domains published specific requests for using the pra, compared to some 40~50% of mail domains using SPF.[6]

Patents

The Sender ID proposal was the subject of controversy regarding licensing issues: Microsoft holds patents[10][11] 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 implementations in general. On October 23, 2006, Microsoft placed those patents under the Open Specification Promise, which is compatible with some free and open source licenses, but not with the most recent version of the GPL license, version 3.x.

See also

References