On 6/10/2014 6:32 PM, uffe wrote:
>
> Now I got it working - thanks
>
> Are tcp_table lookup "deamon" instances supposed to exit themselves - for
> every lookup - or can postfix reuse them "persistent"
>
> I'm having a hard time understanding the comment in the bugs section: The
> client does
Now I got it working - thanks
Are tcp_table lookup "deamon" instances supposed to exit themselves - for
every lookup - or can postfix reuse them "persistent"
I'm having a hard time understanding the comment in the bugs section: The
client does not hang up when the connection is idle for a l
Thanks for your swift answers
I'll try the recommendations immediately.
English is not my native language - but it did not occour to me from reading
that documentation for tcp_table lookups that returning 500 would be
aproprialte - I would have believed that is would have stopped the while
delive
On 6/10/2014 2:59 PM, uffe wrote:
> Hello,
>
> Subject: Problem understanding check_client_access and tcp_table
>
> I have a problem understanding how to properly use check_client_access with
> an external tcp_table (daemon)
>
> in my main.cf
uffe:
> smtpd_client_restrictions = check_client_access tcp:[127.0.0.1]:1
>
> But what I was expecting was to receive lookup "get" requests with the raw
> source ip address as argument - as "unknown" is not of much use for spam
> analysis.
There will be no "get client-address" query when the
Hello,
Subject: Problem understanding check_client_access and tcp_table
I have a problem understanding how to properly use check_client_access with
an external tcp_table (daemon)
in my main.cf i have put the following:
smtpd_client_restrictions = check_client_access tcp:[127.0.0.1]:1
The
