OpenSPF Why Page and SPF record types

Richard Lawley <[email protected]> Thu, 1 Aug 2013 09:19:49 +0100
Newsgroups gmane.mail.spam.spf.discuss
Message-ID <CAPEApX+3ujgPQKNWqXHMD8KckWMnY5=JpngGGFdk0XWSkUrm3w@mail.gmail.com>
--089e0160c454738be204e2de8121
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I'm not sure if anyone on here is responsible for or involved with the
OpenSPF WHY page.

I just spent quite some time tracking down a problem with SPF records on
one of my domains, which ended up being down to the DNS software my DNS
host uses serving a synthesised SPF type record.  This was invisible
through their editor, and is also hard to query since support for the
record type was not in the version of dig which I was initially using, nor
does nslookup support it in Windows.  The problem also compounded by them
serving different synthesised results from both of the nameservers, one of
them ending in -all and the other ~all.

This is clearly a niche situation - for a message to be bounced it had to
be checked by an SPF implementation that took SPF-type records instead of
TXT-type records, and it had to have been served by the DNS server with the
-all record.  However, less of a niche situation would be where SPF and TXT
records both exist but do not match.

One of the bounce messages has directed me to the OpenSPF WHY page, which
was showing me that the message didn't match my SPF record, but that it
shouldn't have stopped the message (presumably it had hit the server with
the ~all record).  What I would like to suggest is that the record checker
prints the contents of the SPF record it retrieved (and ideally the type of
record it is!) in order to make it more obvious what was going on.

Additional diagnostic steps could potentially be added, such as showing
that conflicting SPF and TXT records exist, but my first suggestion would
have helped me solve this a lot.  Just hoping that this can help someone
else in a similar situation!

Regards,

Richard



-------------------------------------------
Sender Policy Framework: http://www.openspf.net [http://www.openspf.net]
Modify Your Subscription: http://www.listbox.com/member/ [http://www.listbox.com/member/]

Archives: https://www.listbox.com/member/archive/735/=now
RSS Feed: https://www.listbox.com/member/archive/rss/735/6959934-50ec8f89
Modify Your Subscription: https://www.listbox.com/member/?member_id=6959934&id_secret=6959934-b7c4528d
Unsubscribe Now: https://www.listbox.com/unsubscribe/?member_id=6959934&id_secret=6959934-edadf31a&post_id=20130801041958:23FDF6DA-FA83-11E2-9291-F76E11191F9C
Powered by Listbox: http://www.listbox.com

--089e0160c454738be204e2de8121
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>I&#39;m not sure if anyone on here =
is responsible for or involved with the OpenSPF WHY page.</div><div><br></d=
iv><div>I just spent quite some time tracking down a problem with SPF recor=
ds on one of my domains, which ended up being down to the DNS software my D=
NS host uses serving a synthesised SPF type record. =A0This was invisible t=
hrough their editor, and is also hard to query since support for the record=
 type was not in the version of dig which I was initially using, nor does n=
slookup support it in Windows. =A0The problem also compounded by them servi=
ng different synthesised results from both of the nameservers, one of them =
ending in -all and the other ~all.</div>
<div><br></div><div>This is clearly a niche situation - for a message to be=
 bounced it had to be checked by an SPF implementation that took SPF-type r=
ecords instead of TXT-type records, and it had to have been served by the D=
NS server with the -all record. =A0However, less of a niche situation would=
 be where SPF and TXT records both exist but do not match.</div>
<div><br></div><div>One of the bounce messages has directed me to the OpenS=
PF WHY page, which was showing me that the message didn&#39;t match my SPF =
record, but that it shouldn&#39;t have stopped the message (presumably it h=
ad hit the server with the ~all record). =A0What I would like to suggest is=
 that the record checker prints the contents of the SPF record it retrieved=
 (and ideally the type of record it is!) in order to make it more obvious w=
hat was going on.</div>
<div><br></div><div>Additional diagnostic steps could potentially be added,=
 such as showing that conflicting SPF and TXT records exist, but my first s=
uggestion would have helped me solve this a lot. =A0Just hoping that this c=
an help someone else in a similar situation!</div>
<div><br></div><div>Regards,</div><div><br></div><div>Richard</div></div>
<div style=3D"width:auto;margin:0;padding:5px;background-color:#fff;clear:b=
oth;border-top: 1px solid #ccc;" bgcolor=3D"#ffffff">
<p style=3D'font-family:Arial,sans-serif;margin:0.5em auto'>Sender Policy F=
ramework: <a href=3D"http://www.openspf.net">http://www.openspf.net</a><br>=
=0D
Modify Your Subscription: <a href=3D"http://www.listbox.com/member/">http:/=
/www.listbox.com/member/</a></p>
<table border=3D"0" cellspacing=3D"0" cellpadding=3D"0" width=3D"100%" styl=
e=3D"background-color:#fff" bgcolor=3D"#ffffff">
  <tr>
    <td padding=3D"4px">
      <font color=3D"#333333" size=3D"1" style=3D"font-family:helvetica, sa=
ns-serif;">
      <a style=3D"text-decoration:none;color:#669933;border-bottom: 1px sol=
id #444444"
href=3D"https://www.listbox.com/member/archive/735/=3Dnow" title=3D"Go to a=
rchives for spf-discuss">Archives</a>
<a border=3D"0" style=3D"text-decoration:none;color:#669933" href=3D"https:=
//www.listbox.com/member/archive/rss/735/6959934-50ec8f89" title=3D"RSS fee=
d for spf-discuss"><img border=3D0 src=3D"https://www.listbox.com/images/fe=
ed-icon-10x10.jpg" /></a>
 | <a style=3D"text-decoration:none;color:#669933;border-bottom: 1px solid =
#444444"
href=3D"https://www.listbox.com/member/?member_id=3D6959934&id_secret=3D695=
9934-b7c4528d" title=3D"">Modify</a>
 Your Subscription | <a style=3D"text-decoration:none;color:#669933;border-=
bottom: 1px solid #444444"
href=3D"https://www.listbox.com/unsubscribe/?member_id=3D6959934&id_secret=
=3D6959934-edadf31a&post_id=3D20130801041958:23FDF6DA-FA83-11E2-9291-F76E11=
191F9C" title=3D"">Unsubscribe Now</a>
<td valign=3D"top" align=3D"right"><a style=3D"border-bottom:none;" href=3D=
"http://www.listbox.com">
<img src=3D"https://www.listbox.com/images/listbox-logo-small.png"
title=3D"Powered by Listbox" border=3D"0" /></a></td>

      </font>
    </td>
  </tr>
</table>
</div>

--089e0160c454738be204e2de8121--