--On Thursday, September 28, 2006 1:07 AM -0400 Barry Warsaw <[EMAIL PROTECTED]> 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: # # [EMAIL PROTECTED] transport:nexthop # Mail for [EMAIL PROTECTED] is delivered through # transport to nexthop. # # [EMAIL PROTECTED] transport:nexthop # Mail for [EMAIL PROTECTED] 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 # [EMAIL PROTECTED] (default: mailer-dae- # [EMAIL PROTECTED]). _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
