Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: local policy)
Date: Tue, 3 Jun 2008 13:46:47 +0000 (UTC)
From: D Hill <d.hill@yournetplus.com>
To: users@spamassassin.apache.org
Subject: Re: google netblocks records etc
In-Reply-To: <48454777.2020409@netoyen.net>
Message-ID: <alpine.BSF.1.10.0806031346210.10420@duane.dbq.yournetplus.com>
References: <004f01c8c4e5$c7563650$9e00000a@msys1>
 <48444FB8.5070300@perkel.com> <000801c8c4ee$87e288d0$4201a8c0@msys1>
 <20080603063231.GA4915@posti.hege.li>
 <45794.RkEUX0YQVF8=.1212487001.squirrel@mail.junc.org>
 <20080603103438.GA6781@posti.hege.li>
 <52177.RkEUX0YQVF8=.1212494549.squirrel@mail.junc.org>
 <20080603124231.GA8125@posti.hege.li>
 <alpine.BSF.1.10.0806031304540.10184@duane.dbq.yournetplus.com>
 <48454777.2020409@netoyen.net>
User-Agent: Alpine 1.10 (BSF 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Tue, 3 Jun 2008 at 15:30 +0200, mouss@netoyen.net confabulated:

> D Hill wrote:
>> [snip]
>> In Postfix:
>>
>>   reject_unknown_reverse_client_hostname
>>     Reject the request when the client IP address has no address->name
>>     mapping.
>>
>>   reject_unknown_client_hostname
>>     Reject the request when 1) the client IP address->name mapping fails,
>>     2) the name->address mapping fails, or 3) the name->address mapping
>>     does not match the client IP address.
>> 
>> reject_unknown_client_hostname would be what you are calling confirmed 
>> reverse. If I were to use that, support would start getting phone calls and 
>> customers would start getting upset.
>
> He is about check_client_access.
>
> recent postfix also have check_reverse_client_hostname_access which acts on 
> PTR (unconfirmed rDNS), but is intended for blocking, not whitelisting.

Yes. Don't know where my head was...