git » spf » next » tree

[next] / testdata / rfc4408-tests.yml

   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
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
# This is the openspf.org test suite (release 2009.10) based on RFC 4408.
# http://www.openspf.org/Test_Suite
#
# $Id$
# vim:sw=2 sts=2 et
#
# See rfc4408-tests.CHANGES for a changelog.
#
# Contributors:
#   Stuart D Gathman    90% of the tests
#   Julian Mehnle       some tests, proofread YAML syntax, formal schema
#   Frank Ellermann
#   Scott Kitterman
#   Wayne Schlitt
#   Craig Whitmore
#   Norman Maurer
#   Mark Shewmaker
#   Philip Gladstone
#
# While the test suite is designed for all types of implementations, it only
# needs to explicitly concern itself with SPF-only (type 99) and TXT-only
# implementations.  This is because while an implementation may support both,
# it must use only one record type for a given query - see 4.5/5.  If an
# implementation finds SPF (type 99) records and decides to use them, they
# override TXT, and it must ignore any TXT records.  Note that an
# implementation may decide whether to use SPF records on a case by case basis.
# Maybe it looks TXT and SPF up in parallel and goes with the first result to
# come back.  Or maybe one is cached already.  Or maybe it chooses at random.
# Think of dual SPF/TXT implementations as a quantum superposition of SPF-only
# and TXT-only.  It must collapse to one or the other on each observation to be
# compliant.
#
# The "Selecting records" test section is the only one concerned with weeding
# out (incorrect) mixed behaviour and checking for proper response to duplicate
# or conflicting records.  Other sections rely on auto-magic duplication
# of SPF to TXT records (by test suite drivers) to test all implementation
# types with one specification.
#
---
description: Initial processing
tests:
  toolonglabel:
    description: >-
      DNS labels limited to 63 chars.
    comment: >-
      For initial processing, a long label results in None, not TempError
    spec: 4.3/1
    helo: mail.example.net
    host: 1.2.3.5
    mailfrom: lyme.eater@A123456789012345678901234567890123456789012345678901234567890123.example.com
    result: none
  longlabel:
    description: >-
      DNS labels limited to 63 chars.
    spec: 4.3/1
    helo: mail.example.net
    host: 1.2.3.5
    mailfrom: lyme.eater@A12345678901234567890123456789012345678901234567890123456789012.example.com
    result: fail
  emptylabel:
    spec: 4.3/1
    helo: mail.example.net
    host: 1.2.3.5
    mailfrom: lyme.eater@A...example.com
    result: none
  helo-not-fqdn:
    spec: 4.3/1
    helo: A2345678
    host: 1.2.3.5
    mailfrom: ""
    result: none
  helo-domain-literal:
    spec: 4.3/1
    helo: "[1.2.3.5]"
    host: 1.2.3.5
    mailfrom: ""
    result: none
  nolocalpart:
    spec: 4.3/2
    helo: mail.example.net
    host: 1.2.3.4
    mailfrom: '@example.net'
    result: fail
    explanation: postmaster
  domain-literal:
    spec: 4.3/1
    helo: OEMCOMPUTER
    host: 1.2.3.5
    mailfrom: "foo@[1.2.3.5]"
    result: none
  non-ascii-policy:
    description: >-
      SPF policies are restricted to 7-bit ascii.
    spec: 3.1.1/1
    helo: hosed
    host: 1.2.3.4
    mailfrom: "foobar@hosed.example.com"
    result: permerror
    skip: We don't enforce 7-bit ascii.
  non-ascii-mech:
    description: >-
      SPF policies are restricted to 7-bit ascii.
    comment: >-
      Checking a possibly different code path for non-ascii chars.
    spec: 3.1.1/1
    helo: hosed
    host: 1.2.3.4
    mailfrom: "foobar@hosed2.example.com"
    result: permerror
    skip: We don't enforce 7-bit ascii.
  non-ascii-result:
    description: >-
      SPF policies are restricted to 7-bit ascii.
    comment: >-
      Checking yet another code path for non-ascii chars.
    spec: 3.1.1/1
    helo: hosed
    host: 1.2.3.4
    mailfrom: "foobar@hosed3.example.com"
    result: permerror
  non-ascii-non-spf:
    description: >-
      Non-ascii content in non-SPF related records.
    comment: >-
      Non-SPF related TXT records are none of our business.  (But what about SPF records?)
    spec: 3.1.1/1
    helo: hosed
    host: 1.2.3.4
    mailfrom: "foobar@nothosed.example.com"
    result: fail
    explanation: DEFAULT
  two-spaces:
    description: >-
      ABNF for term separation is one or more spaces, not just one.
    spec: 4.6.1
    helo: hosed
    host: 1.2.3.4
    mailfrom: "actually@fine.example.com"
    result: fail
zonedata:
  example.com:
    - TIMEOUT: true
  example.net:
    - SPF:  v=spf1 -all exp=exp.example.net
  a.example.net:
    - SPF:  v=spf1 -all exp=exp.example.net
  exp.example.net:
    - TXT:  '%{l}'
  a12345678901234567890123456789012345678901234567890123456789012.example.com:
    - SPF:  v=spf1 -all
  hosed.example.com:
    - SPF:  "v=spf1 a:\xEF\xBB\xBFgarbage.example.net -all"
  hosed2.example.com:
    - SPF:  "v=spf1 \x80a:example.net -all"
  hosed3.example.com:
    - SPF:  "v=spf1 a:example.net \x96all"
  nothosed.example.com:
    - SPF:  "v=spf1 a:example.net -all"
    - SPF:  "\x96"
  fine.example.com:
    - TXT: "v=spf1 a  -all"
---
description: Record lookup
tests:
  both:
    spec: 4.4/1
    helo: mail.example.net
    host: 1.2.3.4
    mailfrom: foo@both.example.net
    result: fail
  txtonly:
    description: Result is none if checking SPF records only.
    spec: 4.4/1
    helo: mail.example.net
    host: 1.2.3.4
    mailfrom: foo@txtonly.example.net
    result: [fail, none]
  spfonly:
    description: Result is none if checking TXT records only.
    spec: 4.4/1
    helo: mail.example.net
    host: 1.2.3.4
    mailfrom: foo@spfonly.example.net
    result: [fail, none]
  spftimeout:
    description: >-
      TXT record present, but SPF lookup times out.
      Result is temperror if checking SPF records only.
    comment: >-
      This actually happens for a popular braindead DNS server.
    spec: 4.4/1
    helo: mail.example.net
    host: 1.2.3.4
    mailfrom: foo@spftimeout.example.net
    result: [fail, temperror]
  txttimeout:
    description: >-
      SPF record present, but TXT lookup times out.
      If only TXT records are checked, result is temperror.
    spec: 4.4/1
    helo: mail.example.net
    host: 1.2.3.4
    mailfrom: foo@txttimeout.example.net
    result: [fail, temperror]
  nospftxttimeout:
    description: >-
      No SPF record present, and TXT lookup times out.
      If only TXT records are checked, result is temperror.
    comment: >-
      Because TXT records is where v=spf1 records will likely be, returning
      temperror will try again later.  A timeout due to a braindead server
      is unlikely in the case of TXT, as opposed to the newer SPF RR.
    spec: 4.4/1
    helo: mail.example.net
    host: 1.2.3.4
    mailfrom: foo@nospftxttimeout.example.net
    result: [temperror, none]
  alltimeout:
    description: Both TXT and SPF queries time out
    spec: 4.4/2
    helo: mail.example.net
    host: 1.2.3.4
    mailfrom: foo@alltimeout.example.net
    result: temperror
zonedata:
  both.example.net:
    - TXT:  v=spf1 -all
    - SPF:  v=spf1 -all
  txtonly.example.net:
    - TXT:  v=spf1 -all
  spfonly.example.net:
    - SPF:  v=spf1 -all
    - TXT:  NONE
  spftimeout.example.net:
    - TXT:  v=spf1 -all
    - TIMEOUT: true
  txttimeout.example.net:
    - SPF:  v=spf1 -all
    - TXT:  NONE
    - TIMEOUT: true
  nospftxttimeout.example.net:
    - SPF:  "v=spf3 !a:yahoo.com -all"
    - TXT:  NONE
    - TIMEOUT: true
  alltimeout.example.net:
    - TIMEOUT: true
---
description: Selecting records
tests:
  nospace1:
    description: >-
      Version must be terminated by space or end of record.  TXT pieces
      are joined without intervening spaces.
    spec: 4.5/4
    helo: mail.example1.com
    host: 1.2.3.4
    mailfrom: foo@example2.com
    result: none
  empty:
    description: Empty SPF record.
    spec: 4.5/4
    helo: mail1.example1.com
    host: 1.2.3.4
    mailfrom: foo@example1.com
    result: neutral
  nospace2:
    spec: 4.5/4
    helo: mail.example1.com
    host: 1.2.3.4
    mailfrom: foo@example3.com
    result: pass
  spfoverride:
    description: >-
      SPF records override TXT records.  Older implementation may
      check TXT records only.
    spec: 4.5/5
    helo: mail.example1.com
    host: 1.2.3.4
    mailfrom: foo@example4.com
    result: [pass, fail]
  multitxt1:
    description: >-
      Older implementations will give permerror/unknown because of
      the conflicting TXT records.  However, RFC 4408 says the SPF
      records overrides them.
    spec: 4.5/5
    helo: mail.example1.com
    host: 1.2.3.4
    mailfrom: foo@example5.com
    result: [pass, permerror]
  multitxt2:
    description: >-
      Multiple records is a permerror, v=spf1 is case insensitive
    spec: 4.5/6
    helo: mail.example1.com
    host: 1.2.3.4
    mailfrom: foo@example6.com
    result: permerror
  multispf1:
    description: >-
      Multiple records is a permerror, even when they are identical.
      However, this situation cannot be reliably reproduced with live
      DNS since cache and resolvers are allowed to combine identical
      records.
    spec: 4.5/6
    helo: mail.example1.com
    host: 1.2.3.4
    mailfrom: foo@example7.com
    result: [permerror, fail]
  multispf2:
    description: >-
      Older implementations ignoring SPF-type records will give pass because
      there is a (single) TXT record.  But RFC 4408 requires permerror because
      the SPF records override and there are more than one.
    spec: 4.5/6
    helo: mail.example1.com
    host: 1.2.3.4
    mailfrom: foo@example8.com
    result: [permerror, pass]
  nospf:
    spec: 4.5/7
    helo: mail.example1.com
    host: 1.2.3.4
    mailfrom: foo@mail.example1.com
    result: none
  case-insensitive:
    description: >-
      v=spf1 is case insensitive
    spec: 4.5/6
    helo: mail.example1.com
    host: 1.2.3.4
    mailfrom: foo@example9.com
    result: softfail
