241905Re: Whitelist a host using check_client_access before the rbl check?
- Aug 4 8:36 AMOn Mon, Aug 04, 2008 at 10:56:36AM -0400, Brian Evans - Postfix List wrote:
> Nicolas KOWALSKI wrote:Ok, I think I get it now.
>> On Mon, Aug 04, 2008 at 08:58:01AM -0400, Charles Marcus wrote:
>>> On 8/4/2008, Nicolas KOWALSKI (niko@...) wrote:
>>>> Aug 4 14:17:18 petole postfix/smtpd: NOQUEUE: reject: RCPT
>>>> from 225.96.68-86.rev.gaoland.net[126.96.36.199]: 554 5.7.1 Service
>>>> unavailable; Client host [188.8.131.52] blocked using
>>> THAT was the client...
>>>> from=<nicolas.kowalski@...> to=<niko@...>
>>>> proto=ESMTP helo=<demisel.dyndns.org>
>>> THAT was the helo...
>>> So, you're trying to whitelist a client using its helo...
>> But demisel.dyndns.org (currently) resolves to the above address
>> (184.108.40.206) ; why doesn't postfix get it?
> This is how it works:
> Postfix receives a connect from an IP and does a lookup on that IP.
> See what it returns yourself with 'host 220.127.116.11'
> In your case, the client address was 225.96.68-86.rev.gaoland.net (which
> is a unqualified RDNS entry for a dynamic pool).
> This is the value that check_client_access can find (either name or IP)
> The client said 'EHLO demisel.dyndns.org'.I apparently have no other choices to whitelist-before-rbl such a
> This is the value that check_helo_access can find, though somewhat
> unreliable to whitelist.
dynamic pool's host.
Thanks to all,
- << Previous post in topic Next post in topic >>