Thanks to John Hardin for noticing one of these was off. I should've checked them before replying.
*None* of these should be hitting RCVD_IN_DNSWL_HI or RCVD_IN_DNSWL_MED, or even RCVD_IN_DNSWL_LOW. Alessio, you have a problem *other* than the data listed by dnswl.org. Start with the X-Spam-RelaysUntrusted header I recommended in my last post. On 10/11, Alessio Cecchi wrote: > Received: from [175.145.6.37] (unknown [175.145.6.37]) $ host 37.6.145.175.list.dnswl.org Host 37.6.145.175.list.dnswl.org not found: 3(NXDOMAIN) Should not hit any RCVD_IN_DNSWL_* rules. > Received: from webbox794.server-home.net (webbox794.server-home.net > [195.137.213.84]) $ host 84.213.137.195.list.dnswl.org Host 84.213.137.195.list.dnswl.org not found: 3(NXDOMAIN) Should not hit any RCVD_IN_DNSWL_* rules. > Received: from node-sl626.smtp.com (node-sl626.smtp.com [74.86.21.70]) $ host 70.21.86.74.list.dnswl.org Host 70.21.86.74.list.dnswl.org not found: 3(NXDOMAIN) Should not hit any RCVD_IN_DNSWL_* rules. > Received: from nm14.bullet.mail.sp2.yahoo.com > (nm14.bullet.mail.sp2.yahoo.com [98.139.91.84]) $ host 84.91.139.98.list.dnswl.org 84.91.139.98.list.dnswl.org has address 127.0.5.0 Should hit RCVD_IN_DNSWL_NONE. -- "A ship in a port is safe, but that's not what ships are built for." -Grace Murray Hopper http://www.ChaosReigns.com
