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:
-- Noel Jones
