On 8/3/2011 9:23 PM, Wietse Venema wrote:
I have another scenario
tcp:host:port
tcp:/path/name
Sorry, tcp:/path/name is bad user interface design. Everywhere else
in Postfix, one has to specify the socket TYPE before the socket
NAME (with BC compatibility for programs such as the SMTP client
or
Hari Hendaryanto:
[ Charset ISO-8859-1 unsupported, converting... ]
> On 8/2/2011 2:29 AM, Wietse Venema wrote:
> > Hari Hendaryanto:
> >> Hello,
> >>
> >> I've created a patch that mimicked tcp_table. however, the table lookups
> >> are directed to a unix domain socket instead of tcp servers.
> >>
On 8/2/2011 2:29 AM, Wietse Venema wrote:
Hari Hendaryanto:
Hello,
I've created a patch that mimicked tcp_table. however, the table lookups
are directed to a unix domain socket instead of tcp servers.
Actually, the patch itself is a modification of the source code of
tcp_table.
Map names have
On 8/2/2011 2:29 AM, Wietse Venema wrote:
Hari Hendaryanto:
Hello,
I've created a patch that mimicked tcp_table. however, the table lookups
are directed to a unix domain socket instead of tcp servers.
Actually, the patch itself is a modification of the source code of
tcp_table.
Map names have
Hari Hendaryanto:
> Hello,
>
> I've created a patch that mimicked tcp_table. however, the table lookups
> are directed to a unix domain socket instead of tcp servers.
> Actually, the patch itself is a modification of the source code of
> tcp_table.
>
> Map names have the form usock:/path/to/soc
