On Fri, 10 Apr 2009, Darren Pilgrim wrote: > I have a setup with postfix MXes handing mail off to postfix backend > mailbox servers via smtp. I currently have transport_maps returning > "relay:[fqdn]" where fqdn is the backend server hostname to which mail > is delivered. I want to change this to individual transports (one per > backend) so I can defer delivery, control MX-side queue lifetimes and > other timeouts, etc. on a per-backend basis. Is there a way to specify > within master.cf the next hop of an smtp(8) transport? Will setting > relayhost on each transport do this? For example: > > In master.cf: > dojebon unix - - n 0 0 smtp -o relayhost=[dojebon.example.com] > haagen unix - - n 0 0 smtp -o relayhost=[haagen.example.com]
This will not work as you probably expect. One of the features of transport_maps is to overrule the relayhost setting. > And have transport_maps return "dojebon" or "haagen" as appropriate. You probably mean having "dojeban:" or "haagen:" on the RHS of a transport(5) table. > Or am I limited to cloning relay and specifying the nexthop when > returning the transport? For example: You need to specify the nexthop; otherwise, transport(5) will use the recipient domain name to direct email to the appropriate MX. -- Sahil Tandon <sa...@tandon.net>
