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
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
|
<pre>Internet Engineering Task Force (IETF) D. Margolis
Request for Comments: 8461 M. Risher
Category: Standards Track Google, Inc.
ISSN: 2070-1721 B. Ramakrishnan
Oath, Inc.
A. Brotman
Comcast, Inc.
J. Jones
Microsoft, Inc.
September 2018
<span class="h1">SMTP MTA Strict Transport Security (MTA-STS)</span>
Abstract
SMTP MTA Strict Transport Security (MTA-STS) is a mechanism enabling
mail service providers (SPs) to declare their ability to receive
Transport Layer Security (TLS) secure SMTP connections and to specify
whether sending SMTP servers should refuse to deliver to MX hosts
that do not offer TLS with a trusted server certificate.
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="./rfc7841#section-2">Section 2 of RFC 7841</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc8461">https://www.rfc-editor.org/info/rfc8461</a>.
<span class="grey">Margolis, et al. Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
Copyright Notice
Copyright (c) 2018 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="https://trustee.ietf.org/license-info">https://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">Margolis, et al. Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-1.1">1.1</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2">2</a>. Related Technologies . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3">3</a>. Policy Discovery . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.1">3.1</a>. MTA-STS TXT Records . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3.2">3.2</a>. MTA-STS Policies . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-3.3">3.3</a>. HTTPS Policy Fetching . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-3.4">3.4</a>. Policy Selection for Smart Hosts and Subdomains . . . . . <a href="#page-11">11</a>
<a href="#section-4">4</a>. Policy Validation . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-4.1">4.1</a>. MX Host Validation . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-4.2">4.2</a>. Recipient MTA Certificate Validation . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-5">5</a>. Policy Application . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-5.1">5.1</a>. Policy Application Control Flow . . . . . . . . . . . . . <a href="#page-13">13</a>
<a href="#section-6">6</a>. Reporting Failures . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
<a href="#section-7">7</a>. Interoperability Considerations . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-7.1">7.1</a>. SNI Support . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-7.2">7.2</a>. Minimum TLS Version Support . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-8">8</a>. Operational Considerations . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-8.1">8.1</a>. Policy Updates . . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-8.2">8.2</a>. Policy Delegation . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-8.3">8.3</a>. Removing MTA-STS . . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
<a href="#section-8.4">8.4</a>. Preserving MX Candidate Traversal . . . . . . . . . . . . <a href="#page-17">17</a>
<a href="#section-9">9</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
<a href="#section-9.1">9.1</a>. Well-Known URIs Registry . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
<a href="#section-9.2">9.2</a>. MTA-STS TXT Record Fields . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
<a href="#section-9.3">9.3</a>. MTA-STS Policy Fields . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
<a href="#section-10">10</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
<a href="#section-10.1">10.1</a>. Obtaining a Signed Certificate . . . . . . . . . . . . . <a href="#page-18">18</a>
<a href="#section-10.2">10.2</a>. Preventing Policy Discovery . . . . . . . . . . . . . . <a href="#page-19">19</a>
<a href="#section-10.3">10.3</a>. Denial of Service . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
<a href="#section-10.4">10.4</a>. Weak Policy Constraints . . . . . . . . . . . . . . . . <a href="#page-20">20</a>
<a href="#section-10.5">10.5</a>. Compromise of the Web PKI System . . . . . . . . . . . . <a href="#page-20">20</a>
<a href="#section-11">11</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
<a href="#section-11.1">11.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
<a href="#section-11.2">11.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-23">23</a>
<a href="#appendix-A">Appendix A</a>. MTA-STS Example Record and Policy . . . . . . . . . <a href="#page-25">25</a>
<a href="#appendix-B">Appendix B</a>. Message Delivery Pseudocode . . . . . . . . . . . . <a href="#page-25">25</a>
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-28">28</a>
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-29">29</a>
<span class="grey">Margolis, et al. Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The STARTTLS extension to SMTP [<a href="./rfc3207" title=""SMTP Service Extension for Secure SMTP over Transport Layer Security"">RFC3207</a>] allows SMTP clients and
hosts to negotiate the use of a TLS channel for encrypted mail
transmission.
While this opportunistic encryption protocol by itself provides a
high barrier against passive man-in-the-middle traffic interception,
any attacker who can delete parts of the SMTP session (such as the
"250 STARTTLS" response) or who can redirect the entire SMTP session
(perhaps by overwriting the resolved MX record of the delivery
domain) can perform downgrade or interception attacks.
This document defines a mechanism for recipient domains to publish
policies, via a combination of DNS and HTTPS, specifying:
o whether MTAs sending mail to this domain can expect PKIX-
authenticated TLS support
o what a conforming client should do with messages when TLS cannot
be successfully negotiated
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
<a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>] [<a href="./rfc8174" title=""Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"">RFC8174</a>] when, and only when, they appear in all
capitals, as shown here.
We also define the following terms for further use in this document:
o MTA-STS Policy: A commitment by the Policy Domain to support TLS
authenticated with PKIX [<a href="./rfc5280" title=""Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC5280</a>] for the specified MX hosts.
o Policy Domain: The domain for which an MTA-STS Policy is defined.
This is the next-hop domain; when sending mail to
"alice@example.com", this would ordinarily be "example.com", but
this may be overridden by explicit routing rules (as described in
<a href="#section-3.4">Section 3.4</a>, "Policy Selection for Smart Hosts and Subdomains").
o Policy Host: The HTTPS host that serves the MTA-STS Policy for a
Policy Domain. Rules for constructing the hostname are described
in <a href="#section-3.2">Section 3.2</a>, "MTA-STS Policies".
o Sender or Sending MTA: The SMTP MTA sending an email message.
<span class="grey">Margolis, et al. Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
o ABNF: Augmented Backus-Naur Form, a syntax for formally specifying
syntax, defined in [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>] and [<a href="./rfc7405" title=""Case-Sensitive String Support in ABNF"">RFC7405</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Related Technologies</span>
The DNS-Based Authentication of a Named Entities (DANE) TLSA record
[<a href="./rfc7672" title=""SMTP Security via Opportunistic DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS)"">RFC7672</a>] is similar, in that DANE is also designed to upgrade
unauthenticated encryption or plaintext transmission into
authenticated, downgrade-resistant encrypted transmission. DANE
requires DNSSEC [<a href="./rfc4033" title=""DNS Security Introduction and Requirements"">RFC4033</a>] for authentication; the mechanism described
here instead relies on certification authorities (CAs) and does not
require DNSSEC, at a cost of risking malicious downgrades. For a
thorough discussion of this trade-off, see <a href="#section-10">Section 10</a>, "Security
Considerations".
In addition, MTA-STS provides an optional testing-only mode, enabling
soft deployments to detect policy failures; partial deployments can
be achieved in DANE by deploying TLSA records only for some of a
domain's MXes, but such a mechanism is not possible for the per-
domain policies used by MTA-STS.
The primary motivation of MTA-STS is to provide a mechanism for
domains to ensure transport security even when deploying DNSSEC is
undesirable or impractical. However, MTA-STS is designed not to
interfere with DANE deployments when the two overlap; in particular,
senders who implement MTA-STS validation MUST NOT allow MTA-STS
Policy validation to override a failing DANE validation.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Policy Discovery</span>
MTA-STS policies are distributed via HTTPS from a "well-known"
[<a href="./rfc5785" title=""Defining Well-Known Uniform Resource Identifiers (URIs)"">RFC5785</a>] path served within the Policy Domain, and their presence
and current version are indicated by a TXT record at the Policy
Domain. These TXT records additionally contain a policy "id" field,
allowing Sending MTAs to check that a cached policy is still current
without performing an HTTPS request.
To discover if a recipient domain implements MTA-STS, a sender need
only resolve a single TXT record. To see if an updated policy is
available for a domain for which the sender has a previously cached
policy, the sender need only check the TXT record's version "id"
against the cached value.
<span class="grey">Margolis, et al. Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. MTA-STS TXT Records</span>
The MTA-STS TXT record is a TXT record with the name "_mta-sts" at
the Policy Domain. For the domain "example.com", this record would
be "_mta-sts.example.com". MTA-STS TXT records MUST be US-ASCII,
semicolon-separated key/value pairs containing the following fields:
o "v" (plaintext, required): Currently, only "STSv1" is supported.
o "id" (plaintext, required): A short string used to track policy
updates. This string MUST uniquely identify a given instance of a
policy, such that senders can determine when the policy has been
updated by comparing to the "id" of a previously seen policy.
There is no implied ordering of "id" fields between revisions.
An example TXT record is as below:
_mta-sts.example.com. IN TXT "v=STSv1; id=20160831085700Z;"
The formal definition of the "_mta-sts" TXT record, defined using
ABNF [<a href="./rfc7405" title=""Case-Sensitive String Support in ABNF"">RFC7405</a>], is as follows:
sts-text-record = sts-version 1*(sts-field-delim sts-field)
[sts-field-delim]
sts-field = sts-id / ; Note that sts-id record
sts-extension ; is required.
sts-field-delim = *WSP ";" *WSP
sts-version = %s"v=STSv1"
sts-id = %s"id=" 1*32(ALPHA / DIGIT) ; id=...
sts-extension = sts-ext-name "=" sts-ext-value ; name=value
sts-ext-name = (ALPHA / DIGIT)
*31(ALPHA / DIGIT / "_" / "-" / ".")
sts-ext-value = 1*(%x21-3A / %x3C / %x3E-7E)
; chars excluding "=", ";", SP, and CTLs
The TXT record MUST begin with the sts-version field; the order of
other fields is not significant. If multiple TXT records for
"_mta-sts" are returned by the resolver, records that do not begin
with "v=STSv1;" are discarded. If the number of resulting records is
not one, or if the resulting record is syntactically invalid, senders
MUST assume the recipient domain does not have an available MTA-STS
<span class="grey">Margolis, et al. Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
Policy and skip the remaining steps of policy discovery. (Note that
the absence of a usable TXT record is not by itself sufficient to
remove a sender's previously cached policy for the Policy Domain, as
discussed in <a href="#section-5.1">Section 5.1</a>, "Policy Application Control Flow".) If the
resulting TXT record contains multiple strings, then the record MUST
be treated as if those strings are concatenated without adding
spaces.
The "_mta-sts" record MAY return a CNAME that points (directly or via
other CNAMEs) to a TXT record, in which case senders MUST follow the
CNAME pointers. This can be used for policy delegation, as described
in <a href="#section-8.2">Section 8.2</a>.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. MTA-STS Policies</span>
The policy itself is a set of key/value pairs (similar to header
fields in [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>]) served via the HTTPS GET method from the fixed
"well-known" [<a href="./rfc5785" title=""Defining Well-Known Uniform Resource Identifiers (URIs)"">RFC5785</a>] path of ".well-known/mta-sts.txt" served by
the Policy Host. The Policy Host DNS name is constructed by
prepending "mta-sts" to the Policy Domain.
Thus, for a Policy Domain of "example.com", the full URL is
"https://mta-sts.example.com/.well-known/mta-sts.txt".
When fetching a policy, senders SHOULD validate that the media type
is "text/plain" to guard against cases where web servers allow
untrusted users to host non-text content (typically, HTML or images)
at a user-defined path. All parameters other than charset=utf-8 or
charset=us-ascii are ignored. Additional "Content-Type" parameters
are also ignored.
This resource contains the following CRLF-separated key/value pairs:
o "version": Currently, only "STSv1" is supported.
o "mode": One of "enforce", "testing", or "none", indicating the
expected behavior of a Sending MTA in the case of a policy
validation failure. See <a href="#section-5">Section 5</a>, "Policy Application", for more
details about the three modes.
o "max_age": Max lifetime of the policy (plaintext non-negative
integer seconds, maximum value of 31557600). Well-behaved clients
SHOULD cache a policy for up to this value from the last policy
fetch time. To mitigate the risks of attacks at policy refresh
time, it is expected that this value typically be in the range of
weeks or greater.
<span class="grey">Margolis, et al. Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
o "mx": Allowed MX patterns. One or more patterns matching allowed
MX hosts for the Policy Domain. As an example,
mx: mail.example.com <CRLF>
mx: *.example.net
indicates that mail for this domain might be handled by MX
"mail.example.com" or any MX at "example.net". Valid patterns can be
either fully specified names ("example.com") or suffixes prefixed by
a wildcard ("*.example.net"). If a policy specifies more than one
MX, each MX MUST have its own "mx:" key, and each MX key/value pair
MUST be on its own line in the policy file. In the case of
Internationalized Domain Names [<a href="./rfc5891" title=""Internationalized Domain Names in Applications (IDNA): Protocol"">RFC5891</a>], the "mx" value MUST specify
the Punycode-encoded A-label [<a href="./rfc3492" title=""Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA)"">RFC3492</a>] to match against, and not the
Unicode-encoded U-label. The full semantics of certificate
validation (including the use of wildcard patterns) are described in
<a href="#section-4.1">Section 4.1</a>, "MX Host Validation".
An example policy is as below:
version: STSv1
mode: enforce
mx: mail.example.com
mx: *.example.net
mx: backupmx.example.com
max_age: 604800
The formal definition of the policy resource, defined using ABNF
[<a href="./rfc7405" title=""Case-Sensitive String Support in ABNF"">RFC7405</a>], is as follows:
sts-policy-record = sts-policy-field *WSP
*(sts-policy-term sts-policy-field *WSP)
[sts-policy-term]
sts-policy-field = sts-policy-version / ; required once
sts-policy-mode / ; required once
sts-policy-max-age / ; required once
sts-policy-mx /
; required at least once, except when
; mode is "none"
sts-policy-extension ; other fields
sts-policy-field-delim = ":" *WSP
sts-policy-version = sts-policy-version-field sts-policy-field-delim
sts-policy-version-value
sts-policy-version-field = %s"version"
<span class="grey">Margolis, et al. Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
sts-policy-version-value = %s"STSv1"
sts-policy-mode = sts-policy-mode-field sts-policy-field-delim
sts-policy-mode-value
sts-policy-mode-field = %s"mode"
sts-policy-mode-value = %s"testing" / %s"enforce" / %s"none"
sts-policy-mx = sts-policy-mx-field sts-policy-field-delim
sts-policy-mx-value
sts-policy-mx-field = %s"mx"
sts-policy-mx-value = ["*."] Domain
sts-policy-max-age = sts-policy-max-age-field sts-policy-field-delim
sts-policy-max-age-value
sts-policy-max-age-field = %s"max_age"
sts-policy-max-age-value = 1*10(DIGIT)
sts-policy-extension = sts-policy-ext-name ; additional
sts-policy-field-delim ; extension
sts-policy-ext-value ; fields
sts-policy-ext-name = (sts-policy-alphanum)
*31(sta-policy-alphanum / "_" / "-" / ".")
sts-policy-term = LF / CRLF
sts-policy-ext-value = sts-policy-vchar
[*(%x20 / sts-policy-vchar)
sts-policy-vchar]
; chars, including UTF-8 [<a href="./rfc3629" title=""UTF-8, a transformation format of ISO 10646"">RFC3629</a>],
; excluding CTLs and no
; leading/trailing spaces
sts-policy-alphanum = ALPHA / DIGIT
sts-policy-vchar = %x21-7E / UTF8-2 / UTF8-3 / UTF8-4
UTF8-2 = <Defined in <a href="./rfc3629#section-4">Section 4 of [RFC3629]</a>>
UTF8-3 = <Defined in <a href="./rfc3629#section-4">Section 4 of [RFC3629]</a>>
UTF8-4 = <Defined in <a href="./rfc3629#section-4">Section 4 of [RFC3629]</a>>
<span class="grey">Margolis, et al. Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
Domain = <Defined in <a href="./rfc5321#section-4.1.2">Section 4.1.2 of [RFC5321]</a>>
Parsers MUST accept TXT records and policy files that are
syntactically valid (i.e., valid key/value pairs separated by
semicolons for TXT records), possibly containing additional key/value
pairs not specified in this document, in which case unknown fields
SHALL be ignored. If any non-repeated field -- i.e., all fields
excepting "mx" -- is duplicated, all entries except for the first
SHALL be ignored.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. HTTPS Policy Fetching</span>
Policy bodies are, as described above, retrieved by Sending MTAs via
HTTPS [<a href="./rfc2818" title=""HTTP Over TLS"">RFC2818</a>]. During the TLS handshake initiated to fetch a new
or updated policy from the Policy Host, the Policy Host HTTPS server
MUST present an X.509 certificate that is valid for the "mta-sts"
DNS-ID [<a href="./rfc6125" title=""Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)"">RFC6125</a>] (e.g., "mta-sts.example.com") as described below,
chain to a root CA that is trusted by the Sending MTA, and be non-
expired. It is expected that Sending MTAs use a set of trusted CAs
similar to those in widely deployed web browsers and operating
systems. See [<a href="./rfc5280" title=""Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC5280</a>] for more details about certificate
verification.
The certificate is valid for the Policy Host (i.e., "mta-sts"
prepended to the Policy Domain) with respect to the rules described
in [<a href="./rfc6125" title=""Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)"">RFC6125</a>], with the following application-specific considerations:
o Matching is performed only against the DNS-ID identifiers.
o DNS domain names in server certificates MAY contain the wildcard
character '*' as the complete left-most label within the
identifier.
The certificate MAY be checked for revocation via the Online
Certificate Status Protocol (OCSP) [<a href="./rfc6960" title=""X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP"">RFC6960</a>], certificate revocation
lists (CRLs), or some other mechanism.
Policies fetched via HTTPS are only valid if the HTTP response code
is 200 (OK). HTTP 3xx redirects MUST NOT be followed, and HTTP
caching (as specified in [<a href="./rfc7234" title=""Hypertext Transfer Protocol (HTTP/1.1): Caching"">RFC7234</a>]) MUST NOT be used.
Senders may wish to rate-limit the frequency of attempts to fetch the
HTTPS endpoint even if a valid TXT record for the recipient domain
exists. In the case where the HTTPS GET fails, implementers SHOULD
limit further attempts to a period of five minutes or longer per
version ID, to avoid overwhelming resource-constrained recipients
with cascading failures.
<span class="grey">Margolis, et al. Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
Senders MAY impose a timeout on the HTTPS GET and/or a limit on the
maximum size of the response body to avoid long delays or resource
exhaustion during attempted policy updates. A suggested timeout is
one minute, and a suggested maximum policy size is 64 kilobytes;
Policy Hosts SHOULD respond to requests with a complete policy body
within that timeout and size limit.
If a valid TXT record is found but no policy can be fetched via HTTPS
(for any reason), and there is no valid (non-expired) previously
cached policy, senders MUST continue with delivery as though the
domain has not implemented MTA-STS.
Conversely, if no "live" policy can be discovered via DNS or fetched
via HTTPS, but a valid (non-expired) policy exists in the sender's
cache, the sender MUST apply that cached policy.
Finally, to mitigate the risk of persistent interference with policy
refresh, as discussed in-depth in <a href="#section-10">Section 10</a>, MTAs SHOULD proactively
refresh cached policies before they expire; a suggested refresh
frequency is once per day. To enable administrators to discover
problems with policy refresh, MTAs SHOULD alert administrators
(through the use of logs or similar) when such attempts fail, unless
the cached policy mode is "none".
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Policy Selection for Smart Hosts and Subdomains</span>
When sending mail via a "smart host" -- an administratively
configured intermediate SMTP relay, which is different from the
message recipient's server as determined from DNS -- compliant
senders MUST treat the smart host domain as the Policy Domain for the
purposes of policy discovery and application. This specification
does not provide a means of associating policies with email addresses
that employ Address Literals [<a href="./rfc5321" title=""Simple Mail Transfer Protocol"">RFC5321</a>].
When sending mail to a mailbox at a subdomain, compliant senders MUST
NOT attempt to fetch a policy from the parent zone. Thus, for mail
sent to "user@mail.example.com", the policy can be fetched only from
"mail.example.com", not "example.com".
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Policy Validation</span>
When sending to an MX at a domain for which the sender has a valid
and non-expired MTA-STS Policy, a Sending MTA honoring MTA-STS MUST
check whether:
1. At least one of the policy's "mx" patterns matches the selected
MX host, as described in <a href="#section-4.1">Section 4.1</a>, "MX Host Validation".
<span class="grey">Margolis, et al. Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
2. The recipient mail server supports STARTTLS and offers a PKIX-
based TLS certificate, during TLS handshake, which is valid for
that host, as described in <a href="#section-4.2">Section 4.2</a>, "Recipient MTA
Certificate Validation".
When these conditions are not met, a policy is said to fail to
validate. This section does not dictate the behavior of Sending MTAs
when the above conditions are not met; see <a href="#section-5">Section 5</a>, "Policy
Application", for a description of Sending MTA behavior when policy
validation fails.
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. MX Host Validation</span>
A receiving candidate MX host is valid according to an applied MTA-
STS Policy if the MX record name matches one or more of the "mx"
fields in the applied policy. Matching is identical to the rules
given in [<a href="./rfc6125" title=""Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)"">RFC6125</a>], with the restriction that the wildcard character
'*' may only be used to match the entire left-most label in the
presented identifier. Thus, the mx pattern "*.example.com" matches
"mail.example.com" but not "example.com" or "foo.bar.example.com".
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Recipient MTA Certificate Validation</span>
The certificate presented by the receiving MTA MUST not be expired
and MUST chain to a root CA that is trusted by the Sending MTA. The
certificate MUST have a subject alternative name (SAN) [<a href="./rfc5280" title=""Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC5280</a>] with
a DNS-ID [<a href="./rfc6125" title=""Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)"">RFC6125</a>] matching the hostname, per the rules given in
[<a href="./rfc6125" title=""Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)"">RFC6125</a>]. The MX's certificate MAY also be checked for revocation
via OCSP [<a href="./rfc6960" title=""X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP"">RFC6960</a>], CRLs [<a href="./rfc6818" title=""Updates to the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC6818</a>], or some other mechanism.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Policy Application</span>
When sending to an MX at a domain for which the sender has a valid,
non-expired MTA-STS Policy, a Sending MTA honoring MTA-STS applies
the result of a policy validation failure in one of two ways,
depending on the value of the policy "mode" field:
1. "enforce": In this mode, Sending MTAs MUST NOT deliver the
message to hosts that fail MX matching or certificate validation
or that do not support STARTTLS.
2. "testing": In this mode, Sending MTAs that also implement the
TLSRPT (TLS Reporting) specification [<a href="./rfc8460" title=""SMTP TLS Reporting"">RFC8460</a>] send a report
indicating policy application failures (as long as TLSRPT is also
implemented by the recipient domain); in any case, messages may
be delivered as though there were no MTA-STS validation failure.
<span class="grey">Margolis, et al. Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
3. "none": In this mode, Sending MTAs should treat the Policy Domain
as though it does not have any active policy; see <a href="#section-8.3">Section 8.3</a>,
"Removing MTA-STS", for use of this mode value.
When a message fails to deliver due to an "enforce" policy, a
compliant MTA MUST NOT permanently fail to deliver messages before
checking, via DNS, for the presence of an updated policy at the
Policy Domain. (In all cases, MTAs SHOULD treat such failures as
transient errors and retry delivery later.) This allows implementing
domains to update long-lived policies on the fly.
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Policy Application Control Flow</span>
An example control flow for a compliant sender consists of the
following steps:
1. Check for a cached policy whose time-since-fetch has not exceeded
its "max_age". If none exists, attempt to fetch a new policy
(perhaps asynchronously, so as not to block message delivery).
Optionally, Sending MTAs may unconditionally check for a new
policy at this step.
2. For each candidate MX, in order of MX priority, attempt to
deliver the message. If a policy is present with an "enforce"
mode, when attempting to deliver to each candidate MX, ensure
STARTTLS support and host identity validity as described in
<a href="#section-4">Section 4</a>, "Policy Validation". If a candidate fails validation,
continue to the next candidate (if there is one).
3. A message delivery attempt MUST NOT be permanently failed until
the sender has first checked for the presence of a new policy (as
indicated by the "id" field in the "_mta-sts" TXT record). If a
new policy is not found, existing rules for the case of temporary
message delivery failures apply (as discussed in <a href="./rfc5321#section-4.5.4.1">[RFC5321],
Section 4.5.4.1</a>).
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Reporting Failures</span>
MTA-STS is intended to be used along with TLSRPT [<a href="./rfc8460" title=""SMTP TLS Reporting"">RFC8460</a>] in order
to ensure that implementing domains can detect cases of both benign
and malicious failures and to ensure that failures that indicate an
active attack are discoverable. As such, senders that also implement
TLSRPT SHOULD treat the following events as reportable failures:
o HTTPS policy fetch failures when a valid TXT record is present.
o Policy fetch failures of any kind when a valid policy exists in
the policy cache, except if that policy's mode is "none".
<span class="grey">Margolis, et al. Standards Track [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
o Delivery attempts in which a contacted MX does not support
STARTTLS or does not present a certificate that validates
according to the applied policy, except if that policy's mode is
"none".
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Interoperability Considerations</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. SNI Support</span>
To ensure that the server sends the right certificate chain, the SMTP
client MUST have support for the TLS Server Name Indication (SNI)
extension [<a href="./rfc6066" title=""Transport Layer Security (TLS) Extensions: Extension Definitions"">RFC6066</a>]. When connecting to an HTTP server to retrieve
the MTA-STS Policy, the SNI extension MUST contain the name of the
Policy Host (e.g., "mta-sts.example.com"). When connecting to an
SMTP server, the SNI extension MUST contain the MX hostname.
HTTP servers used to deliver MTA-STS policies MAY rely on SNI to
determine which certificate chain to present to the client. HTTP
servers MUST respond with a certificate chain that matches the policy
hostname or abort the TLS handshake if unable to do so. Clients that
do not send SNI information may not see the expected certificate
chain.
SMTP servers MAY rely on SNI to determine which certificate chain to
present to the client. However, servers that have one identity and a
single matching certificate do not require SNI support. Servers MUST
NOT enforce the use of SNI by clients, as the client may be using
unauthenticated opportunistic TLS and may not expect any particular
certificate from the server. If the client sends no SNI extension or
sends an SNI extension for an unsupported server name, the server
MUST simply send a fallback certificate chain of its choice. The
reason for not enforcing strict matching of the requested SNI
hostname is that MTA-STS TLS clients may be typically willing to
accept multiple server names but can only send one name in the SNI
extension. The server's fallback certificate may match a different
name that is acceptable to the client, e.g., the original next-hop
domain.
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Minimum TLS Version Support</span>
MTAs supporting MTA-STS MUST have support for TLS 1.2 [<a href="./rfc5246" title=""The Transport Layer Security (TLS) Protocol Version 1.2"">RFC5246</a>] or
TLS 1.3 [<a href="./rfc8446" title=""The Transport Layer Security (TLS) Protocol Version 1.3"">RFC8446</a>] or higher. The general TLS usage guidance in
[<a href="./rfc7525" title=""Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)"">RFC7525</a>] SHOULD be followed.
<span class="grey">Margolis, et al. Standards Track [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Operational Considerations</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Policy Updates</span>
Updating the policy requires that the owner make changes in two
places: the "_mta-sts" TXT record in the Policy Domain's DNS zone and
at the corresponding HTTPS endpoint. As a result, recipients should
expect that a policy will continue to be used by senders until both
the HTTPS and TXT endpoints are updated and the TXT record's TTL has
passed.
In other words, a sender who is unable to successfully deliver a
message while applying a cache of the recipient's now-outdated policy
may be unable to discover that a new policy exists until the DNS TTL
has passed. Recipients SHOULD therefore ensure that old policies
continue to work for message delivery during this period of time, or
risk message delays.
Recipients SHOULD also update the HTTPS policy body before updating
the TXT record; this ordering avoids the risk that senders, seeing a
new TXT record, mistakenly cache the old policy from HTTPS.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Policy Delegation</span>
Domain owners commonly delegate SMTP hosting to a different
organization, such as an ISP or a web host. In such a case, they may
wish to also delegate the MTA-STS Policy to the same organization,
which can be accomplished with two changes.
First, the Policy Domain must point the "_mta-sts" record, via CNAME,
to the "_mta-sts" record maintained by the provider. This allows the
provider to control update signaling.
Second, the Policy Domain must point the "well-known" policy location
to the provider. This can be done either by setting the "mta-sts"
record to an IP address or CNAME specified by the provider and by
giving the provider a TLS certificate that is valid for that host or
by setting up a "reverse proxy" (also known as a "gateway") server
for the Policy Domain's Policy Host, configured to serve proxied
responses from the Policy Host of the provider.
For example, given a user domain "user.example" hosted by a mail
provider "provider.example", the following configuration would allow
policy delegation:
DNS:
_mta-sts.user.example. IN CNAME _mta-sts.provider.example.
<span class="grey">Margolis, et al. Standards Track [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
Policy:
> GET /.well-known/mta-sts.txt Host: mta-sts.user.example
< HTTP/1.1 200 OK # Response proxies content from
# <a href="https://mta-sts.provider.example">https://mta-sts.provider.example</a>
Note that in all such cases, the policy endpoint
("<a href="https://mta-sts.user.example/.well-known/mta-sts.txt">https://mta-sts.user.example/.well-known/mta-sts.txt</a>" in this
example) must still present a certificate valid for the Policy Host
("mta-sts.user.example"), and not for that host at the provider's
domain ("mta-sts.provider.example").
Note that while Sending MTAs MUST NOT use HTTP caching when fetching
policies via HTTPS, such caching may nonetheless be useful to a
reverse proxy configured as described in this section. An HTTPS
policy endpoint expecting to be proxied for multiple hosted domains
-- as with a large mail hosting provider or similar -- may wish to
indicate an HTTP Cache-Control "max-age" response directive (as
specified in [<a href="./rfc7234" title=""Hypertext Transfer Protocol (HTTP/1.1): Caching"">RFC7234</a>]) of 60 seconds as a reasonable value to save
reverse proxies an unnecessarily high-rate of proxied policy
fetching.
<span class="h3"><a class="selflink" id="section-8.3" href="#section-8.3">8.3</a>. Removing MTA-STS</span>
In order to facilitate clean opt-out of MTA-STS by implementing
Policy Domains, and to distinguish clearly between failures that
indicate attacks and those that indicate such opt-outs, MTA-STS
implements the "none" mode, which allows validated policies to
indicate authoritatively that the Policy Domain wishes to no longer
implement MTA-STS and may, in the future, remove the MTA-STS TXT and
policy endpoints entirely.
A suggested workflow to implement such an opt out is as follows:
1. Publish a new policy with "mode" equal to "none" and a small
"max_age" (e.g., one day).
2. Publish a new TXT record to trigger fetching of the new policy.
3. When all previously served policies have expired -- normally this
is the time the previously published policy was last served plus
that policy's "max_age", but note that policies older than the
previously published policy may have been served with a greater
"max_age" than the previously published policy, allowing
overlapping policy caches -- safely remove the TXT record and
HTTPS endpoint.
<span class="grey">Margolis, et al. Standards Track [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
<span class="h3"><a class="selflink" id="section-8.4" href="#section-8.4">8.4</a>. Preserving MX Candidate Traversal</span>
Implementers of send-time MTA-STS validation in mail transfer agents
should take note of the risks of modifying the logic of traversing MX
candidate lists. Because an MTA-STS Policy can be used to prefilter
invalid MX candidates from the MX candidate list, it is tempting to
implement a "two-pass" model, where MX candidates are first filtered
for possible validity according to the MTA-STS Policy, and then the
remaining candidates are attempted in order as without an MTA-STS
Policy. This may lead to incorrect implementations, such as message
loops; instead, it is recommended that implementers traverse the MX
candidate list as usual, and treat invalid candidates as though they
were unreachable (i.e., as though there were some transient error
when trying to deliver to that candidate).
One consequence of validating MX hosts in order of ordinary candidate
traversal is that in the event a higher-priority MX is MTA-STS valid
and a lower-priority MX is not, senders may never encounter the
lower-priority MX, leading to a risk that policy misconfigurations
that apply only to "backup" MXes may only be discovered in the case
of primary MX failure.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. IANA Considerations</span>
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Well-Known URIs Registry</span>
A new "well-known" URI as described in <a href="#section-3">Section 3</a> has been registered
in the "Well-Known URIs" registry as described below:
URI Suffix: mta-sts.txt
Change Controller: IETF
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. MTA-STS TXT Record Fields</span>
IANA has created a new registry titled "MTA-STS TXT Record Fields".
The initial entries in the registry are:
+------------+--------------------+-------------------------+
| Field Name | Description | Reference |
+------------+--------------------+-------------------------+
| v | Record version | <a href="./rfc8461#section-3.1">Section 3.1 of RFC 8461</a> |
| id | Policy instance ID | <a href="./rfc8461#section-3.1">Section 3.1 of RFC 8461</a> |
+------------+--------------------+-------------------------+
New fields are added to this registry using IANA's "Expert Review"
policy [<a href="./rfc8126" title="">RFC8126</a>].
<span class="grey">Margolis, et al. Standards Track [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
<span class="h3"><a class="selflink" id="section-9.3" href="#section-9.3">9.3</a>. MTA-STS Policy Fields</span>
IANA has created a new registry titled "MTA-STS Policy Fields". The
initial entries in the registry are:
+------------+----------------------+-------------------------+
| Field Name | Description | Reference |
+------------+----------------------+-------------------------+
| version | Policy version | <a href="./rfc8461#section-3.2">Section 3.2 of RFC 8461</a> |
| mode | Enforcement behavior | <a href="./rfc8461#section-3.2">Section 3.2 of RFC 8461</a> |
| max_age | Policy lifetime | <a href="./rfc8461#section-3.2">Section 3.2 of RFC 8461</a> |
| mx | MX identities | <a href="./rfc8461#section-3.2">Section 3.2 of RFC 8461</a> |
+------------+----------------------+-------------------------+
New fields are added to this registry using IANA's "Expert Review"
policy.
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Security Considerations</span>
SMTP MTA-STS attempts to protect against an active attacker trying to
intercept or tamper with mail between hosts that support STARTTLS.
There are two classes of attacks considered:
o Foiling TLS negotiation (for example, by deleting the "250
STARTTLS" response from a server or altering TLS session
negotiation). This would result in the SMTP session occurring
over plaintext, despite both parties supporting TLS.
o Impersonating the destination mail server, whereby the sender
might deliver the message to an impostor, who could then monitor
and/or modify messages despite opportunistic TLS. This
impersonation could be accomplished by spoofing the DNS MX record
for the recipient domain or by redirecting client connections
intended for the legitimate recipient server (for example, by
altering BGP routing tables).
MTA-STS can thwart such attacks only if the sender is able to
previously obtain and cache a policy for the recipient domain, and
only if the attacker is unable to obtain a valid certificate that
complies with that policy. Below, we consider specific attacks on
this model.
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Obtaining a Signed Certificate</span>
SMTP MTA-STS relies on certificate validation via PKIX-based TLS
identity checking [<a href="./rfc6125" title=""Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)"">RFC6125</a>]. Attackers who are able to obtain a
valid certificate for the targeted recipient mail service (e.g., by
compromising a CA) are thus able to circumvent STS authentication.
<span class="grey">Margolis, et al. Standards Track [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Preventing Policy Discovery</span>
Since MTA-STS uses DNS TXT records for policy discovery, an attacker
who is able to block DNS responses can suppress the discovery of an
MTA-STS Policy, making the Policy Domain appear not to have an MTA-
STS Policy. The sender policy cache is designed to resist this
attack by decreasing the frequency of policy discovery and thus
reducing the window of vulnerability; it is nonetheless a risk that
attackers who can predict or induce policy discovery -- for example,
by inducing a sending domain to send mail to a never-before-contacted
recipient while carrying out a man-in-the-middle attack -- may be
able to foil policy discovery and effectively downgrade the security
of the message delivery.
Since this attack depends upon intercepting initial policy discovery,
implementers SHOULD prefer policy "max_age" values to be as long as
is practical.
Because this attack is also possible upon refresh of a cached policy,
implementers SHOULD NOT wait until a cached policy has expired before
checking for an update; if senders attempt to refresh the cache
regularly (for example, by fetching the current live policy in a
background task that runs daily or weekly, regardless of the state of
the "_mta-sts" TXT record, and updating their cache's "max age"
accordingly), an attacker would have to foil policy discovery
consistently over the lifetime of a cached policy to prevent a
successful refresh.
Additionally, MTAs SHOULD alert administrators to repeated policy
refresh failures long before cached policies expire (through warning
logs or similar applicable mechanisms), allowing administrators to
detect such a persistent attack on policy refresh. (However, they
should not implement such alerts if the cached policy has a "none"
mode, to allow clean MTA-STS removal, as described in <a href="#section-8.3">Section 8.3</a>.)
Resistance to downgrade attacks of this nature -- due to the ability
to authoritatively determine "lack of a record" even for non-
participating recipients -- is a feature of DANE, due to its use of
DNSSEC for policy discovery.
<span class="h3"><a class="selflink" id="section-10.3" href="#section-10.3">10.3</a>. Denial of Service</span>
We additionally consider the Denial-of-Service risk posed by an
attacker who can modify the DNS records for a recipient domain.
Absent MTA-STS, such an attacker can cause a Sending MTA to cache
invalid MX records, but only for however long the sending resolver
caches those records. With MTA-STS, the attacker can additionally
advertise a new, long "max_age" MTA-STS Policy with "mx" constraints
<span class="grey">Margolis, et al. Standards Track [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
that validate the malicious MX record, causing senders to cache the
policy and refuse to deliver messages once the victim has resecured
the MX records.
This attack is mitigated in part by the ability of a victim domain to
(at any time) publish a new policy updating the cached, malicious
policy, though this does require the victim domain to both obtain a
valid CA-signed certificate and to understand and properly configure
MTA-STS.
Similarly, we consider the possibility of domains that deliberately
allow untrusted users to serve untrusted content on user-specified
subdomains. In some cases (e.g., the service "tumblr.com"), this
takes the form of providing HTTPS hosting of user-registered
subdomains; in other cases (e.g. dynamic DNS providers), this takes
the form of allowing untrusted users to register custom DNS records
at the provider's domain.
In these cases, there is a risk that untrusted users would be able to
serve custom content at the "mta-sts" host, including serving an
illegitimate MTA-STS Policy. We believe this attack is rendered more
difficult by the need for the attacker to also serve the "_mta-sts"
TXT record on the same domain -- something not, to our knowledge,
widely provided to untrusted users. This attack is additionally
mitigated by the aforementioned ability for a victim domain to update
an invalid policy at any future date.
<span class="h3"><a class="selflink" id="section-10.4" href="#section-10.4">10.4</a>. Weak Policy Constraints</span>
Even if an attacker cannot modify a served policy, the potential
exists for configurations that allow attackers on the same domain to
receive mail for that domain. For example, an easy configuration
option when authoring an MTA-STS Policy for "example.com" is to set
the "mx" equal to "*.example.com"; in this case, recipient domains
must consider the risk that any user possessing a valid hostname and
CA-signed certificate (for example, "dhcp-123.example.com") will,
from the perspective of MTA-STS Policy validation, be a valid MX host
for that domain.
<span class="h3"><a class="selflink" id="section-10.5" href="#section-10.5">10.5</a>. Compromise of the Web PKI System</span>
A number of risks apply to the PKI system that is used for
certificate authentication, both of the "mta-sts" HTTPS host's
certificate and the SMTP servers' certificates. These risks are
broadly applicable within the Web PKI ecosystem and are not specific
to MTA-STS; nonetheless, they deserve some consideration in this
context.
<span class="grey">Margolis, et al. Standards Track [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
Broadly speaking, attackers may compromise the system by obtaining
certificates under fraudulent circumstances (i.e., by impersonating
the legitimate owner of the victim domain), by compromising a CA or
Delegate Authority's private keys, by obtaining a legitimate
certificate issued to the victim domain, and similar.
One approach commonly employed by web browsers to help mitigate
against some of these attacks is to allow for revocation of
compromised or fraudulent certificates via OCSP [<a href="./rfc6960" title=""X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP"">RFC6960</a>] or CRLs
[<a href="./rfc6818" title=""Updates to the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC6818</a>]. Such mechanisms themselves represent trade-offs and are
not universally implemented; we nonetheless recommend implementers of
MTA-STS to implement revocation mechanisms that are most applicable
to their implementations.
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span>
<span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Normative References</span>
[<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="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>>.
[<a id="ref-RFC2818">RFC2818</a>] Rescorla, E., "HTTP Over TLS", <a href="./rfc2818">RFC 2818</a>,
DOI 10.17487/RFC2818, May 2000,
<<a href="https://www.rfc-editor.org/info/rfc2818">https://www.rfc-editor.org/info/rfc2818</a>>.
[<a id="ref-RFC3207">RFC3207</a>] Hoffman, P., "SMTP Service Extension for Secure SMTP over
Transport Layer Security", <a href="./rfc3207">RFC 3207</a>, DOI 10.17487/RFC3207,
February 2002, <<a href="https://www.rfc-editor.org/info/rfc3207">https://www.rfc-editor.org/info/rfc3207</a>>.
[<a id="ref-RFC3492">RFC3492</a>] Costello, A., "Punycode: A Bootstring encoding of Unicode
for Internationalized Domain Names in Applications
(IDNA)", <a href="./rfc3492">RFC 3492</a>, DOI 10.17487/RFC3492, March 2003,
<<a href="https://www.rfc-editor.org/info/rfc3492">https://www.rfc-editor.org/info/rfc3492</a>>.
[<a id="ref-RFC3629">RFC3629</a>] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, <a href="./rfc3629">RFC 3629</a>, DOI 10.17487/RFC3629, November
2003, <<a href="https://www.rfc-editor.org/info/rfc3629">https://www.rfc-editor.org/info/rfc3629</a>>.
[<a id="ref-RFC5234">RFC5234</a>] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>,
DOI 10.17487/RFC5234, January 2008,
<<a href="https://www.rfc-editor.org/info/rfc5234">https://www.rfc-editor.org/info/rfc5234</a>>.
<span class="grey">Margolis, et al. Standards Track [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
[<a id="ref-RFC5246">RFC5246</a>] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", <a href="./rfc5246">RFC 5246</a>,
DOI 10.17487/RFC5246, August 2008,
<<a href="https://www.rfc-editor.org/info/rfc5246">https://www.rfc-editor.org/info/rfc5246</a>>.
[<a id="ref-RFC5280">RFC5280</a>] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,
Housley, R., and W. Polk, "Internet X.509 Public Key
Infrastructure Certificate and Certificate Revocation List
(CRL) Profile", <a href="./rfc5280">RFC 5280</a>, DOI 10.17487/RFC5280, May 2008,
<<a href="https://www.rfc-editor.org/info/rfc5280">https://www.rfc-editor.org/info/rfc5280</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="https://www.rfc-editor.org/info/rfc5321">https://www.rfc-editor.org/info/rfc5321</a>>.
[<a id="ref-RFC5785">RFC5785</a>] Nottingham, M. and E. Hammer-Lahav, "Defining Well-Known
Uniform Resource Identifiers (URIs)", <a href="./rfc5785">RFC 5785</a>,
DOI 10.17487/RFC5785, April 2010,
<<a href="https://www.rfc-editor.org/info/rfc5785">https://www.rfc-editor.org/info/rfc5785</a>>.
[<a id="ref-RFC6066">RFC6066</a>] Eastlake 3rd, D., "Transport Layer Security (TLS)
Extensions: Extension Definitions", <a href="./rfc6066">RFC 6066</a>,
DOI 10.17487/RFC6066, January 2011,
<<a href="https://www.rfc-editor.org/info/rfc6066">https://www.rfc-editor.org/info/rfc6066</a>>.
[<a id="ref-RFC6125">RFC6125</a>] Saint-Andre, P. and J. Hodges, "Representation and
Verification of Domain-Based Application Service Identity
within Internet Public Key Infrastructure Using X.509
(PKIX) Certificates in the Context of Transport Layer
Security (TLS)", <a href="./rfc6125">RFC 6125</a>, DOI 10.17487/RFC6125, March
2011, <<a href="https://www.rfc-editor.org/info/rfc6125">https://www.rfc-editor.org/info/rfc6125</a>>.
[<a id="ref-RFC7405">RFC7405</a>] Kyzivat, P., "Case-Sensitive String Support in ABNF",
<a href="./rfc7405">RFC 7405</a>, DOI 10.17487/RFC7405, December 2014,
<<a href="https://www.rfc-editor.org/info/rfc7405">https://www.rfc-editor.org/info/rfc7405</a>>.
[<a id="ref-RFC7525">RFC7525</a>] Sheffer, Y., Holz, R., and P. Saint-Andre,
"Recommendations for Secure Use of Transport Layer
Security (TLS) and Datagram Transport Layer Security
(DTLS)", <a href="https://www.rfc-editor.org/bcp/bcp195">BCP 195</a>, <a href="./rfc7525">RFC 7525</a>, DOI 10.17487/RFC7525, May
2015, <<a href="https://www.rfc-editor.org/info/rfc7525">https://www.rfc-editor.org/info/rfc7525</a>>.
[<a id="ref-RFC8174">RFC8174</a>] Leiba, B., "Ambiguity of Uppercase vs Lowercase in <a href="./rfc2119">RFC</a>
<a href="./rfc2119">2119</a> Key Words", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc8174">RFC 8174</a>, DOI 10.17487/RFC8174,
May 2017, <<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>>.
<span class="grey">Margolis, et al. Standards Track [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
[<a id="ref-RFC8446">RFC8446</a>] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", <a href="./rfc8446">RFC 8446</a>, DOI 10.17487/RFC8446, August 2018,
<<a href="https://www.rfc-editor.org/info/rfc8446">https://www.rfc-editor.org/info/rfc8446</a>>.
[<a id="ref-RFC8460">RFC8460</a>] Margolis, D., Brotman, A., Ramakrishnan, B., Jones, J.,
and M. Risher, "SMTP TLS Reporting", <a href="./rfc8460">RFC 8460</a>,
DOI 10.17487/RFC8460, September 2018,
<<a href="https://www.rfc-editor.org/info/rfc8460">https://www.rfc-editor.org/info/rfc8460</a>>.
<span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Informative References</span>
[<a id="ref-RFC4033">RFC4033</a>] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "DNS Security Introduction and Requirements",
<a href="./rfc4033">RFC 4033</a>, DOI 10.17487/RFC4033, March 2005,
<<a href="https://www.rfc-editor.org/info/rfc4033">https://www.rfc-editor.org/info/rfc4033</a>>.
[<a id="ref-RFC5322">RFC5322</a>] Resnick, P., Ed., "Internet Message Format", <a href="./rfc5322">RFC 5322</a>,
DOI 10.17487/RFC5322, October 2008,
<<a href="https://www.rfc-editor.org/info/rfc5322">https://www.rfc-editor.org/info/rfc5322</a>>.
[<a id="ref-RFC5891">RFC5891</a>] Klensin, J., "Internationalized Domain Names in
Applications (IDNA): Protocol", <a href="./rfc5891">RFC 5891</a>,
DOI 10.17487/RFC5891, August 2010,
<<a href="https://www.rfc-editor.org/info/rfc5891">https://www.rfc-editor.org/info/rfc5891</a>>.
[<a id="ref-RFC6818">RFC6818</a>] Yee, P., "Updates to the Internet X.509 Public Key
Infrastructure Certificate and Certificate Revocation List
(CRL) Profile", <a href="./rfc6818">RFC 6818</a>, DOI 10.17487/RFC6818, January
2013, <<a href="https://www.rfc-editor.org/info/rfc6818">https://www.rfc-editor.org/info/rfc6818</a>>.
[<a id="ref-RFC6960">RFC6960</a>] Santesson, S., Myers, M., Ankney, R., Malpani, A.,
Galperin, S., and C. Adams, "X.509 Internet Public Key
Infrastructure Online Certificate Status Protocol - OCSP",
<a href="./rfc6960">RFC 6960</a>, DOI 10.17487/RFC6960, June 2013,
<<a href="https://www.rfc-editor.org/info/rfc6960">https://www.rfc-editor.org/info/rfc6960</a>>.
[<a id="ref-RFC7234">RFC7234</a>] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
<a href="./rfc7234">RFC 7234</a>, DOI 10.17487/RFC7234, June 2014,
<<a href="https://www.rfc-editor.org/info/rfc7234">https://www.rfc-editor.org/info/rfc7234</a>>.
[<a id="ref-RFC7672">RFC7672</a>] Dukhovni, V. and W. Hardaker, "SMTP Security via
Opportunistic DNS-Based Authentication of Named Entities
(DANE) Transport Layer Security (TLS)", <a href="./rfc7672">RFC 7672</a>,
DOI 10.17487/RFC7672, October 2015,
<<a href="https://www.rfc-editor.org/info/rfc7672">https://www.rfc-editor.org/info/rfc7672</a>>.
<span class="grey">Margolis, et al. Standards Track [Page 23]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
[<a id="ref-RFC8126">RFC8126</a>] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>,
<a href="./rfc8126">RFC 8126</a>, DOI 10.17487/RFC8126, June 2017,
<<a href="https://www.rfc-editor.org/info/rfc8126">https://www.rfc-editor.org/info/rfc8126</a>>.
<span class="grey">Margolis, et al. Standards Track [Page 24]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. MTA-STS Example Record and Policy</span>
The owner of "example.com" wishes to begin using MTA-STS with a
policy that will solicit reports from senders without affecting how
the messages are processed, in order to verify the identity of MXes
that handle mail for "example.com", confirm that TLS is correctly
used, and ensure that certificates presented by the recipient MX
validate.
MTA-STS Policy indicator TXT RR:
_mta-sts.example.com. IN TXT "v=STSv1; id=20160831085700Z;"
MTA-STS Policy file served as the response body at
"https://mta-sts.example.com/.well-known/mta-sts.txt":
version: STSv1
mode: testing
mx: mx1.example.com
mx: mx2.example.com
mx: mx.backup-example.com
max_age: 1296000
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. Message Delivery Pseudocode</span>
Below is pseudocode demonstrating the logic of a compliant Sending
MTA.
While this pseudocode implementation suggests synchronous policy
retrieval in the delivery path, that may be undesirable in a working
implementation, and we expect some implementers to instead prefer a
background fetch that does not block delivery when no cached policy
is present.
func isEnforce(policy) {
// Return true if the policy mode is "enforce".
}
func isNonExpired(policy) {
// Return true if the policy is not expired.
}
func tryStartTls(connection) {
// Attempt to open an SMTP STARTTLS connection with the MX.
}
func certMatches(connection, host) {
<span class="grey">Margolis, et al. Standards Track [Page 25]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
// Assume a handy function to return if the server
// certificate presented in "connection" is valid for "host".
}
func policyMatches(candidate, policy) {
for mx in policy.mx {
// Literal match.
if mx == candidate {
return true
}
// Wildcard matches only the leftmost label.
// Wildcards must always be followed by a '.'.
if mx[0] == '*' {
parts = SplitN(candidate, '.', 2) // Split on the first '.'.
if len(parts) > 1 && parts[1] == mx[2:] {
return true
}
}
}
return false
}
func tryDeliverMail(connection, message) {
// Attempt to deliver "message" via "connection".
}
func tryGetNewPolicy(domain) {
// Check for an MTA-STS TXT record for "domain" in DNS, and return
// the indicated policy.
}
func cachePolicy(domain, policy) {
// Store "policy" as the cached policy for "domain".
}
func tryGetCachedPolicy(domain) {
// Return a cached policy for "domain".
}
func reportError(error) {
// Report an error via TLSRPT.
}
func tryMxAccordingTo(message, mx, policy) {
connection := connect(mx)
if !connection {
return false // Can't connect to the MX, so it's not an MTA-STS
// error.
<span class="grey">Margolis, et al. Standards Track [Page 26]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
}
secure := true
if !policyMatches(mx, policy) {
secure = false
reportError(E_HOST_MISMATCH)
} else if !tryStartTls(connection) {
secure = false
reportError(E_NO_VALID_TLS)
} else if !certMatches(connection, policy) {
secure = false
reportError(E_CERT_MISMATCH)
}
if secure || !isEnforce(policy) {
return tryDeliverMail(connection, message)
}
return false
}
func tryWithPolicy(message, domain, policy) {
mxes := getMxForDomain(domain)
for mx in mxes {
if tryMxAccordingTo(message, mx, policy) {
return true
}
}
return false
}
func handleMessage(message) {
domain := ... // domain part after '@' from recipient
policy := tryGetNewPolicy(domain)
if policy {
cachePolicy(domain, policy)
} else {
policy = tryGetCachedPolicy(domain)
}
if policy {
return tryWithPolicy(message, domain, policy)
}
// Try to deliver the message normally (i.e., without MTA-STS).
}
<span class="grey">Margolis, et al. Standards Track [Page 27]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
Contributors
Wei Chuang
Google, Inc.
weihaw@google.com
Viktor Dukhovni
ietf-dane@dukhovni.de
Markus Laber
1&1 Mail & Media Development & Technology GmbH
markus.laber@1und1.de
Nicolas Lidzborski
Google, Inc.
nlidz@google.com
Brandon Long
Google, Inc.
blong@google.com
Franck Martin
LinkedIn, Inc.
fmartin@linkedin.com
Klaus Umbach
1&1 Mail & Media Development & Technology GmbH
klaus.umbach@1und1.de
<span class="grey">Margolis, et al. Standards Track [Page 28]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
<span class="grey"><a href="./rfc8461">RFC 8461</a> MTA-STS September 2018</span>
Authors' Addresses
Daniel Margolis
Google, Inc.
Email: dmargolis@google.com
Mark Risher
Google, Inc.
Email: risher@google.com
Binu Ramakrishnan
Oath, Inc.
Email: prbinu@yahoo.com
Alexander Brotman
Comcast, Inc.
Email: alex_brotman@comcast.com
Janet Jones
Microsoft, Inc.
Email: janet.jones@microsoft.com
Margolis, et al. Standards Track [Page 29]
</pre>
|
