A NULL MX Resource Record for Domains that Accept No Mail
draft-delany-nullmx-01
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Authors | John R. Levine , Mark Delany | ||
Last updated | 2014-01-03 (Latest revision 2013-07-02) | ||
Replaced by | draft-ietf-appsawg-nullmx, draft-ietf-appsawg-nullmx, RFC 7505 | ||
RFC stream | (None) | ||
Formats | |||
Additional resources | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
When the 5321.MailFrom domain in an e-mail message has a DNS MX Resource Record (RR), it is making an explicit statement that it is willing to accept email. However, when the domain has just a DNS A or AAAA RR, there mail clients cannot easily tell whether the domain accepts mail, as many hosts on the Internet advertise an A or AAAA RR regardless of whether they want to accept email. The NULL MX RR formalizes the existing mechanism by which a domain announces that it accepts no mail.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)