Re: Harvest netblocks of good MTAs from SPF for whitelisting from greylisting

On 02/12/2013 09:36 PM, Constantine A. Murenin wrote:
>
> not the "netblock" set.  SPF is much more fine grained than netblocks.  The
> I think you're putting distinct meanings into the terms "IP set" and
> "netblock", or ignoring the fact that bigger providers actually
> publish their IP set as netblocks within SPF.
I may have misunderstood you also.  I thought you were broadening 
narrower IPs to include the entire netblock.
> Else, why would someone specify a netblock in their SPF that's not
> their actual IP set?  If they do, then their SPF is broken, and it'll
> still be broken regardless whether you do the harvesting like I
> contemplate, or implement SPF on your MTA.
>
>> same colocation facility might have both "good" and "evil" domains.  The
>> idea of statically compiling the IP set for your type of application is a
>> good one, and has already been implemented.
> Where has it been implemented?  Please provide me a link, I'm very
> interested in applying it to my setup.

http://www.libspf2.org/docs/html/spf__compile_8c.html

I'm not sure if that was intended to be used by itself - libspf2 uses it 
to cache SPF records in a very fast form.

Also, I have a similar feature I added recently to pyspf - it isn't 
checked in to CVS yet, not thoroughly test.  I added it because I've 
often just wanted a list of MTA IPs for debugging mail problems...