On 01/28/2011 03:06 PM, Noel Jones wrote: > On 1/28/2011 1:53 PM, Michael Orlitzky wrote: >> On 01/28/2011 02:09 PM, Ralf Hildebrandt wrote: >>> * Michael Orlitzky<mich...@orlitzky.com>: >>> >>>> but one web server is running Mailman and can't do that (I think?) >>> If it has a seperate domain for lists, you can use: >>> >>> lists.domain.com local: >>> >>> in transport_maps and thus route that one domain to local: >>> >> >> Wouldn't that override the default virtual transport, though? I do have >> lists.example.com, but right now, everything comes in virtual and gets >> mapped to local addresses which are then aliased to pipes. So, >> >> (virtual) (local) (Mailman magic) >> memb...@lists.example.com -> members -> |/usr/bin... >> > > Not quite. > > Your virtual table rewrites it to "members". Within postfix > all addresses have a domain, so "members" is rewritten to > "members@$myorigin". Postfix then discovers the domain > $myorigin resolves to is listed in mydestination, and the > message is passed to the local transport for delivery. Local > then drops the domain name for processing since local names > have no domain. > > You can skip that process by directly writing an address > (either a whole domain or a specific address) to local with > the transport map. > > # transport > memb...@list.example.com local:
I tried with transport_maps: example.com local: and local_transport = error:... and got this (http3.viabit.com is myorigin): Jan 28 15:05:25 http3 postfix/error[20737]: 24944A302DF: to=<memb...@http3.viabit.com>, orig_to=<memb...@example.com>, relay=none, delay=2.7, delays=2.7/0/0/0, dsn=5.0.0, status=bounced(Local delivery is disabled.) The more I think about it, the more I think it should have worked. I'll try again once things slow down a bit (5pm).
