Hi all,
Could someone clarify the following passage from the TCP_TABLE manual:
REQUEST FORMAT
Each request specifies a command, a lookup key, and possibly a lookup
result.
get SPACE key NEWLINE
Look up data under the specified key.
put SPACE key SPACE value NEWLINE
This request is currentl
da...@pavlotzky.nl:
> Hi all,
>
> Could someone clarify the following passage from the TCP_TABLE manual:
>
> REQUEST FORMAT
> Each request specifies a command, a lookup key, and possibly a lookup
> result.
>
> get SPACE key NEWLINE
> Look up data under the specified key.
>
> put SPACE key SP
On 01/25/2018 05:58 PM, Viktor Dukhovni wrote:
This is not good advice, it breaks delivery to other domains. Much better
to run a local caching resolver. Note also that the OP reports that raising
concurrency does not improve throughput by much. If DNS lookups were slow
higher concurrency woul
> On Jan 26, 2018, at 4:23 AM, da...@pavlotzky.nl wrote:
>
> Could someone clarify the following passage from the TCP_TABLE manual:
While not an answer to the question you were asking, something to
keep in mind is that you could also use socketmap rather than tcp
tables:
http://www.postfix.
On 26 Jan 2018, 12:46 +0100, Wietse Venema , wrote:
> It means that
>
> EVERY COMMAND specifies a command, a lookup key.
>
> SOME COMMANDS ALSO specify a lookup result.
>
> Wietse
Clarified.
Thanks!
Kind regards,
David
Thanks for the heads up viktor. In this case the lookup table (postsrsd) is
already implemented as a tcp lookup table. I thought I could maybe find a
little wiggle room to send some state to postsrsd (original recipient) by
misusing “a possible lookup result”...
Kind regards,
David
On 26 Jan 2
On Wed, January 24, 2018 3:55 am, Noel Jones wrote:
> There is no simple regexp, but there is the fqrdns.pcre project. The
> project is a large hand-maintained list of dynamic hostnames with a goal of
> zero false positives. It's not perfect, but it's useful and safe for
> general use.
>
> https:
