On 6/1/2010 2:22 PM, Victor Duchovni wrote:
On Tue, Jun 01, 2010 at 02:09:23PM -0400, Curtis Maurand wrote:
I have in the main.cf
relay_domains=< a couple of domains> mysql:/etc/postfix/transport.cf
transport_maps = mysql:/etc/postfix/transport.cf
Don't use the transport table directly as a relay domain table, some day
you'll need special routing for an external domain, that will become an
inadvertant relay domain.
I have lots of email addresses that need to be delivered to the dbmail
lmtp agent. How would you suggest I map those. Currently they go via:
left hand: domain.tld right hand: dbmail-lmtp:127.0.0.1:24
I was editing the table by hand, but it seemed to be easier to do via
the dbmail administrator and the mysql lookup. two domains, I'm simply
filtering mail for and then sending along to their exchange server via
smtp (sort of a postini type service.).
Also, it is best to avoid mysql, ldap, ... for the transport table and
relay domain list. These are used by the queue manager (via trivial-rewrite)
and are performance critical. I recomment indexed files for these, not
database sources.
such as a regular map file (e.g. hashtable)? That becomes unwieldy and
unscalable for a large number of domains doesn't it. Isn't that the
reason for using mysql? It does these types of lookups very fast.
There is also the added advantage that I can index that table. I
suppose I could write an interface to a hash table, but not fun.
> You have not defined "relay_recipient_maps".
That was the problem. Its now working as advertised.
Thanks,
Curtis
