Re: looks like CAPITALS-Bug in library

Hi,

thanks for getting back on this issue.

On 03/11/2016 08:05 AM, Scott Kitterman wrote:
>
> On March 10, 2016 9:48:07 PM EST, "Stuart D. Gathman" <[email protected]=
> wrote:
>> On Thu, 10 Mar 2016, alan wrote:
>>
>>> can i suggest providing the real domain names involved so anyone can
>>> replicate/verify or possibly find alternate causation im sure some
>> can
>>> easily test against a range of versions of bind in different modes


Actually the domain in question was "wwk.de" ; sending IP was
 212.144.243.129 - leading to:

python -m spf -v 212.144.243.129  [email protected] wwk.de
top: wwk.de "v=3Dspf1 a mx:WWK.de include:spf.mandrillapp.com
include:_spf.retarus.com -all"
include: spf.mandrillapp.com "v=3Dspf1 ip4:198.2.128.0/24
ip4:198.2.132.0/22 ip4:198.2.136.0/23 ip4:198.2.186.0/23
ip4:205.201.131.128/25 ip4:205.201.134.128/25 ip4:205.201.136.0/23
ip4:205.201.139.0/24 ip4:198.2.180.0/24 ip4:198.2.179.0/24
ip4:198.2.178.0/24 ip4:198.2.177.0/24 ~all"
include: _spf.retarus.com "v=3Dspf1 ip4:94.199.88.0/22 ip4:82.135.18.0/23
ip4:62.245.148.0/26 ip4:62.134.45.32/28 ip4:217.111.120.0/27
ip4:94.199.92.0/23 ip4:185.93.140.0/24 ~all"
(('fail', 550, 'SPF fail - not authorized'), '-all')

when asking a resolver using bind 9.95

The behaviour was like described.

pyspf used is :
VERSION
    2.0.9: Apr 29, 2014

kind regards,

Gunther



>> +1
>>
>> Also, the pyspf version used.  For instance, 2.0.11 adds a workaround=20
>> for a DNS caching server returning random case for lookups.  (Maybe
>> the developer wanted to make sure everyone was properly ignoring
>> case - I dunno.)
> The repository he's installing from has 2.0.9.
>
> Scott K
>
>