On 10/11, John Hardin wrote: > On Tue, 11 Oct 2011, Alessio Cecchi wrote: > >Received: from nm14.bullet.mail.sp2.yahoo.com > >(nm14.bullet.mail.sp2.yahoo.com [98.139.91.84]) > > by www-mydomain.myserver.net (Postfix) with SMTP id 8889762AB1 > > for <i...@mydomain.biz>; Tue, 11 Oct 2011 15:44:22 +0200 (CEST) > > Yahoo is in RCVD_IN_DNSWL_HI ?!?! YGBFKM!
Hah, no, that IP 98.139.91.84, listed as NONE. As it should be. $ host 84.91.139.98.list.dnswl.org 84.91.139.98.list.dnswl.org has address 127.0.5.0 0 in the last octet of the returned IP = NONE. - http://www.dnswl.org/tech So, there could be a trusted_networks / internal_networks spamassassin configuration problem, a bug in spamassassin, or a DNS server between spamassassin and dnswl.org doing something weird. Alessio, a good place to start would be to add to your spamassassin config: add_header all RelaysUntrusted _RELAYSUNTRUSTED_ This will add headers like: X-Spam-RelaysUntrusted: [ ip=140.211.11.3 rdns=hermes.apache.org That first IP listed is the IP that network tests like RCVD_IN_DNSWL_* use, so it should be the IP you got it from. In this example you'd want it to be 98.139.91.84. If it's not, you have a problem with your trusted_networks / internal_networks settings in your spamassassin config. On 10/11, Michael Scheidell wrote: > <p>You don't have permission to access /dnswl/dl/DNSWLh.pm Thanks, fixed. Sorry about that. On 10/11, Michael Scheidell wrote: > On 10/11/11 1:47 PM, John Hardin wrote: > >Yahoo is in RCVD_IN_DNSWL_HI ?!?! YGBFKM! > there goes the neighborhood. > > I am removing RCVD_IN_DNSWL_HI checks on our servers right now. I encourage you to develop a habit of verifying information before making decisions based on it. -- "Let's just say that if complete and utter chaos was lightning, then he'd be the sort to stand on a hilltop in a thunderstorm wearing wet copper armour and shouting 'All gods are bastards'." - The Color of Magic http://www.ChaosReigns.com
