1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
|
<pre>Internet Engineering Task Force (IETF) J. Levine
Request for Comments: 7505 Taughannock Networks
Category: Standards Track M. Delany
ISSN: 2070-1721 Apple Inc.
June 2015
<span class="h1">A "Null MX" No Service Resource Record for Domains That Accept No Mail</span>
Abstract
Internet mail determines the address of a receiving server through
the DNS, first by looking for an MX record and then by looking for an
A/AAAA record as a fallback. Unfortunately, this means that the
A/AAAA record is taken to be mail server address even when that
address does not accept mail. The No Service MX RR, informally
called "null MX", formalizes the existing mechanism by which a domain
announces that it accepts no mail, without having to provide a mail
server; this permits significant operational efficiencies.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7505">http://www.rfc-editor.org/info/rfc7505</a>.
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Levine & Delany Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7505">RFC 7505</a> Null MX June 2015</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Conventions Used in This Document . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-3">3</a>. MX Resource Records Specifying Null MX . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4">4</a>. Effects of Null MX . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4.1">4.1</a>. SMTP Server Benefits . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4.2">4.2</a>. Sending Mail from Domains That Publish Null MX . . . . . <a href="#page-4">4</a>
<a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-6">6</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-7">7</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-7.1">7.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-7.2">7.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document defines the No Service MX, informally called "null MX",
as a simple mechanism by which a domain can indicate that it does not
accept email.
SMTP clients have a prescribed sequence for identifying a server that
accepts email for a domain. <a href="./rfc5321#section-5">Section 5 of [RFC5321]</a> covers this in
detail; in essence, the SMTP client first looks up a DNS MX RR, and,
if that is not found, it falls back to looking up a DNS A or AAAA RR.
Hence, this overloads a DNS record (that has a different primary
mission) with an email service semantic.
If a domain has no MX records, senders will attempt to deliver mail
to the hosts at the addresses in the domain's A or AAAA records. If
there are no SMTP listeners at the A/AAAA addresses, message delivery
will be attempted repeatedly for a long period, typically a week,
before the sending Mail Transfer Agent (MTA) gives up. This will
delay notification to the sender in the case of misdirected mail and
will consume resources at the sender.
This document defines a null MX that will cause all mail delivery
attempts to a domain to fail immediately, without requiring domains
to create SMTP listeners dedicated to preventing delivery attempts.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions Used in This Document</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="grey">Levine & Delany Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7505">RFC 7505</a> Null MX June 2015</span>
The terms "<a href="./rfc5321">RFC5321</a>.MailFrom" and "<a href="./rfc5322">RFC5322</a>.From" are used as defined
in [<a href="./rfc5598" title=""Internet Mail Architecture"">RFC5598</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. MX Resource Records Specifying Null MX</span>
To indicate that a domain does not accept email, it advertises a
single MX RR (see <a href="./rfc1035#section-3.3.9">Section 3.3.9 of [RFC1035]</a>) with an RDATA section
consisting of preference number 0 and a zero-length label, written in
master files as ".", as the exchange domain, to denote that there
exists no mail exchanger for a domain. Since "." is not a valid host
name, a null MX record cannot be confused with an ordinary MX record.
The use of "." as a pseudo-hostname meaning no service available is
modeled on the SRV RR [<a href="./rfc2782" title=""A DNS RR for specifying the location of services (DNS SRV)"">RFC2782</a>] where it has a similar meaning.
A domain that advertises a null MX MUST NOT advertise any other MX
RR.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Effects of Null MX</span>
The null MX record has a variety of efficiency and usability
benefits.
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. SMTP Server Benefits</span>
Mail often has an incorrect address due to user error, where the
address was mistranscribed or misunderstood, for example, to
alice@www.example.com, alice@example.org, or alice@examp1e.com rather
than alice@example.com. Null MX allows a mail system to report the
delivery failure when the user sends the message, rather than hours
or days later.
Senders of abusive mail often use forged undeliverable return
addresses. Null MX allows Delivery Status Notifications (DSNs) and
other attempted responses to such mail to be disposed of efficiently.
The ability to detect domains that do not accept email offers
resource savings to an SMTP client. It will discover on the first
sending attempt that an address is not deliverable, avoiding queuing
and retries.
When a submission or SMTP relay server rejects an envelope recipient
due to a domain's null MX record, it SHOULD use a 556 reply code
[<a href="./rfc7504" title=""SMTP 521 and 556 Reply Codes"">RFC7504</a>] (Requested action not taken: domain does not accept mail)
and a 5.1.10 enhanced status code (Permanent failure: Recipient
address has null MX).
<span class="grey">Levine & Delany Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7505">RFC 7505</a> Null MX June 2015</span>
A receiving SMTP server that chooses to reject email during the SMTP
conversation that presents an undeliverable <a href="./rfc5321">RFC5321</a>.MailFrom or
<a href="./rfc5322">RFC5322</a>.From domain can be more confident that for other messages a
subsequent attempt to send a DSN or other response will reach a
recipient SMTP server.
SMTP servers that reject mail because a <a href="./rfc5321">RFC5321</a>.MailFrom or
<a href="./rfc5322">RFC5322</a>.From domain has a null MX record SHOULD use a 550 reply code
(Requested action not taken: mailbox unavailable) and a 5.7.27
enhanced status code (Permanent failure: Sender address has null MX).
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Sending Mail from Domains That Publish Null MX</span>
Null MX is primarily intended for domains that do not send or receive
any mail, but have mail sent to them anyway due to mistakes or
malice. Many receiving systems reject mail that has an invalid
return address. Return addresses are needed to allow the sender to
handle message delivery errors. An invalid return address often
signals that the message is spam. Hence, mail systems SHOULD NOT
publish a null MX record for domains that they use in
<a href="./rfc5321">RFC5321</a>.MailFrom or <a href="./rfc5322">RFC5322</a>.From addresses. If a system nonetheless
does so, it risks having its mail rejected.
Operators of domains that do not send mail can publish Sender Policy
Framework (SPF) "-all" policies [<a href="./rfc7208" title=""Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1"">RFC7208</a>] to make an explicit
declaration that the domains send no mail.
Null MX is not intended to be a replacement for the null reverse-path
described in <a href="./rfc5321#section-4.5.5">Section 4.5.5 of RFC 5321</a> and does not change the
meaning or use of a null reverse-path.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
Within the DNS, a null MX RR is an ordinary MX record and presents no
new security issues. If desired, it can be secured in the same
manner as any other DNS record using DNSSEC.
<span class="grey">Levine & Delany Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7505">RFC 7505</a> Null MX June 2015</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
IANA has added the following entries to the "Enumerated Status Codes"
subregistry of the "Simple Mail Transfer Protocol (SMTP) Enhanced
Status Codes Registry".
Code: X.1.10
Sample Text: Recipient address has null MX
Associated basic status code: 556
Description: This status code is returned when the associated
address is marked as invalid using a null MX.
Reference: This document
Submitter: Authors of this document
Change controller: IESG
Code: X.7.27
Sample Text: Sender address has null MX
Associated basic status code: 550
Description: This status code is returned when the associated
sender address has a null MX, and the SMTP
receiver is configured to reject mail from such
sender (e.g., because it could not return a DSN).
Reference: This document
Submitter: Authors of this document
Change controller: IESG
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
[<a id="ref-RFC1035">RFC1035</a>] Mockapetris, P., "Domain names - implementation and
specification", STD 13, <a href="./rfc1035">RFC 1035</a>, DOI 10.17487/RFC1035,
November 1987, <<a href="http://www.rfc-editor.org/info/rfc1035">http://www.rfc-editor.org/info/rfc1035</a>>.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
DOI 10.17487/RFC2119, March 1997,
<<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>>.
[<a id="ref-RFC5321">RFC5321</a>] Klensin, J., "Simple Mail Transfer Protocol", <a href="./rfc5321">RFC 5321</a>,
DOI 10.17487/RFC5321, October 2008,
<<a href="http://www.rfc-editor.org/info/rfc5321">http://www.rfc-editor.org/info/rfc5321</a>>.
[<a id="ref-RFC7504">RFC7504</a>] Klensin, J., "SMTP 521 and 556 Reply Codes", <a href="./rfc7504">RFC 7504</a>,
DOI 10.17487/RFC7504, June 2015,
<<a href="http://www.rfc-editor.org/info/rfc7504">http://www.rfc-editor.org/info/rfc7504</a>>.
<span class="grey">Levine & Delany Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7505">RFC 7505</a> Null MX June 2015</span>
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
[<a id="ref-RFC2782">RFC2782</a>] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for
specifying the location of services (DNS SRV)", <a href="./rfc2782">RFC 2782</a>,
DOI 10.17487/RFC2782, February 2000,
<<a href="http://www.rfc-editor.org/info/rfc2782">http://www.rfc-editor.org/info/rfc2782</a>>.
[<a id="ref-RFC5598">RFC5598</a>] Crocker, D., "Internet Mail Architecture", <a href="./rfc5598">RFC 5598</a>,
DOI 10.17487/RFC5598, July 2009,
<<a href="http://www.rfc-editor.org/info/rfc5598">http://www.rfc-editor.org/info/rfc5598</a>>.
[<a id="ref-RFC7208">RFC7208</a>] Kitterman, S., "Sender Policy Framework (SPF) for
Authorizing Use of Domains in Email, Version 1", <a href="./rfc7208">RFC 7208</a>,
DOI 10.17487/RFC7208, April 2014,
<<a href="http://www.rfc-editor.org/info/rfc7208">http://www.rfc-editor.org/info/rfc7208</a>>.
Acknowledgements
We thank Dave Crocker for his diligent and lengthy shepherding of
this document, and members of the APPSAWG working group for their
constructive suggestions.
Authors' Addresses
John Levine
Taughannock Networks
PO Box 727
Trumansburg, NY 14886
United States
Phone: +1 831 480 2300
Email: standards@taugh.com
URI: <a href="http://jl.ly">http://jl.ly</a>
Mark Delany
Apple Inc.
1 Infinite Loop
Cupertino, CA 95014
United States
Email: mx0dot@yahoo.com
Levine & Delany Standards Track [Page 6]
</pre>
|