zonedata:
  example3.com:
    - SPF:  v=spf10
    - SPF:  v=spf1 mx
    - MX:   [0, mail.example1.com]
  example1.com:
    - SPF:  v=spf1
  example2.com:
    - SPF:  ['v=spf1', 'mx']
  mail.example1.com:
    - A:    1.2.3.4
  example4.com:
    - SPF:  v=spf1 +all
    - TXT:  v=spf1 -all
  example5.com:
    - SPF:  v=spf1 +all
    - TXT:  v=spf1 -all
    - TXT:  v=spf1 +all
  example6.com:
    - SPF:  v=spf1 -all
    - SPF:  V=sPf1 +all
  example7.com:
    - SPF:  v=spf1 -all
    - SPF:  v=spf1 -all
  example8.com:
    - SPF:  V=spf1 -all
    - SPF:  v=spf1 -all
    - TXT:  v=spf1 +all
  example9.com:
    - SPF:  v=SpF1 ~all
---
description: Record evaluation
tests:
  detect-errors-anywhere:
    description: Any syntax errors anywhere in the record MUST be detected.
    spec: 4.6
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@t1.example.com
    result: permerror
    skip: We don't catch errors after a match.
  modifier-charset-good:
    description: name = ALPHA *( ALPHA / DIGIT / "-" / "_" / "." )
    spec: 4.6.1/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@t2.example.com
    result: pass
    skip: We don't enforce the domain charset.
  modifier-charset-bad1:
    description: >-
      '=' character immediately after the name and before any ":" or "/"
    spec: 4.6.1/4
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@t3.example.com
    result: permerror
  modifier-charset-bad2:
    description: >-
      '=' character immediately after the name and before any ":" or "/"
    spec: 4.6.1/4
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@t4.example.com
    result: permerror
  redirect-after-mechanisms1:
    description: >-
      The "redirect" modifier has an effect after all the mechanisms.
    comment: >-
      The redirect in this example would violate processing limits, except
      that it is never used because of the all mechanism.
    spec: 4.6.3
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@t5.example.com
    result: softfail
  redirect-after-mechanisms2:
    description: >-
      The "redirect" modifier has an effect after all the mechanisms.
    spec: 4.6.3
    helo: mail.example.com
    host: 1.2.3.5
    mailfrom: foo@t6.example.com
    result: fail
    skip: Not worth the complexity of erroring on this.
  default-result:
    description: Default result is neutral.
    spec: 4.7/1
    helo: mail.example.com
    host: 1.2.3.5
    mailfrom: foo@t7.example.com
    result: neutral
  redirect-is-modifier:
    description: |-
      Invalid mechanism.  Redirect is a modifier.
    spec: 4.6.1/4
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@t8.example.com
    result: permerror
    skip: We don't catch errors after a match.
  invalid-domain:
    description: >-
      Domain-spec must end in macro-expand or valid toplabel.
    spec: 8.1/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@t9.example.com
    result: permerror
    skip: We don't enforce TLD structure.
  invalid-domain-empty-label:
    description: >-
      target-name that is a valid domain-spec per RFC 4408 but an invalid
      domain name per RFC 1035 (empty label) must be treated as non-existent.
    comment: >-
      An empty domain label, i.e. two successive dots, in a mechanism
      target-name is valid domain-spec syntax, even though a DNS query cannot
      be composed from it.  The spec being unclear about it, this could either
      be considered a syntax error, or, by analogy to 4.3/1 and 5/10/3, the
      mechanism chould be treated as a no-match.
    spec: [4.3/1, 5/10/3]
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@t10.example.com
    result: [permerror, fail]
  invalid-domain-long:
    description: >-
      target-name that is a valid domain-spec per RFC 4408 but an invalid
      domain name per RFC 1035 (long label) must be treated as non-existent.
    comment: >-
      A domain label longer than 63 characters in a mechanism target-name is
      valid domain-spec syntax, even though a DNS query cannot be composed
      from it.  The spec being unclear about it, this could either be
      considered a syntax error, or, by analogy to 4.3/1 and 5/10/3, the
      mechanism chould be treated as a no-match.
    spec: [4.3/1, 5/10/3]
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@t11.example.com
    result: [permerror,fail]
  invalid-domain-long-via-macro:
    description: >-
      target-name that is a valid domain-spec per RFC 4408 but an invalid
      domain name per RFC 1035 (long label) must be treated as non-existent.
    comment: >-
      A domain label longer than 63 characters that results from macro
      expansion in a mechanism target-name is valid domain-spec syntax (and is
      not even subject to syntax checking after macro expansion), even though
      a DNS query cannot be composed from it.  The spec being unclear about
      it, this could either be considered a syntax error, or, by analogy to
      4.3/1 and 5/10/3, the mechanism chould be treated as a no-match.
    spec: [4.3/1, 5/10/3]
    helo: "%%%%%%%%%%%%%%%%%%%%%%"
    host: 1.2.3.4
    mailfrom: foo@t12.example.com
    result: [permerror,fail]
zonedata:
  mail.example.com:
    - A: 1.2.3.4
  t1.example.com:
    - SPF: v=spf1 ip4:1.2.3.4 -all moo
  t2.example.com:
    - SPF: v=spf1 moo.cow-far_out=man:dog/cat ip4:1.2.3.4 -all
  t3.example.com:
    - SPF: v=spf1 moo.cow/far_out=man:dog/cat ip4:1.2.3.4 -all
  t4.example.com:
    - SPF: v=spf1 moo.cow:far_out=man:dog/cat ip4:1.2.3.4 -all
  t5.example.com:
    - SPF: v=spf1 redirect=t5.example.com ~all
  t6.example.com:
    - SPF: v=spf1 ip4:1.2.3.4 redirect=t2.example.com
  t7.example.com:
    - SPF: v=spf1 ip4:1.2.3.4
  t8.example.com:
    - SPF: v=spf1 ip4:1.2.3.4 redirect:t2.example.com
  t9.example.com:
    - SPF: v=spf1 a:foo-bar -all
  t10.example.com:
    - SPF: v=spf1 a:mail.example...com -all
  t11.example.com:
    - SPF: v=spf1 a:a123456789012345678901234567890123456789012345678901234567890123.example.com -all
  t12.example.com:
    - SPF: v=spf1 a:%{H}.bar -all
---
description: ALL mechanism syntax
tests:
  all-dot:
    description: |
      all              = "all"
    comment: |-
      At least one implementation got this wrong
    spec: 5.1/1
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e1.example.com
    result: permerror
  all-arg:
    description: |
      all              = "all"
    comment: |-
      At least one implementation got this wrong
    spec: 5.1/1
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e2.example.com
    result: permerror
  all-cidr:
    description: |
      all              = "all"
    spec: 5.1/1
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e3.example.com
    result: permerror
  all-neutral:
    description: |
      all              = "all"
    spec: 5.1/1
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e4.example.com
    result: neutral
  all-double:
    description: |
      all              = "all"
    spec: 5.1/1
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e5.example.com
    result: pass
zonedata:
  mail.example.com:
    - A: 1.2.3.4
  e1.example.com:
    - SPF: v=spf1 -all.
  e2.example.com:
    - SPF: v=spf1 -all:foobar
  e3.example.com:
    - SPF: v=spf1 -all/8
  e4.example.com:
    - SPF: v=spf1 ?all
  e5.example.com:
    - SPF: v=spf1 all -all
---
description: PTR mechanism syntax
tests:
  ptr-cidr:
    description: |-
      PTR              = "ptr"    [ ":" domain-spec ]
    spec: 5.5/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e1.example.com
    result: permerror
  ptr-match-target:
    description: >-
      Check all validated domain names to see if they end in the <target-name>
      domain.
    spec: 5.5/5
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e2.example.com
    result: pass
  ptr-match-implicit:
    description: >-
      Check all validated domain names to see if they end in the <target-name>
      domain.
    spec: 5.5/5
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e3.example.com
    result: pass
  ptr-nomatch-invalid:
    description: >-
      Check all validated domain names to see if they end in the <target-name>
      domain.
    comment: >-
      This PTR record does not validate
    spec: 5.5/5
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e4.example.com
    result: fail
  ptr-match-ip6:
    description: >-
      Check all validated domain names to see if they end in the <target-name>
      domain.
    spec: 5.5/5
    helo: mail.example.com
    host: CAFE:BABE::1
    mailfrom: foo@e3.example.com
    result: pass
  ptr-empty-domain:
    description: >-
      domain-spec cannot be empty.
    spec: 5.5/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e5.example.com
    result: permerror
zonedata:
  mail.example.com:
    - A: 1.2.3.4
  e1.example.com:
    - SPF: v=spf1 ptr/0 -all
  e2.example.com:
    - SPF: v=spf1 ptr:example.com -all
  4.3.2.1.in-addr.arpa:
    - PTR: e3.example.com
    - PTR: e4.example.com
    - PTR: mail.example.com
  1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.E.B.A.B.E.F.A.C.ip6.arpa:
    - PTR: e3.example.com
  e3.example.com:
    - SPF: v=spf1 ptr -all
    - A: 1.2.3.4
    - AAAA: CAFE:BABE::1
  e4.example.com:
    - SPF: v=spf1 ptr -all
  e5.example.com:
    - SPF: "v=spf1 ptr:"
---
description: A mechanism syntax
tests:
  a-cidr6:
    description: |
      A                = "a"      [ ":" domain-spec ] [ dual-cidr-length ]
      dual-cidr-length = [ ip4-cidr-length ] [ "/" ip6-cidr-length ]
    spec: 5.3/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e6.example.com
    result: fail
  a-bad-cidr4:
    description: |
      A                = "a"      [ ":" domain-spec ] [ dual-cidr-length ]
      dual-cidr-length = [ ip4-cidr-length ] [ "/" ip6-cidr-length ]
    spec: 5.3/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e6a.example.com
    result: permerror
  a-bad-cidr6:
    description: |
      A                = "a"      [ ":" domain-spec ] [ dual-cidr-length ]
      dual-cidr-length = [ ip4-cidr-length ] [ "/" ip6-cidr-length ]
    spec: 5.3/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e7.example.com
    result: permerror
  a-dual-cidr-ip4-match:
    description: |
      A                = "a"      [ ":" domain-spec ] [ dual-cidr-length ]
      dual-cidr-length = [ ip4-cidr-length ] [ "/" ip6-cidr-length ]
    spec: 5.3/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e8.example.com
    result: pass
  a-dual-cidr-ip4-err:
    description: |
      A                = "a"      [ ":" domain-spec ] [ dual-cidr-length ]
      dual-cidr-length = [ ip4-cidr-length ] [ "/" ip6-cidr-length ]
    spec: 5.3/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e8e.example.com
    result: permerror
  a-dual-cidr-ip6-match:
    description: |
      A                = "a"      [ ":" domain-spec ] [ dual-cidr-length ]
      dual-cidr-length = [ ip4-cidr-length ] [ "/" ip6-cidr-length ]
    spec: 5.3/2
    helo: mail.example.com
    host: 2001:db8:1234::cafe:babe
    mailfrom: foo@e8.example.com
    result: pass
  a-dual-cidr-ip4-default:
    description: |
      A                = "a"      [ ":" domain-spec ] [ dual-cidr-length ]
      dual-cidr-length = [ ip4-cidr-length ] [ "/" ip6-cidr-length ]
    spec: 5.3/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e8b.example.com
    result: fail
  a-dual-cidr-ip6-default:
    description: |
      A                = "a"      [ ":" domain-spec ] [ dual-cidr-length ]
      dual-cidr-length = [ ip4-cidr-length ] [ "/" ip6-cidr-length ]
    spec: 5.3/2
    helo: mail.example.com
    host: 2001:db8:1234::cafe:babe
    mailfrom: foo@e8a.example.com
    result: fail
  a-multi-ip1:
    description: >-
      A matches any returned IP.
    spec: 5.3/3
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e10.example.com
    result: pass
  a-multi-ip2:
    description: >-
      A matches any returned IP.
    spec: 5.3/3
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e10.example.com
    result: pass
  a-bad-domain:
    description: >-
      domain-spec must pass basic syntax checks;
      a ':' may appear in domain-spec, but not in top-label
    spec: 8.1/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e9.example.com
    result: permerror
    skip: We don't enforce domain charset.
  a-nxdomain:
    description: >-
      If no ips are returned, A mechanism does not match, even with /0.
    spec: 5.3/3
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e1.example.com
    result: fail
  a-cidr4-0:
    description: >-
      Matches if any A records are present in DNS.
    spec: 5.3/3
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e2.example.com
    result: pass
  a-cidr4-0-ip6:
    description: >-
      Matches if any A records are present in DNS.
    spec: 5.3/3
    helo: mail.example.com
    host: 1234::1
    mailfrom: foo@e2.example.com
    result: fail
  a-cidr6-0-ip4:
    description: >-
      Would match if any AAAA records are present in DNS,
      but not for an IP4 connection.
    spec: 5.3/3
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e2a.example.com
    result: fail
  a-cidr6-0-ip4mapped:
    description: >-
      Would match if any AAAA records are present in DNS,
      but not for an IP4 connection.
    spec: 5.3/3
    helo: mail.example.com
    host: ::FFFF:1.2.3.4
    mailfrom: foo@e2a.example.com
    result: fail
  a-cidr6-0-ip6:
    description: >-
      Matches if any AAAA records are present in DNS.
    spec: 5.3/3
    helo: mail.example.com
    host: 1234::1
    mailfrom: foo@e2a.example.com
    result: pass
  a-ip6-dualstack:
    description: >-
      Simple IP6 Address match with dual stack.
    spec: 5.3/3
    helo: mail.example.com
    host: 1234::1
    mailfrom: foo@ipv6.example.com
    result: pass
  a-cidr6-0-nxdomain:
    description: >-
      No match if no AAAA records are present in DNS.
    spec: 5.3/3
    helo: mail.example.com
    host: 1234::1
    mailfrom: foo@e2b.example.com
    result: fail
  a-null:
    description: >-
      Null octets not allowed in toplabel
    spec: 8.1/2
    helo: mail.example.com
    host: 1.2.3.5
    mailfrom: foo@e3.example.com
    result: permerror
    skip: We don't enforce charset.
  a-numeric:
    description: >-
      toplabel may not be all numeric
    comment: >-
      A common publishing mistake is using ip4 addresses with A mechanism.
      This should receive special diagnostic attention in the permerror.
    spec: 8.1/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e4.example.com
    result: permerror
    skip: We don't enforce domain structure.
  a-numeric-toplabel:
    description: >-
      toplabel may not be all numeric
    spec: 8.1/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e5.example.com
    result: permerror
    skip: We don't enforce TLD structure.
  a-dash-in-toplabel:
    description: >-
      toplabel may contain dashes
    comment: >-
      Going from the "toplabel" grammar definition, an implementation using
      regular expressions in incrementally parsing SPF records might
      erroneously try to match a TLD such as ".xn--zckzah" (cf. IDN TLDs!) to
      '( *alphanum ALPHA *alphanum )' first before trying the alternative
      '( 1*alphanum "-" *( alphanum / "-" ) alphanum )', essentially causing
      a non-greedy, and thus, incomplete match.  Make sure a greedy match is
      performed!
    spec: 8.1/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e14.example.com
    result: pass
  a-bad-toplabel:
    description: >-
      toplabel may not begin with a dash
    spec: 8.1/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e12.example.com
    result: permerror
    skip: We don't enforce TLD structure.
  a-only-toplabel:
    description: >-
      domain-spec may not consist of only a toplabel.
    spec: 8.1/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e5a.example.com
    result: permerror
    skip: We don't enforce TLD structure.
  a-only-toplabel-trailing-dot:
    description: >-
      domain-spec may not consist of only a toplabel.
    comment: >-
      "A trailing dot doesn't help."
    spec: 8.1/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e5b.example.com
    result: permerror
    skip: We don't enforce TLD structure.
  a-colon-domain:
    description: >-
      domain-spec may contain any visible char except %
    spec: 8.1/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e11.example.com
    result: pass
    skip: Allowing / in domain names is not worth the complexity
  a-colon-domain-ip4mapped:
    description: >-
      domain-spec may contain any visible char except %
    spec: 8.1/2
    helo: mail.example.com
    host: ::FFFF:1.2.3.4
    mailfrom: foo@e11.example.com
    result: pass
    skip: Allowing / in domain names is not worth the complexity
  a-empty-domain:
    description: >-
      domain-spec cannot be empty.
    spec: 5.3/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e13.example.com
    result: permerror
    skip: Not worth the complexity of erroring on this.
