Am 15.08.2012 03:18, schrieb Viktor Dukhovni: > I would also note that trivial-rewrite(8) (like proxymap(8)) is > already a multi-client service, so typically, there are a lot fewer > trivial-rewrite(8) processes than smtpd(8)'s or cleanup(8)'s. > Therefore any savings in further consolidating database connections > are likely offset by unnecessary indirection. > > So bottom-line, don't use proxymap for tables that are used only > by trivial-rewrite(8). We could perhaps make Postfix ignore proxymap > in trivial-rewrite(8), but it is not clear that this would not be > surprising to a lot of people...
please do not proxymap may be choosed in setups like yours where the dealy is not a big deal because not sucha high mail-flow but the whole mailservcies including storage are mysql-based and more database connections with the per-thead-buffer-overhead would be a bigger problem than any delay raised connection count may lead here in overthink the max-connections and memory-allocations of the virtual machine running the mail system this setup may not sitisfy each workload, but it does ours perfectly since 2009 and the main design-decision was "really anything per mysql-configuration to write as flexible as possible web-interfaces" additionally any postfix-relay on webservers is using the origin-db and a slave as fallback for decide if a sender is allowed and if there are sender-dependent relayhosts configured in the infrastrcuture somehing around 25.000 lines of php-code which was a hard-job while learning-by-doing postfix/dovecot/dbmail in 2009 :-)
signature.asc
Description: OpenPGP digital signature
