Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <48454777.2020409@netoyen.net>
Date: Tue, 03 Jun 2008 15:30:31 +0200
From: mouss <mouss@netoyen.net>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
CC: users@spamassassin.apache.org
Subject: Re: google netblocks records etc
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>
In-Reply-To: <alpine.BSF.1.10.0806031304540.10184@duane.dbq.yournetplus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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.