241901Re: Whitelist a host using check_client_access before the rbl check?
- Aug 4, 2008Nicolas KOWALSKI wrote:
> On Mon, Aug 04, 2008 at 08:58:01AM -0400, Charles Marcus wrote:This is how it works:
>> Let me give this one a try... I *think* i see the problem...
>> 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[220.127.116.11]: 554 5.7.1 Service
>>> unavailable; Client host [18.104.22.168] 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
> (22.214.171.124) ; why doesn't postfix get it?
Postfix receives a connect from an IP and does a lookup on that IP.
See what it returns yourself with 'host 126.96.36.199'
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'.
This is the value that check_helo_access can find, though somewhat
unreliable to whitelist.
- << Previous post in topic Next post in topic >>