Charles Account:
> 
> Hi,
> 
> I have been asked to see if we can streamline the events by using
> tcp interface instead ldap.
> I've read the man tcp_table page and the protocol is pretty straightforward.
> I was unable to find any references on implementation details nor examples.
> Does anyone have any 'tcp table implementation for dummies' links?
> 
> If I wanted to replace the ldap query for transport_maps, the ldap
> search expression and response
> is specified in the query_filter/result_attribute. 
> How does postfix generate a 'get' query for the transport?

As documented in the tcp_table manpage, the client sends a request,
and the server sends one reply.

As with LDAP and *SQL, Postfix provides the client, you provide
the server.

The client "get" request format is:

   get SPACE key NEWLINE

The server reply format is one of:

   500 SPACE text NEWLINE
   400 SPACE text NEWLINE
   200 SPACE text NEWLINE

The text is encoded.

> Can I use the same query_filter,
> result_attribute and result_filter I am using for ldap
> (ie transport_maps = tcp:/opt/zimbra/conf/tcp-transport.cf)?

The tcp_table manpage does not mention filters, and therefore
such functionality does not exist.

        Wietse

Reply via email to