>> Patrick Saweikis wrote: >> >> Hello >> >> >> >> We are using postfix 2.3.8 and have it integrated with >> mysql and transport maps are set on a per domain basis this way >> (transport_maps = mysql:/etc/postfix/mysql-transport.cf, >> mysql-transport.cf contains the authentication and mysql query to >> retrieve this info). >> >> >> >> We are now trying to incorporate a way to create >> redundancy on the relay end, so currently we may just have the >> transport map set to "smtp:[10.1.1.7]" and are trying to find a way to >> tell it that if it cannot relay to the transport_maps location, try >> this other. I had done some research and found that >> smtp_fallback_relay should do what I need. I tried implementing this >> without success, I am getting "unknown mail transport error" when >> enabling that option, whether the transport_maps location is >> accessible or not. >> >> >> Any ideas on how we can accomplish this? Is >> smtp_fallback_relay the correct method to do this? Any help would be >> greatly appreciated. Thanks. > > >Remember, transport_maps overrides all other settings. > >The simplest way is to setup a local DNS domain (example.local for >instance) with MX records of the same priority. >Then, replace the IP with the local domain you created. >This adds a small amount of cost for each message. > >Brian
This worked perfectly! Thanks for the tip -- I think I was just trying to over-complicate things. Here is what I ended up doing: DNS: patsaw.local A, mx1.patsaw.local, 10.1.1.7 A, mx2.patsaw.local, 10.1.1.12 MX, 0, mx1.patsaw.local MX, 10, mx2.patsaw.local Postfix for patsaw.com: transport_maps=smtp:patsaw.local Test1, successfully relayed to patsaw.com on 10.1.1.7 Test2, changed mx1.patsaw.local to 1.2.3.4 - Successfully delivered to 10.1.1.12 The one problem I ran into is that we normally use the format smtp:[10.1.1.7], when I kept patsaw.local in brackets it tried to deliver to the A record, I had to take it out of brackets for postfix to do an mx lookup. Thanks Again!
