A NULL MX Resource Record means "I never accept email"
draft-delany-nullmx-00
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Author | Mark Delany | ||
Last updated | 2005-04-06 | ||
Replaced by | draft-ietf-appsawg-nullmx, draft-ietf-appsawg-nullmx, RFC 7505 | ||
RFC stream | (None) | ||
Formats | |||
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
A common strategy of SMTP servers when deciding whether to accept an email or not, is to ensure that the 2821.MailFrom contains a domain willing to accept non-delivery email (aka bounces). When the 2821.MailFrom domain 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 is no such clarity as most hosts on the Internet advertise an A RR regardless of whether they want to accept email or not. The NULL MX RR formalizes the existing mechanism by which a domain communicates that it will never accept email.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)