|Main Archive Page > Month Archives > amavis-user archives|
Fixed a small mistake and re-wrapped the tarball, please re-fetch.
> A few questions/comments on 2.8.0-pre4. :)
> 1) avoid persistent connections to SQL and LDAP servers - at the expense
> of about 3 to 7 ms elapsed time for a reconnect; persistent connections
> from mostly idling child processes unnecessarily consume database server
> resources (e.g. a TCP socket) and may become stuck when some intermediate
> stateful device like a firewall or a NAT decides to drop stale sessions;
> reported by Jernej Porenta;
> Can this be made optional? A well written LDAP server is designed to
> handle persistent connections. I don't know what Jernej was using, but
> apparently it wasn't well designed. In any case, well designed LDAP
> servers also allow you to set a server-side timeout if you really don't
> want idle connections sitting about.
Right, forgot to make it optional, will do so.
> 2) I see you did some work on the Amavis portions. Will a scalable LDAP
> solution be supported as previously discussed? See discussion from
> 3) LDAP schema expansion to include looking domain disclaimer maps. The
> solution in 2.6.4 doesn't scale well with 10,000+ domains. (See discussion
> from 12/10/2008)
I need to refresh my memory, will take a look.
Not enough compute cycles in a day :)
I'd also like to replace the use of Net::Server::Multiplex in
amavisd-signer by 0MQ - the async support in the Net::LDAP module
is very poor.
And modify p0f-analyzer.pl to work with the new version of p0f.