Am 05.11.2014 17:31, schrieb Wietse Venema:
> Viktor Dukhovni:
>> On Wed, Nov 05, 2014 at 10:47:33AM -0500, Wietse Venema wrote:
>>
>>> postfix-us...@arcsin.de:
Since the tcp_table is consulted with a full address, it can produce wrong
answers even if it is placed at the last position of
Viktor Dukhovni:
> On Wed, Nov 05, 2014 at 10:47:33AM -0500, Wietse Venema wrote:
>
> > postfix-us...@arcsin.de:
> > > Since the tcp_table is consulted with a full address, it can produce wrong
> > > answers even if it is placed at the last position of transport_maps.
> >
> > I have a revolutiona
On Wed, Nov 05, 2014 at 10:47:33AM -0500, Wietse Venema wrote:
> postfix-us...@arcsin.de:
> > Since the tcp_table is consulted with a full address, it can produce wrong
> > answers even if it is placed at the last position of transport_maps.
>
> I have a revolutionary suggestion: DO NOT REPLY WIT
postfix-us...@arcsin.de:
> Since the tcp_table is consulted with a full address, it can produce wrong
> answers even if it is placed at the last position of transport_maps.
I have a revolutionary suggestion: DO NOT REPLY WITH INCORRECT INFORMATION.
Wietse
Wietse Venema:
> Damian Lukowski:
>> Hi,
>>
>> is there a reason that tcp_table has the DICT_FLAG_PATTERN flag
>> instead of DICT_FLAG_FIXED? One could create more flexible transport
>> map chains if tcp_table was also queried for pure domains.
> Like pcre, regexp, and socketmap, tcp_table is quer
Damian Lukowski:
> Hi,
>
> is there a reason that tcp_table has the DICT_FLAG_PATTERN flag
> instead of DICT_FLAG_FIXED? One could create more flexible transport
> map chains if tcp_table was also queried for pure domains.
Like pcre, regexp, and socketmap, tcp_table is queried only with
the full
Hi,
is there a reason that tcp_table has the DICT_FLAG_PATTERN flag instead of
DICT_FLAG_FIXED?
One could create more flexible transport map chains if tcp_table was also
queried for pure domains.
Regards
Damian