zonedata:
  mail.example.com:
    - A: 1.2.3.4
  e1.example.com:
    - SPF: v=spf1 a/0 -all
  e2.example.com:
    - A: 1.1.1.1
    - AAAA: 1234::2
    - SPF: v=spf1 a/0 -all
  e2a.example.com:
    - AAAA: 1234::1
    - SPF: v=spf1 a//0 -all
  e2b.example.com:
    - A: 1.1.1.1
    - SPF: v=spf1 a//0 -all
  ipv6.example.com:
    - AAAA: 1234::1
    - A: 1.1.1.1
    - SPF: v=spf1 a -all
  e3.example.com:
    - SPF: "v=spf1 a:foo.example.com\0"
  e4.example.com:
    - SPF: v=spf1 a:111.222.33.44
  e5.example.com:
    - SPF: v=spf1 a:abc.123
  e5a.example.com:
    - SPF: v=spf1 a:museum
  e5b.example.com:
    - SPF: v=spf1 a:museum.
  e6.example.com:
    - SPF: v=spf1 a//33 -all
  e6a.example.com:
    - SPF: v=spf1 a/33 -all
  e7.example.com:
    - SPF: v=spf1 a//129 -all
  e8.example.com:
    - A: 1.2.3.5
    - AAAA: 2001:db8:1234::dead:beef
    - SPF: v=spf1 a/24//64 -all
  e8e.example.com:
    - A: 1.2.3.5
    - AAAA: 2001:db8:1234::dead:beef
    - SPF: v=spf1 a/24/64 -all
  e8a.example.com:
    - A: 1.2.3.5
    - AAAA: 2001:db8:1234::dead:beef
    - SPF: v=spf1 a/24 -all
  e8b.example.com:
    - A: 1.2.3.5
    - AAAA: 2001:db8:1234::dead:beef
    - SPF: v=spf1 a//64 -all
  e9.example.com:
    - SPF: v=spf1 a:example.com:8080
  e10.example.com:
    - SPF: v=spf1 a:foo.example.com/24
  foo.example.com:
    - A: 1.1.1.1
    - A: 1.2.3.5
  e11.example.com:
    - SPF: v=spf1 a:foo:bar/baz.example.com
  foo:bar/baz.example.com:
    - A: 1.2.3.4
  e12.example.com:
    - SPF: v=spf1 a:example.-com
  e13.example.com:
    - SPF: "v=spf1 a:"
  e14.example.com:
    - SPF: "v=spf1 a:foo.example.xn--zckzah -all"
  foo.example.xn--zckzah:
    - A: 1.2.3.4
---
description: Include mechanism semantics and syntax
tests:
  include-fail:
    description: >-
      recursive check_host() result of fail causes include to not match.
    spec: 5.2/9
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e1.example.com
    result: softfail
  include-softfail:
    description: >-
      recursive check_host() result of softfail causes include to not match.
    spec: 5.2/9
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e2.example.com
    result: pass
  include-neutral:
    description: >-
      recursive check_host() result of neutral causes include to not match.
    spec: 5.2/9
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e3.example.com
    result: fail
  include-temperror:
    description: >-
      recursive check_host() result of temperror causes include to temperror
    spec: 5.2/9
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e4.example.com
    result: temperror
  include-permerror:
    description: >-
      recursive check_host() result of permerror causes include to permerror
    spec: 5.2/9
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e5.example.com
    result: permerror
  include-syntax-error:
    description: >-
      include          = "include"  ":" domain-spec
    spec: 5.2/1
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e6.example.com
    result: permerror
  include-cidr:
    description: >-
      include          = "include"  ":" domain-spec
    spec: 5.2/1
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e9.example.com
    result: permerror
  include-none:
    description: >-
      recursive check_host() result of none causes include to permerror
    spec: 5.2/9
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e7.example.com
    result: permerror
  include-empty-domain:
    description: >-
      domain-spec cannot be empty.
    spec: 5.2/1
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e8.example.com
    result: permerror
zonedata:
  mail.example.com:
    - A: 1.2.3.4
  ip5.example.com:
    - SPF: v=spf1 ip4:1.2.3.5 -all
  ip6.example.com:
    - SPF: v=spf1 ip4:1.2.3.6 ~all
  ip7.example.com:
    - SPF: v=spf1 ip4:1.2.3.7 ?all
  ip8.example.com:
    - TIMEOUT: true
  erehwon.example.com:
    - TXT: v=spfl am not an SPF record
  e1.example.com:
    - SPF: v=spf1 include:ip5.example.com ~all
  e2.example.com:
    - SPF: v=spf1 include:ip6.example.com all
  e3.example.com:
    - SPF: v=spf1 include:ip7.example.com -all
  e4.example.com:
    - SPF: v=spf1 include:ip8.example.com -all
  e5.example.com:
    - SPF: v=spf1 include:e6.example.com -all
  e6.example.com:
    - SPF: v=spf1 include +all
  e7.example.com:
    - SPF: v=spf1 include:erehwon.example.com -all
  e8.example.com:
    - SPF: "v=spf1 include: -all"
  e9.example.com:
    - SPF: "v=spf1 include:ip5.example.com/24 -all"
---
description: MX mechanism syntax
tests:
  mx-cidr6:
    description: |
      MX                = "mx"      [ ":" domain-spec ] [ dual-cidr-length ]
      dual-cidr-length = [ ip4-cidr-length ] [ "/" ip6-cidr-length ]
    spec: 5.4/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e6.example.com
    result: fail
  mx-bad-cidr4:
    description: |
      MX                = "mx"      [ ":" domain-spec ] [ dual-cidr-length ]
      dual-cidr-length = [ ip4-cidr-length ] [ "/" ip6-cidr-length ]
    spec: 5.4/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e6a.example.com
    result: permerror
  mx-bad-cidr6:
    description: |
      MX                = "mx"      [ ":" domain-spec ] [ dual-cidr-length ]
      dual-cidr-length = [ ip4-cidr-length ] [ "/" ip6-cidr-length ]
    spec: 5.4/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e7.example.com
    result: permerror
  mx-multi-ip1:
    description: >-
      MX matches any returned IP.
    spec: 5.4/3
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e10.example.com
    result: pass
  mx-multi-ip2:
    description: >-
      MX matches any returned IP.
    spec: 5.4/3
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e10.example.com
    result: pass
  mx-bad-domain:
    description: >-
      domain-spec must pass basic syntax checks
    comment: >-
      A ':' may appear in domain-spec, but not in top-label.
    spec: 8.1/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e9.example.com
    result: permerror
    skip: We don't enforce domain syntax.
  mx-nxdomain:
    description: >-
      If no ips are returned, MX mechanism does not match, even with /0.
    spec: 5.4/3
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e1.example.com
    result: fail
  mx-cidr4-0:
    description: >-
      Matches if any A records for any MX records are present in DNS.
    spec: 5.4/3
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e2.example.com
    result: pass
  mx-cidr4-0-ip6:
    description: >-
      cidr4 doesn't apply to IP6 connections.
    spec: 5.4/3
    helo: mail.example.com
    host: 1234::1
    mailfrom: foo@e2.example.com
    result: fail
  mx-cidr6-0-ip4:
    description: >-
      Would match if any AAAA records for MX records are present in DNS,
      but not for an IP4 connection.
    spec: 5.4/3
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e2a.example.com
    result: fail
  mx-cidr6-0-ip4mapped:
    description: >-
      Would match if any AAAA records for MX records are present in DNS,
      but not for an IP4 connection.
    spec: 5.4/3
    helo: mail.example.com
    host: ::FFFF:1.2.3.4
    mailfrom: foo@e2a.example.com
    result: fail
  mx-cidr6-0-ip6:
    description: >-
      Matches if any AAAA records for any MX records are present in DNS.
    spec: 5.3/3
    helo: mail.example.com
    host: 1234::1
    mailfrom: foo@e2a.example.com
    result: pass
  mx-cidr6-0-nxdomain:
    description: >-
      No match if no AAAA records for any MX records are present in DNS.
    spec: 5.4/3
    helo: mail.example.com
    host: 1234::1
    mailfrom: foo@e2b.example.com
    result: fail
  mx-null:
    description: >-
      Null not allowed in top-label.
    spec: 8.1/2
    helo: mail.example.com
    host: 1.2.3.5
    mailfrom: foo@e3.example.com
    result: permerror
    skip: We don't enforce charset.
  mx-numeric-top-label:
    description: >-
      Top-label may not be all numeric
    spec: 8.1/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e5.example.com
    result: permerror
    skip: We don't validate top-level domains.
  mx-colon-domain:
    description: >-
      Domain-spec may contain any visible char except %
    spec: 8.1/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e11.example.com
    result: pass
    skip: Allowing / in domain names is not worth the complexity
  mx-colon-domain-ip4mapped:
    description: >-
      Domain-spec may contain any visible char except %
    spec: 8.1/2
    helo: mail.example.com
    host: ::FFFF:1.2.3.4
    mailfrom: foo@e11.example.com
    result: pass
    skip: Allowing / in domain names is not worth the complexity
  mx-bad-toplab:
    description: >-
      Toplabel may not begin with -
    spec: 8.1/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e12.example.com
    result: permerror
    skip: We don't enforce TLD structure.
  mx-empty:
    description: >-
      test null MX
    comment: >-
      Some implementations have had trouble with null MX
    spec: 5.4/3
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: ""
    result: neutral
  mx-implicit:
    description: >-
      If the target name has no MX records, check_host() MUST NOT pretend the
      target is its single MX, and MUST NOT default to an A lookup on the
      target-name directly.
    spec: 5.4/4
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e4.example.com
    result: neutral
  mx-empty-domain:
    description: >-
      domain-spec cannot be empty.
    spec: 5.2/1
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e13.example.com
    result: permerror
    skip: Not worth the complexity of erroring on this.
