rihad wrote:
rihad wrote:
What's going on? How is Postfix supposed to learn the whole
mydestination list if there's no such SQL template? I thought Postfix
would deduce a "select k from mydestination" query or similar on its
own. The manpage is ambiguous in this regard.
Answering to myself: OK, Postfix seems to wish to learn mydestination
"lazily", that is, it issues SQL queries only when receiving mail to
decide what to do with it.
of course! postfix will not load a mysql table in memory. if it were so,
then this would be useless: you could simply dump the sql tables before
into a file ;-p
Lack of the way to choose to cache query
results is pretty surprising. Moreover, a simple telnet to SMTP port and
then issuing RCPT TO: [EMAIL PROTECTED] results in _4_ successive queries
every time!
run
# postconf | egrep "(mydestination|parent_dom)"
you'll need to read about lookup order and about mysql table.
consider using proxymap (proxy:mysql:....)
Anyway, it is generally not recommended to put domain lists
(mydestination, relay_domains, virtual_*_domains), transport and
relocated maps in a remote backend.
SELECT 1 FROM mydestination WHERE k='bar.com'
