Sender ID: Difference between revisions
Appearance
Link to german version |
→External links: Alphabetized & added Cat Fight article |
||
| Line 12: | Line 12: | ||
==External links== | ==External links== | ||
* [http://apache.org/foundation/docs/sender-id-position.html ''ASF Position Regarding Sender ID''] statement from the [[Apache Software Foundation]] | * [http://apache.org/foundation/docs/sender-id-position.html ''ASF Position Regarding Sender ID''] statement from the [[Apache Software Foundation]] | ||
* [http://www.emailbattles.com/archive/battles/spam_aabeeighag_ef/ Cat Fight! SPF Claws Sender-ID.] In late August, 2005, changes to the Sender-ID Framework experiment triggered a response from the Sender Policy Framework council that threatened doom for both projects. <i>- Email Battles</i> | |||
* [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://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.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. | |||
* [http://www.mailchannels.com/opensource Open source SenderID module for Apache] | |||
* [http://www.microsoft.com/mscorp/safety/technologies/senderid/default.mspx ''Sender ID Framework''] [[Microsoft|Microsoft Corporation]] | |||
* Two articles on the history of Sender-ID: | * Two articles on the history of Sender-ID: | ||
** http://www.circleid.com/article/730_0_1_0_C/ | ** http://www.circleid.com/article/730_0_1_0_C/ | ||
** http://www.circleid.com/article/732_0_1_0_C/ | ** http://www.circleid.com/article/732_0_1_0_C/ | ||
[[Category:Spam filtering]] | [[Category:Spam filtering]] | ||
[[de: Sender ID]] | [[de: Sender ID]] | ||
Revision as of 20:19, 3 September 2005
Sender ID is an anti-spam proposal from the MARID IETF working group, joining Sender Policy Framework and Caller ID.
The Sender ID proposal is currently the subject of controversy regarding intellectual property and licensing issues: Microsoft holds patents on key parts of Sender ID and licenses those patents under terms that are not compatible with the GNU General Public License and which are considered problematic for free software implementations in general by free software groups like the Apache Software Foundation and the Debian project .
The MARID IETF working group stopped their work on the new standard on September 23 2004 because of major differences between the members of the group.
See also
External links
- ASF Position Regarding Sender ID statement from the Apache Software Foundation
- Cat Fight! SPF Claws Sender-ID. In late August, 2005, changes to the Sender-ID Framework experiment triggered a response from the Sender Policy Framework council that threatened doom for both projects. - Email Battles
- Debian project unable to deploy Sender ID statement by the Debian project
- IETF Decides on SPF / Sender-ID issue coverage and discussion on slashdot
- Is Sender ID Dead in the Water? - No MARID Working Group Consensus coverage and discussion on groklaw
- MARID Co-Chairs Clarify Consensus Statement
- MARID to close mailing list thread.
- Open source SenderID module for Apache
- Sender ID Framework Microsoft Corporation
- Two articles on the history of Sender-ID: