Topic: RDNS_NONE hitting all the time
I have a small problem with the RDNS_NONE rule in spamassasin, it's hitting all the time (at least almost all the time), even if the partner server has proper name -> address -> name resolution.
X-Spam-Status: No, score=-1.872 required=4 tests=[AWL=0.008, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_SORBS_WEB=0.619, RDNS_NONE=0.1, SPF_PASS=-0.001] autolearn=no Authentication-Results: mx2.xxxxx.com (amavisd-new); domainkeys=pass firstname.lastname@example.org Received: from mx2.xxxxx.com ([127.0.0.1]) by localhost (mx2.xxxxx.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xc8lRjM3yS-L for <email@example.com>; Mon, 1 Mar 2010 17:07:22 +0200 (EET) X-Original-Helo: outbound-mail-359.bluehost.com (iRedMail: http://code.google.com/p/iredmail/) Received: from outbound-mail-359.bluehost.com (unknown [18.104.22.168]) by mx2.xxxxx.com (iRedMail) with SMTP id 98BA22C1016B for <firstname.lastname@example.org>; Mon, 1 Mar 2010 17:07:21 +0200 (EET) Received: (qmail 17033 invoked by uid 0); 1 Mar 2010 15:07:20 -0000 Received: from unknown (HELO box467.bluehost.com) (22.214.171.124) by oproxy1.bluehost.com.bluehost.com with SMTP; 1 Mar 2010 15:07:20 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=touch-media.ro; h=Received:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language:X-Identified-User; b=e7L5GnDwlxO/PeHFJxiboB8tlEDQ9kBdLSN+lA0xZtZg0iLUkfgrZK3alVF6mvrBETPK2Ab1iaECLw0flL3A65VUhx/VimH/5ZyjCijMYgko0F1EBjBDX48avLz2rlTt; Received: from [126.96.36.199] (helo=Blablabla) by box467.bluehost.com with esmtpa (Exim 4.69) (envelope-from <email@example.com>) id 1Nm7DH-0006R1-4l for firstname.lastname@example.org; Mon, 01 Mar 2010 08:07:20 -0700
outbound-mail-359.bluehost.com -> 188.8.131.52 -> outbound-mail-359.bluehost.com, so the name resolution is consistent.
According to spamassassin wiki, there always is checked the last untrusted relay. So, what is wrong in this case? Why it isn't working?
- Urgent issue? Pay iRedMail developer to solve it remotely at $39.