From: Michael Tokarev (no email)
Date: Sun Feb 01 2004 - 15:04:12 EST
wrote:
[]
> Make sure that "localhost.$mydomain" is listed in mydestination. Configure
> any virtual(5) entries you want delivered with RHS values of the form:
>
> out-addr at localhost
>
> This will work for all values of the myorigin setting (which per your
> description is not yet local on the replacement machine). It will also
> work in production without changes.
Another possibility is to do some transport magic.
I personally don't like when original recipient
address changes during delivery (as in the above
example).
With per-address transport map entries, you may
specify:
local:
in transport maps. With appropriate alias entry
for in-addr, your aliases will work (IF the domain
in question is virtual_mailbox_domain, not
virtual_alias_domains - in the latter case, postfix
will bounce the message anyway).
And for mailinglist managers, I prefer different
solution:
ml-transport:ml-submit
ml-transport:ml-request
ml-transport:ml-subscribe
...
where ml-transport is a transport defined in
master.cf, usually pipe(8) running with appropriate
user id, that will pass message to a mailinglist
software with proper information about the mailinglist
in question and the operation requested.
transport map:
mailman:post:avcheck
mailman:admin:avcheck
mailman:bounces:avcheck
mailman:confirm:avcheck
mailman:join:avcheck
mailman:leave:avcheck
mailman:owner:avcheck
mailman:request:avcheck
mailman:subscribe:avcheck
mailman:unsubscribe:avcheck
main.cf:
mailman unix - n n - 3 pipe
flags=uF user=list argv=/bin/sh /var/lib/mailman/postfix.sh ${nexthop}
/var/lib/mailman/postfix.sh:
#! /bin/bash
exec /usr/bin/python /var/lib/mailman/scripts/${1%%:*} ${1#*:}
Similar setup may be used for sympa as well.
/mjt
|
|
|