zonedata:
  mail.example.com:
    - A: 1.2.3.4
    - MX: [0, ""]
    - SPF: v=spf1 mx
  e1.example.com:
    - SPF: v=spf1 mx/0 -all
    - MX: [0, e1.example.com]
  e2.example.com:
    - A: 1.1.1.1
    - AAAA: 1234::2
    - MX: [0, e2.example.com]
    - SPF: v=spf1 mx/0 -all
  e2a.example.com:
    - AAAA: 1234::1
    - MX: [0, e2a.example.com]
    - SPF: v=spf1 mx//0 -all
  e2b.example.com:
    - A: 1.1.1.1
    - MX: [0, e2b.example.com]
    - SPF: v=spf1 mx//0 -all
  e3.example.com:
    - SPF: "v=spf1 mx:foo.example.com\0"
  e4.example.com:
    - SPF: v=spf1 mx
    - A: 1.2.3.4
  e5.example.com:
    - SPF: v=spf1 mx:abc.123
  e6.example.com:
    - SPF: v=spf1 mx//33 -all
  e6a.example.com:
    - SPF: v=spf1 mx/33 -all
  e7.example.com:
    - SPF: v=spf1 mx//129 -all
  e9.example.com:
    - SPF: v=spf1 mx:example.com:8080
  e10.example.com:
    - SPF: v=spf1 mx:foo.example.com/24
  foo.example.com:
    - MX: [0, foo1.example.com]
  foo1.example.com:
    - A: 1.1.1.1
    - A: 1.2.3.5
  e11.example.com:
    - SPF: v=spf1 mx:foo:bar/baz.example.com
  foo:bar/baz.example.com:
    - MX: [0, "foo:bar/baz.example.com"]
    - A: 1.2.3.4
  e12.example.com:
    - SPF: v=spf1 mx:example.-com
  e13.example.com:
    - SPF: "v=spf1 mx: -all"
---
description: EXISTS mechanism syntax
tests:
  exists-empty-domain:
    description: >-
      domain-spec cannot be empty.
    spec: 5.7/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e1.example.com
    result: permerror
  exists-implicit:
    description: >-
      exists           = "exists"   ":" domain-spec
    spec: 5.7/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e2.example.com
    result: permerror
  exists-cidr:
    description: >-
      exists           = "exists"   ":" domain-spec
    spec: 5.7/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e3.example.com
    result: permerror
  exists-ip4:
    description: >-
      mechanism matches if any DNS A RR exists
    spec: 5.7/3
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e4.example.com
    result: pass
  exists-ip6:
    description: >-
      The lookup type is A even when the connection is ip6
    spec: 5.7/3
    helo: mail.example.com
    host: CAFE:BABE::3
    mailfrom: foo@e4.example.com
    result: pass
  exists-ip6only:
    description: >-
      The lookup type is A even when the connection is ip6
    spec: 5.7/3
    helo: mail.example.com
    host: CAFE:BABE::3
    mailfrom: foo@e5.example.com
    result: fail
  exists-dnserr:
    description: >-
      Result for DNS error is being clarified in spfbis
    spec: 5.7/3
    helo: mail.example.com
    host: CAFE:BABE::3
    mailfrom: foo@e6.example.com
    result: [fail, temperror]
zonedata:
  mail.example.com:
    - A: 1.2.3.4
  mail6.example.com:
    - AAAA: CAFE:BABE::4
  err.example.com:
    - TIMEOUT: true
  e1.example.com:
    - SPF: "v=spf1 exists:"
  e2.example.com:
    - SPF: "v=spf1 exists"
  e3.example.com:
    - SPF: "v=spf1 exists:mail.example.com/24"
  e4.example.com:
    - SPF: "v=spf1 exists:mail.example.com"
  e5.example.com:
    - SPF: "v=spf1 exists:mail6.example.com -all"
  e6.example.com:
    - SPF: "v=spf1 exists:err.example.com -all"
---
description: IP4 mechanism syntax
tests:
  cidr4-0:
    description: >-
      ip4-cidr-length  = "/" 1*DIGIT
    spec: 5.6/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e1.example.com
    result: pass
  cidr4-32:
    description: >-
      ip4-cidr-length  = "/" 1*DIGIT
    spec: 5.6/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e2.example.com
    result: pass
  cidr4-33:
    description: >-
      Invalid CIDR should get permerror.
    comment: >-
      The RFC is silent on ip4 CIDR > 32 or ip6 CIDR > 128.  However,
      since there is no reasonable interpretation (except a noop), we have
      read between the lines to see a prohibition on invalid CIDR.
    spec: 5.6/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e3.example.com
    result: permerror
  cidr4-032:
    description: >-
      Invalid CIDR should get permerror.
    comment: >-
      Leading zeros are not explicitly prohibited by the RFC. However,
      since the RFC explicity prohibits leading zeros in ip4-network,
      our interpretation is that CIDR should be also.
    spec: 5.6/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e4.example.com
    result: permerror
    skip: It's not clear this is problematic.
  bare-ip4:
    description: >-
      IP4              = "ip4"      ":" ip4-network   [ ip4-cidr-length ]
    spec: 5.6/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e5.example.com
    result: permerror
  bad-ip4-port:
    description: >-
      IP4              = "ip4"      ":" ip4-network   [ ip4-cidr-length ]
    comment: >-
      This has actually been published in SPF records.
    spec: 5.6/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e8.example.com
    result: permerror
  bad-ip4-short:
    description: >-
      It is not permitted to omit parts of the IP address instead of
      using CIDR notations.
    spec: 5.6/4
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e9.example.com
    result: permerror
  ip4-dual-cidr:
    description: >-
      dual-cidr-length not permitted on ip4
    spec: 5.6/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e6.example.com
    result: permerror
  ip4-mapped-ip6:
    description: >-
      IP4 mapped IP6 connections MUST be treated as IP4
    spec: 5/9/2
    helo: mail.example.com
    host: ::FFFF:1.2.3.4
    mailfrom: foo@e7.example.com
    result: fail
zonedata:
  mail.example.com:
    - A: 1.2.3.4
  e1.example.com:
    - SPF: v=spf1 ip4:1.1.1.1/0 -all
  e2.example.com:
    - SPF: v=spf1 ip4:1.2.3.4/32 -all
  e3.example.com:
    - SPF: v=spf1 ip4:1.2.3.4/33 -all
  e4.example.com:
    - SPF: v=spf1 ip4:1.2.3.4/032 -all
  e5.example.com:
    - SPF: v=spf1 ip4
  e6.example.com:
    - SPF: v=spf1 ip4:1.2.3.4//32
  e7.example.com:
    - SPF: v=spf1 -ip4:1.2.3.4 ip6:::FFFF:1.2.3.4
  e8.example.com:
    - SPF: v=spf1 ip4:1.2.3.4:8080
  e9.example.com:
    - SPF: v=spf1 ip4:1.2.3
---
description: IP6 mechanism syntax
comment: >-
  IP4 only implementations may skip tests where host is not IP4
tests:
  bare-ip6:
    description: >-
      IP6              = "ip6"      ":" ip6-network   [ ip6-cidr-length ]
    spec: 5.6/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e1.example.com
    result: permerror
    skip: There's an early match.
  cidr6-0-ip4:
    description: >-
      IP4 connections do not match ip6.
    comment: >-
      There is controversy over ip4 mapped connections.  RFC4408 clearly
      requires such connections to be considered as ip4.  However,
      some interpret the RFC to mean that such connections should *also*
      match appropriate ip6 mechanisms (but not, inexplicably, A or MX
      mechanisms).  Until there is consensus, both
      results are acceptable.
    spec: 5/9/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e2.example.com
    result: [neutral, pass]
  cidr6-ip4:
    description: >-
      Even if the SMTP connection is via IPv6, an IPv4-mapped IPv6 IP address
      (see RFC 3513, Section 2.5.5) MUST still be considered an IPv4 address.
    comment: >-
      There is controversy over ip4 mapped connections.  RFC4408 clearly
      requires such connections to be considered as ip4.  However,
      some interpret the RFC to mean that such connections should *also*
      match appropriate ip6 mechanisms (but not, inexplicably, A or MX
      mechanisms).  Until there is consensus, both
      results are acceptable.
    spec: 5/9/2
    helo: mail.example.com
    host: ::FFFF:1.2.3.4
    mailfrom: foo@e2.example.com
    result: [neutral, pass]
  cidr6-0:
    description: >-
      Match any IP6
    spec: 5/8
    helo: mail.example.com
    host: DEAF:BABE::CAB:FEE
    mailfrom: foo@e2.example.com
    result: pass
  cidr6-129:
    description: >-
      Invalid CIDR
    comment: >-
      IP4 only implementations MUST fully syntax check all mechanisms,
      even if they otherwise ignore them.
    spec: 5.6/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e3.example.com
    result: permerror
  cidr6-bad:
    description: >-
      dual-cidr syntax not used for ip6
    comment: >-
      IP4 only implementations MUST fully syntax check all mechanisms,
      even if they otherwise ignore them.
    spec: 5.6/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e4.example.com
    result: permerror
  cidr6-33:
    description: >-
      make sure ip4 cidr restriction are not used for ip6
    spec: 5.6/2
    helo: mail.example.com
    host: "CAFE:BABE:8000::"
    mailfrom: foo@e5.example.com
    result: pass
  cidr6-33-ip4:
    description: >-
      make sure ip4 cidr restriction are not used for ip6
    spec: 5.6/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e5.example.com
    result: neutral
  ip6-bad1:
    description: >-
    spec: 5.6/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e6.example.com
    result: permerror
zonedata:
  mail.example.com:
    - A: 1.2.3.4
  e1.example.com:
    - SPF: v=spf1 -all ip6
  e2.example.com:
    - SPF: v=spf1 ip6:::1.1.1.1/0
  e3.example.com:
    - SPF: v=spf1 ip6:::1.1.1.1/129
  e4.example.com:
    - SPF: v=spf1 ip6:::1.1.1.1//33
  e5.example.com:
    - SPF: v=spf1 ip6:CAFE:BABE:8000::/33
  e6.example.com:
    - SPF: v=spf1 ip6::CAFE::BABE
---
description: Semantics of exp and other modifiers
comment: >-
  Implementing exp= is optional.  If not implemented, the test driver should
  not check the explanation field.
