Hi again, Still working on this - something that I didn't mention (sorry, should have) was that the Postfix gateway is multi-homed and that the other edge Postfix systems (and the internal mail servers) are each on different subnets.
Example: a.com: internal mail server 192.168.200.1, edge proxy 192.168.201.1 b.com: internal mail server 192.168.210.1, edge proxy 192.168.211.1 c.com: internal mail server 192.168.220.1, edge proxy 192.168.221.1 ...and so on. The gateway system has a NIC for each pair of systems and the traffic is forwarded through a router from the internal server to the gateway and then either back to one of the other internal servers or out to the edge proxy that matches the sender's domain from the internal mail server. How does this new info affect the previous solution that you provided? Thanks... On Fri, Feb 27, 2009 at 6:50 PM, Iad Scoot <iad.sc...@gmail.com> wrote: > Gotcha - and after a "little more" research I've found a couple of examples > online. It'll be Monday before I can try but much thanks again - I will post > back my outcome. > > - iad > > On Fri, Feb 27, 2009 at 6:33 PM, Barney Desmond <barneydesm...@gmail.com > > wrote: > >> 2009/2/28 Iad Scoot <iad.sc...@gmail.com>: >> > Hey thanks for the info - it looks like (from what I've read so far) >> that >> > the sender_dependent_relayhost_maps parameter is for specific users - is >> > there any way to do this for any user (or all users) in a given domain >> w/o >> > having to list their full address in the map file? >> >> That should work; according to the documentation, "The tables are >> searched by the envelope sender address and @domain". >> >> I admit I haven't *actually* used this myself, but I'm guessing you >> either use "senderdomain.com" (like a transport table) or >> "@senderdomain.com" (virtual-style catchall) as the key to the lookup. >> Testing will tell you in a matter of minutes. >> > >
