Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <48451F97.3000709@netoyen.net>
Date: Tue, 03 Jun 2008 12:40:23 +0200
From: mouss <mouss@netoyen.net>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
CC: users@spamassassin.apache.org
Subject: Re: google netblocks records etc
References: <004f01c8c4e5$c7563650$9e00000a@msys1>
In-Reply-To: <004f01c8c4e5$c7563650$9e00000a@msys1>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Robert - elists wrote:
> Since they seem to have zillions of outbound mx machines
>
> I did this in response to some email latency issues.
>
> dig google.com txt
>
> google.com.             31      IN      TXT     "v=spf1
> include:_netblocks.google.com ~all"
>
> then i
>
> dig _netblocks.google.com txt
>
> _netblocks.google.com.  47      IN      TXT     "v=spf1 ip4:216.239.32.0/19
> ip4:64.233.160.0/19 ip4:66.249.80.0/20 ip4:72.14.192.0/18
> ip4:209.85.128.0/17 ip4:66.102.0.0/20 ip4:74.125.0.0/16 ip4:64.18.0.0/20
> ip4:207.126.144.0/20 ?all"
>
> Are most of you whitelisting these blocks ?
>   

You can use dnswl.
> has anyone noticed if these are pretty static or do these TXT records change
> frequently or otherwise?
>
>  - rh
>
>