tests:
  redirect-none:
    description: >-
      If no SPF record is found, or if the target-name is malformed, the result
      is a "PermError" rather than "None".
    spec: 6.1/4
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e10.example.com
    result: permerror
  redirect-cancels-exp:
    description: >-
      when executing "redirect", exp= from the original domain MUST NOT be used.
    spec: 6.2/13
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e1.example.com
    result: fail
    explanation: DEFAULT
  redirect-syntax-error:
    description: |
      redirect      = "redirect" "=" domain-spec
    comment: >-
      A literal application of the grammar causes modifier syntax
      errors (except for macro syntax) to become unknown-modifier.
      
        modifier = explanation | redirect | unknown-modifier
      
      However, it is generally agreed, with precedent in other RFCs,
      that unknown-modifier should not be "greedy", and should not
      match known modifier names.  There should have been explicit
      prose to this effect, and some has been proposed as an erratum.
    spec: 6.1/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e17.example.com
    result: permerror
    skip: We don't enforce charset within the redirect.
  include-ignores-exp:
    description: >-
      when executing "include", exp= from the target domain MUST NOT be used.
    spec: 6.2/13
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e7.example.com
    result: fail
    explanation: Correct!
  redirect-cancels-prior-exp:
    description: >-
      when executing "redirect", exp= from the original domain MUST NOT be used.
    spec: 6.2/13
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e3.example.com
    result: fail
    explanation: See me.
  invalid-modifier:
    description: |
      unknown-modifier = name "=" macro-string
      name             = ALPHA *( ALPHA / DIGIT / "-" / "_" / "." )
    comment: >-
      Unknown modifier name must begin with alpha.
    spec: A/3
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e5.example.com
    result: permerror
  empty-modifier-name:
    description: |
      name             = ALPHA *( ALPHA / DIGIT / "-" / "_" / "." )
    comment: >-
      Unknown modifier name must not be empty.
    spec: A/3
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e6.example.com
    result: permerror
  dorky-sentinel:
    description: >-
      An implementation that uses a legal expansion as a sentinel.  We
      cannot check them all, but we can check this one.
    comment: >-
      Spaces are allowed in local-part.
    spec: 8.1/6
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: "Macro Error@e8.example.com"
    result: fail
    explanation: Macro Error in implementation
  exp-multiple-txt:
    description: |
      Ignore exp if multiple TXT records.
    comment: >-
      If domain-spec is empty, or there are any DNS processing errors (any
      RCODE other than 0), or if no records are returned, or if more than one
      record is returned, or if there are syntax errors in the explanation
      string, then proceed as if no exp modifier was given.
    spec: 6.2/4
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e11.example.com
    result: fail
    explanation: DEFAULT
  exp-no-txt:
    description: |
      Ignore exp if no TXT records.
    comment: >-
      If domain-spec is empty, or there are any DNS processing errors (any
      RCODE other than 0), or if no records are returned, or if more than one
      record is returned, or if there are syntax errors in the explanation
      string, then proceed as if no exp modifier was given.
    spec: 6.2/4
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e22.example.com
    result: fail
    explanation: DEFAULT
  exp-dns-error:
    description: |
      Ignore exp if DNS error.
    comment: >-
      If domain-spec is empty, or there are any DNS processing errors (any
      RCODE other than 0), or if no records are returned, or if more than one
      record is returned, or if there are syntax errors in the explanation
      string, then proceed as if no exp modifier was given.
    spec: 6.2/4
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e21.example.com
    result: fail
    explanation: DEFAULT
  exp-empty-domain:
    description: |
      PermError if exp= domain-spec is empty.
    comment: >-
      Section 6.2/4 says, "If domain-spec is empty, or there are any DNS
      processing errors (any RCODE other than 0), or if no records are
      returned, or if more than one record is returned, or if there are syntax
      errors in the explanation string, then proceed as if no exp modifier was
      given."  However, "if domain-spec is empty" conflicts with the grammar
      given for the exp modifier.  This was reported as an erratum, and the
      solution chosen was to report explicit "exp=" as PermError, but ignore
      problems due to macro expansion, DNS, or invalid explanation string.
    spec: 6.2/4
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e12.example.com
    result: permerror
    skip: We ignore exp, and is harmless.
  explanation-syntax-error:
    description: |
      Ignore exp if the explanation string has a syntax error.
    comment: >-
      If domain-spec is empty, or there are any DNS processing errors (any
      RCODE other than 0), or if no records are returned, or if more than one
      record is returned, or if there are syntax errors in the explanation
      string, then proceed as if no exp modifier was given.
    spec: 6.2/4
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e13.example.com
    result: fail
    explanation: DEFAULT
  exp-syntax-error:
    description: |
      explanation      = "exp" "=" domain-spec
    comment: >-
      A literal application of the grammar causes modifier syntax
      errors (except for macro syntax) to become unknown-modifier.
      
        modifier = explanation | redirect | unknown-modifier
      
      However, it is generally agreed, with precedent in other RFCs,
      that unknown-modifier should not be "greedy", and should not
      match known modifier names.  There should have been explicit
      prose to this effect, and some has been proposed as an erratum.
    spec: 6.2/1
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e16.example.com
    result: permerror
    skip: We don't enforce exp values.
  exp-twice:
    description: |
      exp= appears twice.
    comment: >-
      These two modifiers (exp,redirect) MUST NOT appear in a record more than
      once each. If they do, then check_host() exits with a result of
      "PermError".
    spec: 6/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e14.example.com
    result: permerror
    skip: We ignore exp, and is harmless.
  redirect-empty-domain:
    description: |
      redirect = "redirect" "=" domain-spec
    comment: >-
      Unlike for exp, there is no instruction to override the permerror
      for an empty domain-spec (which is invalid syntax).
    spec: 6.2/4
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e18.example.com
    result: permerror
    skip: There's an early match.
  redirect-twice:
    description: |
      redirect= appears twice.
    comment: >-
      These two modifiers (exp,redirect) MUST NOT appear in a record more than
      once each. If they do, then check_host() exits with a result of
      "PermError".
    spec: 6/2
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e15.example.com
    result: permerror
  unknown-modifier-syntax:
    description: |
      unknown-modifier = name "=" macro-string
    comment: >-
      Unknown modifiers must have valid macro syntax.
    spec: A/3
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e9.example.com
    result: permerror
    skip: There's an early match.
  default-modifier-obsolete:
    description: |
      Unknown modifiers do not modify the RFC SPF result.
    comment: >-
      Some implementations may have a leftover default= modifier from
      earlier drafts.
    spec: 6/3
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e19.example.com
    result: neutral
    skip: Not worth the complexity of erroring on this.
  default-modifier-obsolete2:
    description: |
      Unknown modifiers do not modify the RFC SPF result.
    comment: >-
      Some implementations may have a leftover default= modifier from
      earlier drafts.
    spec: 6/3
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e20.example.com
    result: neutral
    skip: Not worth the complexity of erroring on this.
  non-ascii-exp:
    description: >-
      SPF explanation text is restricted to 7-bit ascii.
    comment: >-
      Checking a possibly different code path for non-ascii chars.
    spec: 6.2/5
    helo: hosed
    host: 1.2.3.4
    mailfrom: "foobar@nonascii.example.com"
    result: fail
    explanation: DEFAULT
  two-exp-records:
    description: >-
      Must ignore exp= if DNS returns more than one TXT record.
    spec: 6.2/4
    helo: hosed
    host: 1.2.3.4
    mailfrom: "foobar@tworecs.example.com"
    result: fail
    explanation: DEFAULT
zonedata:
  mail.example.com:
    - A: 1.2.3.4
  e1.example.com:
    - SPF: v=spf1 exp=exp1.example.com redirect=e2.example.com
  e2.example.com:
    - SPF: v=spf1 -all
  e3.example.com:
    - SPF: v=spf1 exp=exp1.example.com redirect=e4.example.com
  e4.example.com:
    - SPF: v=spf1 -all exp=exp2.example.com
  exp1.example.com:
    - TXT: No-see-um
  exp2.example.com:
    - TXT: See me.
  exp3.example.com:
    - TXT: Correct!
  exp4.example.com:
    - TXT: "%{l} in implementation"
  e5.example.com:
    - SPF: v=spf1 1up=foo
  e6.example.com:
    - SPF: v=spf1 =all
  e7.example.com:
    - SPF: v=spf1 include:e3.example.com -all exp=exp3.example.com
  e8.example.com:
    - SPF: v=spf1 -all exp=exp4.example.com
  e9.example.com:
    - SPF: v=spf1 -all foo=%abc
  e10.example.com:
    - SPF: v=spf1 redirect=erehwon.example.com
  e11.example.com:
    - SPF: v=spf1 -all exp=e11msg.example.com
  e11msg.example.com:
    - TXT: Answer a fool according to his folly.
    - TXT: Do not answer a fool according to his folly.
  e12.example.com:
    - SPF: v=spf1 exp= -all
  e13.example.com:
    - SPF: v=spf1 exp=e13msg.example.com -all
  e13msg.example.com:
    - TXT: The %{x}-files.
  e14.example.com:
    - SPF: v=spf1 exp=e13msg.example.com -all exp=e11msg.example.com
  e15.example.com:
    - SPF: v=spf1 redirect=e12.example.com -all redirect=e12.example.com
  e16.example.com:
    - SPF: v=spf1 exp=-all
  e17.example.com:
    - SPF: v=spf1 redirect=-all ?all
  e18.example.com:
    - SPF: v=spf1 ?all redirect=
  e19.example.com:
    - SPF: v=spf1 default=pass
  e20.example.com:
    - SPF: "v=spf1 default=+"
  e21.example.com:
    - SPF: v=spf1 exp=e21msg.example.com -all
  e21msg.example.com:
    - TIMEOUT: true
  e22.example.com:
    - SPF: v=spf1 exp=mail.example.com -all
  nonascii.example.com:
    - SPF: v=spf1 exp=badexp.example.com -all
  badexp.example.com:
    - TXT: "\xEF\xBB\xBFExplanation"
  tworecs.example.com:
    - SPF: v=spf1 exp=twoexp.example.com -all
  twoexp.example.com:
    - TXT: "one"
    - TXT: "two"
