[Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [8041] trunk/mailman/Mailman

[Carson Gaspar]

--On Thursday, September 28, 2006 1:07 AM -0400 Barry Warsaw 
<barry at python.org> wrote:

> Or is there some way I'm missing that would allow us to segregate
> some domain traffic to Mailman's LMTP server and other traffic to
> Postfix's standard transports?  What about Sendmail?

Shouldn't be an issue with postfix. From the default postfix transport map 
template:

# TABLE LOOKUP
#        With lookups from indexed files such as DB or DBM, or from
#        networked  tables  such  as NIS, LDAP or SQL, patterns are
#        tried in the order as listed below:
#
#        user+extension at domain transport:nexthop
#               Mail for user+extension at domain is delivered through
#               transport to nexthop.
#
#        user at domain transport:nexthop
#               Mail for user at domain is delivered through transport
#               to nexthop.
#
#        domain transport:nexthop
#               Mail for domain is delivered through  transport  to
#               nexthop.
#
#        .domain transport:nexthop
#               Mail  for  any  subdomain  of  domain  is delivered
#               through transport to  nexthop.  This  applies  only
#               when the string transport_maps is not listed in the
#               parent_domain_matches_subdomains configuration set-
#               ting.   Otherwise, a domain name matches itself and
#               its subdomains.
#
#        Note 1: the special pattern * represents any address (i.e.
#        it functions as the wild-card pattern).
#
#        Note  2:  the  null  recipient  address  is  looked  up as
#        $empty_address_recipient@$myhostname (default: mailer-dae-
#        mon at hostname).