2009/7/23 Clunk Werclick <clunk.wercl...@wibblywobblyteapot.co.uk>: > On Wed, 2009-07-22 at 11:04 -0500, Noel Jones wrote: >> Clunk Werclick wrote: >> > I think perhaps 4-12 queries per message is not optimal? >> > If server handle 50,000 a day X 12 that is quite a lot? I don't think >> > it is going to get may fields returned for .co.uk .uk in my database?
It was a rhetorical question. :) >> Postfix does the lookups required to route your mail properly. > It is a bit silly to do this for .co.uk then .uk yes? Not necessarily, it's doing what it's been configured to do. It just so happens that the configuration is a bit "legacy" - as documented, it's a backwards compatibility feature. You can turn it off, though it *may* cause behaviour to change in ways you don't expect. >> For the tables that I suggest you keep in a hash, if you want >> to still store the data in mysql you can automate a daily dump >> to a hash file for postfix to use. > > This seems to be a bit silly, that is what the database is for, but > thank you for your advice. I may have to do this to stop this DoS type > of hammering for silly lookups. Thank you anyhow. You need to ask yourself if this is a real problem, or something you're just imagining. Mysql generally works fine, 50,000 messages a day at 12 queries each, equates to several queries per second. This is an "easy" load. If you're concerned, then disable the parent domain searching as mentioned before. If you're worried about mysql's stability then you probably shouldn't be using it. Using a database as a table backend carries its own share of risks and failure cases. I notice in your postconf output that you're not using proxymap with mysql. This is generally recommended: http://www.postfix.org/MYSQL_README.html (notes on client connections) http://www.postfix.org/proxymap.8.html (specific proxy:mysql example)