---
description: Macro expansion rules
tests:
  trailing-dot-domain:
    spec: 8.1/16
    description: >-
      trailing dot is ignored for domains
    helo: msgbas2x.cos.example.com
    host: 192.168.218.40
    mailfrom: test@example.com
    result: pass
  trailing-dot-exp:
    spec: 8.1
    description: >-
      trailing dot is not removed from explanation
    comment: >-
      A simple way for an implementation to ignore trailing dots on
      domains is to remove it when present.  But be careful not to
      remove it for explanation text.
    helo: msgbas2x.cos.example.com
    host: 192.168.218.40
    mailfrom: test@exp.example.com
    result: fail
    explanation: This is a test.
  exp-only-macro-char:
    spec: 8.1/8
    description: >-
      The following macro letters are allowed only in "exp" text: c, r, t
    helo: msgbas2x.cos.example.com
    host: 192.168.218.40
    mailfrom: test@e2.example.com
    result: permerror
    skip: We ignore exp, and is harmless.
  invalid-macro-char:
    spec: 8.1/9
    description: >-
      A '%' character not followed by a '{', '%', '-', or '_' character
      is a syntax error.
    helo: msgbas2x.cos.example.com
    host: 192.168.218.40
    mailfrom: test@e1.example.com
    result: permerror
  invalid-embedded-macro-char:
    spec: 8.1/9
    description: >-
      A '%' character not followed by a '{', '%', '-', or '_' character
      is a syntax error.
    helo: msgbas2x.cos.example.com
    host: 192.168.218.40
    mailfrom: test@e1e.example.com
    result: permerror
  invalid-trailing-macro-char:
    spec: 8.1/9
    description: >-
      A '%' character not followed by a '{', '%', '-', or '_' character
      is a syntax error.
    helo: msgbas2x.cos.example.com
    host: 192.168.218.40
    mailfrom: test@e1t.example.com
    result: permerror
  macro-mania-in-domain:
    description: >-
      macro-encoded percents (%%), spaces (%_), and URL-percent-encoded
      spaces (%-)
    spec: 8.1/3, 8.1/4
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: test@e1a.example.com
    result: pass
  exp-txt-macro-char:
    spec: 8.1/20
    description: >-
      For IPv4 addresses, both the "i" and "c" macros expand
      to the standard dotted-quad format.
    helo: msgbas2x.cos.example.com
    host: 192.168.218.40
    mailfrom: test@e3.example.com
    result: fail
    explanation: Connections from 192.168.218.40 not authorized.
  domain-name-truncation:
    spec: 8.1/25
    description: >-
      When the result of macro expansion is used in a domain name query, if the
      expanded domain name exceeds 253 characters, the left side is truncated
      to fit, by removing successive domain labels until the total length does
      not exceed 253 characters.
    helo: msgbas2x.cos.example.com
    host: 192.168.218.40
    mailfrom: test@somewhat.long.exp.example.com
    result: fail
    explanation: Congratulations!  That was tricky.
  v-macro-ip4:
    spec: 8.1/6
    description: |-
      v = the string "in-addr" if <ip> is ipv4, or "ip6" if <ip> is ipv6
    helo: msgbas2x.cos.example.com
    host: 192.168.218.40
    mailfrom: test@e4.example.com
    result: fail
    explanation: 192.168.218.40 is queried as 40.218.168.192.in-addr.arpa
  v-macro-ip6:
    spec: 8.1/6
    description: |-
      v = the string "in-addr" if <ip> is ipv4, or "ip6" if <ip> is ipv6
    helo: msgbas2x.cos.example.com
    host: CAFE:BABE::1
    mailfrom: test@e4.example.com
    result: fail
    explanation: cafe:babe::1 is queried as 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.E.B.A.B.E.F.A.C.ip6.arpa
  undef-macro:
    spec: 8.1/6
    description: >-
      Allowed macros chars are 'slodipvh' plus 'crt' in explanation.
    helo: msgbas2x.cos.example.com
    host: CAFE:BABE::192.168.218.40
    mailfrom: test@e5.example.com
    result: permerror
  p-macro-ip4-novalid:
    spec: 8.1/22
    description: |-
      p = the validated domain name of <ip>
    comment: >-
      The PTR in this example does not validate.
    helo: msgbas2x.cos.example.com
    host: 192.168.218.40
    mailfrom: test@e6.example.com
    result: fail
    explanation: connect from unknown
  p-macro-ip4-valid:
    spec: 8.1/22
    description: |-
      p = the validated domain name of <ip>
    comment: >-
      If a subdomain of the <domain> is present, it SHOULD be used.
    helo: msgbas2x.cos.example.com
    host: 192.168.218.41
    mailfrom: test@e6.example.com
    result: fail
    explanation: connect from mx.example.com
  p-macro-ip6-novalid:
    spec: 8.1/22
    description: |-
      p = the validated domain name of <ip>
    comment: >-
      The PTR in this example does not validate.
    helo: msgbas2x.cos.example.com
    host: CAFE:BABE::1
    mailfrom: test@e6.example.com
    result: fail
    explanation: connect from unknown
  p-macro-ip6-valid:
    spec: 8.1/22
    description: |-
      p = the validated domain name of <ip>
    comment: >-
      If a subdomain of the <domain> is present, it SHOULD be used.
    helo: msgbas2x.cos.example.com
    host: CAFE:BABE::3
    mailfrom: test@e6.example.com
    result: fail
    explanation: connect from mx.example.com
  p-macro-multiple:
    spec: 8.1/22
    description: |-
      p = the validated domain name of <ip>
    comment: >-
      If a subdomain of the <domain> is present, it SHOULD be used.
    helo: msgbas2x.cos.example.com
    host: 192.168.218.42
    mailfrom: test@e7.example.com
    result: [pass, softfail]
    skip: p macro is not supported
  upper-macro:
    spec: 8.1/26
    description: >-
      Uppercased macros expand exactly as their lowercased equivalents,
      and are then URL escaped.
    helo: msgbas2x.cos.example.com
    host: 192.168.218.42
    mailfrom: jack&jill=up@e8.example.com
    result: fail
    explanation: http://example.com/why.html?l=jack%26jill%3Dup
  hello-macro:
    spec: 8.1/6
    description: |-
      h = HELO/EHLO domain
    helo: msgbas2x.cos.example.com
    host: 192.168.218.40
    mailfrom: test@e9.example.com
    result: pass
    skip: We don't have a HELO-explicit mode.
  invalid-hello-macro:
    spec: 8.1/2
    description: |-
      h = HELO/EHLO domain, but HELO is invalid
    comment: >-
      Domain-spec must end in either a macro, or a valid toplabel.
      It is not correct to check syntax after macro expansion.
    helo: "JUMPIN' JUPITER"
    host: 192.168.218.40
    mailfrom: test@e9.example.com
    result: fail
  hello-domain-literal:
    spec: 8.1/2
    description: |-
      h = HELO/EHLO domain, but HELO is a domain literal
    comment: >-
      Domain-spec must end in either a macro, or a valid toplabel.
      It is not correct to check syntax after macro expansion.
    helo: "[192.168.218.40]"
    host: 192.168.218.40
    mailfrom: test@e9.example.com
    result: fail
  require-valid-helo:
    spec: 8.1/6
    description: >-
      Example of requiring valid helo in sender policy.  This is a complex
      policy testing several points at once.
    helo: OEMCOMPUTER
    host: 1.2.3.4
    mailfrom: test@e10.example.com
    result: fail
  macro-reverse-split-on-dash:
    spec: [8.1/15, 8.1/16, 8.1/17, 8.1/18]
    description: >-
      Macro value transformation (splitting on arbitrary characters, reversal,
      number of right-hand parts to use)
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: philip-gladstone-test@e11.example.com
    result: pass
  macro-multiple-delimiters:
    spec: [8.1/15, 8.1/16]
    description: |-
      Multiple delimiters may be specified in a macro expression.
        macro-expand = ( "%{" macro-letter transformers *delimiter "}" )
                       / "%%" / "%_" / "%-"
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo-bar+zip+quux@e12.example.com
    result: pass
