Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Tue, 24 Nov 2015 12:29:26 +0100
From: Benny Pedersen <me@junc.eu>
To: users@spamassassin.apache.org
Subject: Re: question re/ =?UTF-8?Q?RDNS=5FNONE?=
Organization: Jersore Underground Network Center
In-Reply-To: <56544266.1010003@thelounge.net>
References: <20151121154109.GA3386@c720-r276659>
 <440aff12-1277-4bbd-9085-c9dbfae0a894@unixarea.de>
 <20151121185741.4a836d34@gumby.homeunix.com>
 <20151124102220.GA2855@c720-r276659>
 <313eb4f4ba25c54d33b56e31228ce1ab@junc.eu> <56544266.1010003@thelounge.net>
Message-ID: <9a5287590f510a96a46255f6ea043723@junc.eu>
User-Agent: Roundcube Webmail/1.0.6

Reindl Harald skrev den 2015-11-24 11:56:

> it's the exim of the ISP

with old version of exim

> it's the exim of the ISP

with old version of exim

>> again disable of rdns_none is not the solution, so why fokus on that?
> 
> because *it is* the solution damned when "make spamassassin exceptions
> for the faulty isp headers" would do exactly the same, not fire the
> rule and since it affects *every* mail, well disable it

no isp might recieve mail from more then one single ip / domains, so 
solve rdns_none with disable is incorrect with score 0

if the 3 header exeption is added it would still work on other isps spam 
sources breaking rfc rules on how headers should be

>> spamassasssin is not a single rule spam scanner / tagger
> and hence you disable the rules which don't match your environment

bah, upgrade exim is not that hard is it ?