Stuart D. Gathman wrote:
Is rr.com reasonable?
Not if you find a way to count more than 10 DNS mechanisms ;-)
The general policy has 10 DNS mechanisms, and the last is mx,
so that's _apparently_ still allowed.
But the 9th include:tampabay has its own mx counted as 10th
DNS mechanism, that already pushes the general mx to number 11,
and a conforming implementation would report a PermError never
reaching the ~all.
Asumming that all included SPF policies are like tampabay each
include counts as 1 (q=txt) + 1 (q=mx) = 2, and you should get
a PermError at the 6th include:rfc-nyc
That would reduce your list to 39 DNS queries, see below, bye.
rr.com TXT
biz.rr.com TXT
biz.rr.com MX
mx1.biz.rr.com A
mx2.biz.rr.com A
texas.rr.com TXT
texas.rr.com MX
orngca-01.mgw.rr.com A
orngca-02.mgw.rr.com A
hrndva-01.mgw.rr.com A
hrndva-02.mgw.rr.com A
austtx-01.mgw.rr.com A
austtx-02.mgw.rr.com A
southeast.rr.com TXT
southeast.rr.com MX
austtx-02.mgw.rr.com A
orngca-01.mgw.rr.com A
orngca-02.mgw.rr.com A
hrndva-01.mgw.rr.com A
hrndva-02.mgw.rr.com A
austtx-01.mgw.rr.com A
ohiordc.rr.com TXT
ohiordc.rr.com MX
orngca-01.mgw.rr.com A
orngca-02.mgw.rr.com A
hrndva-01.mgw.rr.com A
hrndva-02.mgw.rr.com A
mx-server.mgw.rr.com A
av.mgw.rr.com A
clmboh-01.mgw.rr.com A
clmboh-02.mgw.rr.com A
rdc-kc.rr.com TXT
rdc-kc.rr.com MX
kcmx01.mgw.rr.com A
kcmx02.mgw.rr.com A
lamx01.mgw.rr.com A
lamx02.mgw.rr.com A
kc.mgw.rr.com A
vamx02.mgw.rr.com A