zonedata:
  example.com.d.spf.example.com:
    - SPF: v=spf1 redirect=a.spf.example.com
  a.spf.example.com:
    - SPF: v=spf1 include:o.spf.example.com. ~all
  o.spf.example.com:
    - SPF: v=spf1 ip4:192.168.218.40
  msgbas2x.cos.example.com:
    - A: 192.168.218.40
  example.com:
    - A: 192.168.90.76
    - SPF: v=spf1 redirect=%{d}.d.spf.example.com.
  exp.example.com:
    - SPF: v=spf1 exp=msg.example.com. -all
  msg.example.com:
    - TXT: This is a test.
  e1.example.com:
    - SPF: v=spf1 -exists:%(ir).sbl.example.com ?all
  e1e.example.com:
    - SPF: v=spf1 exists:foo%(ir).sbl.example.com ?all
  e1t.example.com:
    - SPF: v=spf1 exists:foo%.sbl.example.com ?all
  e1a.example.com:
    - SPF: "v=spf1 a:macro%%percent%_%_space%-url-space.example.com -all"
  "macro%percent  space%20url-space.example.com":
    - A: 1.2.3.4
  e2.example.com:
    - SPF: v=spf1 -all exp=%{r}.example.com
  e3.example.com:
    - SPF: v=spf1 -all exp=%{ir}.example.com
  40.218.168.192.example.com:
    - TXT: Connections from %{c} not authorized.
  somewhat.long.exp.example.com:
    - SPF: v=spf1 -all exp=foobar.%{o}.%{o}.%{o}.%{o}.%{o}.%{o}.%{o}.%{o}.example.com
  somewhat.long.exp.example.com.somewhat.long.exp.example.com.somewhat.long.exp.example.com.somewhat.long.exp.example.com.somewhat.long.exp.example.com.somewhat.long.exp.example.com.somewhat.long.exp.example.com.somewhat.long.exp.example.com.example.com:
    - TXT: Congratulations!  That was tricky.
  e4.example.com:
    - SPF: v=spf1 -all exp=e4msg.example.com
  e4msg.example.com:
    - TXT: "%{c} is queried as %{ir}.%{v}.arpa"
  e5.example.com:
    - SPF: v=spf1 a:%{a}.example.com -all
  e6.example.com:
    - SPF: v=spf1 -all exp=e6msg.example.com
  e6msg.example.com:
    - TXT: "connect from %{p}"
  mx.example.com:
    - A: 192.168.218.41
    - A: 192.168.218.42
    - AAAA: CAFE:BABE::2
    - AAAA: CAFE:BABE::3
  40.218.168.192.in-addr.arpa:
    - PTR: mx.example.com
  41.218.168.192.in-addr.arpa:
    - PTR: mx.example.com
  42.218.168.192.in-addr.arpa:
    - PTR: mx.example.com
    - PTR: mx.e7.example.com
  1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.E.B.A.B.E.F.A.C.ip6.arpa:
    - PTR: mx.example.com
  3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.E.B.A.B.E.F.A.C.ip6.arpa:
    - PTR: mx.example.com
  mx.e7.example.com:
    - A: 192.168.218.42
  mx.e7.example.com.should.example.com:
    - A: 127.0.0.2
  mx.example.com.ok.example.com:
    - A: 127.0.0.2
  e7.example.com:
    - SPF: v=spf1 exists:%{p}.should.example.com ~exists:%{p}.ok.example.com
  e8.example.com:
    - SPF: v=spf1 -all exp=msg8.%{D2}
  msg8.example.com:
    - TXT: "http://example.com/why.html?l=%{L}"
  e9.example.com:
    - SPF: v=spf1 a:%{H} -all
  e10.example.com:
    - SPF: v=spf1 -include:_spfh.%{d2} ip4:1.2.3.0/24 -all
  _spfh.example.com:
    - SPF: v=spf1 -a:%{h} +all
  e11.example.com:
    - SPF: v=spf1 exists:%{i}.%{l2r-}.user.%{d2}
  1.2.3.4.gladstone.philip.user.example.com:
    - A: 127.0.0.2
  e12.example.com:
    - SPF: v=spf1 exists:%{l2r+-}.user.%{d2}
  bar.foo.user.example.com:
    - A: 127.0.0.2
---
description: Processing limits
tests:
  redirect-loop:
    description: >-
      SPF implementations MUST limit the number of mechanisms and modifiers
      that do DNS lookups to at most 10 per SPF check.
    spec: 10.1/6
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e1.example.com
    result: permerror
  include-loop:
    description: >-
      SPF implementations MUST limit the number of mechanisms and modifiers
      that do DNS lookups to at most 10 per SPF check.
    spec: 10.1/6
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e2.example.com
    result: permerror
  mx-limit:
    description: >-
      there MUST be a limit of no more than 10 MX looked up and checked.
    comment: >-
      The required result for this test was the subject of much
      controversy.  Many felt that the RFC *should* have specified
      permerror, but the consensus was that it failed to actually do so.
      The preferred result reflects evaluating the 10 allowed MX records in the
      order returned by the test data - or sorted via priority.
      If testing with live DNS, the MX order may be random, and a pass
      result would still be compliant.  The SPF result is effectively
      random.
    spec: 10.1/7
    helo: mail.example.com
    host: 1.2.3.5
    mailfrom: foo@e4.example.com
    result: [neutral, pass, permerror]
  ptr-limit:
    description: >-
      there MUST be a limit of no more than 10 PTR looked up and checked.
    comment: >-
      The result of this test cannot be permerror not only because the
      RFC does not specify it, but because the sender has no control over
      the PTR records of spammers.
      The preferred result reflects evaluating the 10 allowed PTR records in
      the order returned by the test data.
      If testing with live DNS, the PTR order may be random, and a pass
      result would still be compliant.  The SPF result is effectively
      randomized.
    spec: 10.1/7
    helo: mail.example.com
    host: 1.2.3.5
    mailfrom: foo@e5.example.com
    result: [neutral, pass]
  false-a-limit:
    description: >-
      unlike MX, PTR, there is no RR limit for A
    comment: >-
      There seems to be a tendency for developers to want to limit
      A RRs in addition to MX and PTR.  These are IPs, not usable for
      3rd party DoS attacks, and hence need no low limit.
    spec: 10.1/7
    helo: mail.example.com
    host: 1.2.3.12
    mailfrom: foo@e10.example.com
    result: pass
  mech-at-limit:
    description: >-
      SPF implementations MUST limit the number of mechanisms and modifiers
      that do DNS lookups to at most 10 per SPF check.
    spec: 10.1/6
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e6.example.com
    result: pass
  mech-over-limit:
    description: >-
      SPF implementations MUST limit the number of mechanisms and modifiers
      that do DNS lookups to at most 10 per SPF check.
    comment: >-
      We do not check whether an implementation counts mechanisms before
      or after evaluation.  The RFC is not clear on this.
    spec: 10.1/6
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e7.example.com
    result: permerror
  include-at-limit:
    description: >-
      SPF implementations MUST limit the number of mechanisms and modifiers
      that do DNS lookups to at most 10 per SPF check.
    comment: >-
      The part of the RFC that talks about MAY parse the entire record first
      (4.6) is specific to syntax errors.  Processing limits is a different,
      non-syntax issue.  Processing limits (10.1) specifically talks about
      limits during a check.
    spec: 10.1/6
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e8.example.com
    result: pass
  include-over-limit:
    description: >-
      SPF implementations MUST limit the number of mechanisms and modifiers
      that do DNS lookups to at most 10 per SPF check.
    spec: 10.1/6
    helo: mail.example.com
    host: 1.2.3.4
    mailfrom: foo@e9.example.com
    result: permerror
zonedata:
  mail.example.com:
    - A: 1.2.3.4
  e1.example.com:
    - SPF: v=spf1 ip4:1.1.1.1 redirect=e1.example.com
    - A: 1.2.3.6
  e2.example.com:
    - SPF: v=spf1 include:e3.example.com
    - A: 1.2.3.7
  e3.example.com:
    - SPF: v=spf1 include:e2.example.com
    - A: 1.2.3.8
  e4.example.com:
    - SPF: v=spf1 mx
    - MX: [0, mail.example.com]
    - MX: [1, mail.example.com]
    - MX: [2, mail.example.com]
    - MX: [3, mail.example.com]
    - MX: [4, mail.example.com]
    - MX: [5, mail.example.com]
    - MX: [6, mail.example.com]
    - MX: [7, mail.example.com]
    - MX: [8, mail.example.com]
    - MX: [9, mail.example.com]
    - MX: [10, e4.example.com]
    - A: 1.2.3.5
  e5.example.com:
    - SPF: v=spf1 ptr
    - A: 1.2.3.5
  5.3.2.1.in-addr.arpa:
    - PTR: e1.example.com.
    - PTR: e2.example.com.
    - PTR: e3.example.com.
    - PTR: e4.example.com.
    - PTR: example.com.
    - PTR: e6.example.com.
    - PTR: e7.example.com.
    - PTR: e8.example.com.
    - PTR: e9.example.com.
    - PTR: e10.example.com.
    - PTR: e5.example.com.
  e6.example.com:
    - SPF: v=spf1 a mx a mx a mx a mx a ptr ip4:1.2.3.4 -all
    - A: 1.2.3.8
    - MX: [10, e6.example.com]
  e7.example.com:
    - SPF: v=spf1 a mx a mx a mx a mx a ptr a ip4:1.2.3.4 -all
    - A: 1.2.3.20
  e8.example.com:
    - SPF: v=spf1 a include:inc.example.com ip4:1.2.3.4 mx -all
    - A: 1.2.3.4
  inc.example.com:
    - SPF: v=spf1 a a a a a a a a
    - A: 1.2.3.10
  e9.example.com:
    - SPF: v=spf1 a include:inc.example.com a ip4:1.2.3.4 -all
    - A: 1.2.3.21
  e10.example.com:
    - SPF: v=spf1 a -all
    - A: 1.2.3.1
    - A: 1.2.3.2
    - A: 1.2.3.3
    - A: 1.2.3.4
    - A: 1.2.3.5
    - A: 1.2.3.6
    - A: 1.2.3.7
    - A: 1.2.3.8
    - A: 1.2.3.9
    - A: 1.2.3.10
    - A: 1.2.3.11
    - A: 1.2.3.12