Yes, relay_domains, sender_access, ....and more. Maybe the easier solution is to use the ssh/keys, but is it not dangerous to store private keys on a DMZ ?
Luis /dev/rob0 wrote: > > On Thu, Feb 24, 2011 at 02:18:07PM -0800, Luis Esteves wrote: >> In our organisation we have 4 postfix servers. >> Each time i need to add a new configuration to the transport >> file (for a new domain), i need to update the transport file on >> each server. This is cumbersome. Connect on each server with ssh, >> update the transport file, et run make to generate a db file. > > Since we're talking about transport_maps here, my preference is DNS > rather than transport_maps. I'd use DNS views such that each mail > host sees the internal MX for each new domain rather than the MX as > seen in the global DNS. > > Sounds like you're also talking about relay_domains and possibly > relay_recipient_maps as well. You would still need a means of > updating those, but that could be scripted and use SSH keys as > suggested. Networked map types are possible for these, but in the > case of relay_domains, not recommended. > -- > Offlist mail to this address is discarded unless > "/dev/rob0" or "not-spam" is in Subject: header > > -- View this message in context: http://old.nabble.com/Update-Postfix-transport-file-on-multiple-servers-tp31008507p31018639.html Sent from the Postfix mailing list archive at Nabble.com.
