| |||||||||||||||||||||||||||||||
|
I have a Postfix/DBMail server, so that DBmail is the sole *virtual_transport* in the system. I am using a mysql lookup for *virtual_mailbox_maps* to validate existing users. It all works wonderfully. Since I am not using any catch-all users 'user@' I figured it will be nice to make *virtual_mailbox_domains* a mysql lookup as well. Here is my table: user = dbmail password = XXXXXXX hosts = 127.0.0.1 dbname = dbmail query = SELECT `alias` FROM dbmail_aliases WHERE `alias` like '%%@%s' And it works just as expected. The problem is that when I stopped the mysql server to see what impact it would have, every new smtpd process blocked indefinitely. After about 2 minutes I eventually got this: Jul 28 08:54:56 Arzamas postfix/master[4191]: warning: service "smtp" (25) has reached its process limit "100": new clients may experience noticeable delays Jul 28 08:54:56 Arzamas postfix/master[4191]: warning: to avoid this condition, increase the process count in master.cf or reduce the service time per client I started back mysql - a rush of queries came in, and the server kept working as before. I looked in the docs for any sort of table lookup timeout, but did not find anything. Did I do something wrong or is this a problem with postfix? By the way the same does not happen with the *virtual_mailbox_maps* lookup: query = SELECT `alias` FROM dbmail_aliases WHERE `alias` = '%s'. If the mysql server is unreachable the client immediately receives: 451 4.3.0 <address>: Temporary lookup failure Thank you for your help. Peter
| ||||||||||||||||||||||||||||||
© 2004-2008 readlist.com