spf-discuss
[Top] [All Lists]

Re: libspf2 incorrectly handling certain queries

2005-01-12 16:00:29
On Wed, 12 Jan 2005, Rick Cooper wrote:

host -t TXT wrtv.com
wrtv.com text "v=spf1 a:qbert.ibsys.com a:anubis.ibsys.com
a:treets100.ibsys.com include:mcgraw-hill.com -all"


it contains an include: for mcgraw-hill.com so now check the spf record
for mcgraw-hill

host -t TXT mcgraw-hill.com
mcgraw-hill.com text "v=spf1 ip4:66.54.164.0/24 ip4:64.94.160.128/26 mx
ptr -all"

now using spfquery from libspf2 the query fails

spfquery -i 198.45.18.176 -s xxx(_at_)wrtv(_dot_)com -h 
corp148mr3-11.mcgraw-hill.com
fail
Please see
http://spf.pobox.com/why.html?sender=xxx%40wrtv.com&ip=198.45.18.176&receive
r=spfquery
spfquery: domain of wrtv.com does not designate 198.45.18.176 as permitted
sender
Received-SPF: fail (spfquery: domain of wrtv.com does not designate
198.45.18.176 as permitted sender) client-ip=198.45.18.176;
envelope-from=xxx(_at_)wrtv(_dot_)com; helo=corp148mr3-11.mcgraw-hill.com;


I seem to remember this was mentioned on the list before.  If I remember 
right, one implementation didn't handle the ptr: inside the include: 
correctly.  It was being treated as if you had said ptr:wrtv.com instead of 
ptr:mcgraw-hill.com.

Perhaps you could recommend to the mcgraw-hill.com people that they could 
explicitly put "ptr:mcgraw-hill.com" instead of just ptr?  Though the real 
problem of the library should be fixed anyway...

-- 
Greg Connor
gconnor(_at_)nekodojo(_dot_)org

Everyone says that having power is a great responsibility.  This is a lot
of bunk.  Responsibility is when someone can blame you if something goes
wrong.  When you have power you are surrounded by people whose job it is
to take the blame for your mistakes.  If they're smart, that is. 
                -- Cerebus, "On Governing"


<Prev in Thread] Current Thread [Next in Thread>