Hello Nathan, NZ> I was under the impression that this was what has happening. How NZ> do I tell postfix to just use mysql and not mydestination? I am a NZ> novice here so please dummy it down for me.
The first thing to do is make sure your copy of postfix is compiled with SQL capability to match the database you're using. I don't have time to go into how to do that right now, but it is necessary for SQL transport maps AND the pop-before-smtp authentication to work. After that, you need to follow this advice from a previous post I made here, for MySQL tables: When querying the table for mydestination, postfix ONLY needs to have a valid row returned. When querying for transport, it wants the routing returned. 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: --- my_trans.cf contents: --- user = postfix password = [password] dbname = forwarder table = mytransport hosts = 192.168.2.142 select_field = transport where_field = domain --- The same configuration file works for both, because Postfix doesn't care what is returned the first time, just that a row was found. ------- You can also have Postfix look at the dbmail aliases table to determine whether or not an address is deliverable, using the local_recipient_maps parameter: local_recipient_maps = mysql:/etc/postfix/mailbox.cf where mailbox.cf is similar to my_trans.cf above, except points to the dbmail aliases table. -- Jeff Brenton Vice 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
