Reverse MX: Difference between revisions
Jump to navigation
Jump to search
imported>Hadmut Danisch No edit summary |
imported>Ro Thorpe mNo edit summary |
||
| Line 6: | Line 6: | ||
== Development of RMX == | == Development of RMX == | ||
=== Background and | === Background and motivation === | ||
=== Design | === Design criteria === | ||
=== The | === The concept of Reverse MX records === | ||
=== Publication at the IRTF and IETF === | === Publication at the IRTF and IETF === | ||
== Technical | == Technical description == | ||
=== Implementation as DNS | === Implementation as DNS records === | ||
== Reasons for | == Reasons for failure == | ||
=== SPF and Microsoft's | === SPF and Microsoft's attitudes === | ||
=== IRTF/IETF-specific | === IRTF/IETF-specific reasons === | ||
=== Design flaws of DNS === | === Design flaws of DNS === | ||
=== Design flaws of the SMTP email protocol === | === Design flaws of the SMTP email protocol === | ||
=== Economical | === Economical reasons === | ||
=== Freedom of | === Freedom of speech and cultural reasons === | ||
=== Education === | === Education === | ||
=== Perceptions of | === Perceptions of identity and juristic reasons === | ||
=== Personal and European | === Personal and European reasons === | ||
Revision as of 10:52, 22 November 2009
Reverse MX (RMX) is an email authentication method developed by Hadmut Danisch. It became a basis for the two most commonly used methods - Sender Policy Framework and Sender ID. http://www.danisch.de/work/security/txt/draft-danisch-dns-rr-smtp-04.txt