Hello Nataniel, NK> Then I put another domain in transport (marilon.com.br and NK> .marilon.com.br) table... Done postmap and configured accounts in NK> DBMail. Result: the only account that receive email is NK> [EMAIL PROTECTED] the others that I created just return a NK> message like this:
The problem is that Postfix doesn't know it is the final destination for the new domain. Just having a transport for it doesn't do it. And, to be honest, I didn't have any luck with the officially-sanctioned (by postfix.org) way of doing it... So, I modified what Eelco directed to me. Assuming that you've compiled postfix with SQL support, you can use a single SQL table for both the 'mydestination' and 'transport' parameters of postfix. It's the first of those that you don't have yet. Here's the shortened version of how to do it: my_trans.cf contents: --- user = postfix password = [password] dbname = forwarder table = mytransport hosts = 192.168.2.142 select_field = transport where_field = domain --- Excerpt from main.cf: --- mydestination = mysql:/etc/postfix/my_trans.cf transport_maps = mysql:/etc/postfix/my_trans.cf --- Partial contents of forwarder.mytransport table: --- id domain transport comment 1 csrye.org dbmail: First Test 2 espi.com dbmail: Second test victim 3 cruftware.com dbmail: 4 dididahdahdidit.com dbmail: --- With this setup, adding a domain does NOT require shutting down postfix; simply insert the domain and transport into the mytransport table. My database for this is named "forwarder" because it was part of some other project; you COULD include the transport table in the dbmail database... I may eventually move mine. -- Jeff Brenton President, Engineered Software Products, Inc http://espi.com Questionable web page: http://dididahdahdidit.com Liberalism grants you the freedom to advocate any idea*. * Please see http://www.dididahdahdidit.com/except.php for a current list of exceptions
