On Tue, Mar 29, 2016 at 10:55:31AM -0500, /dev/rob0 wrote:

> > If it's not a bug, additional explanation in the documentation as 
> > to its behavior would be useful.
> 
> I agree.  I had the same question some years ago, until it was 
> explained to me.
> 
> The only documentation I know of is
> postconf.5.html#parent_domain_matches_subdomains and
> postconf.5.html#relay_domains :
> 
> relay_domains (default: $mydestination)
> 
>     What destination domains (and subdomains thereof) this system
>     will relay mail to. Subdomain matching is controlled with the 
>     parent_domain_matches_subdomains parameter.

There are a few features for which the semantics of p_d_m_s are
explained in more detail, for example:

http://www.postfix.org/access.5.html

    EMAIL ADDRESS PATTERNS
       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@domain
              Matches the specified mail address.

       domain.tld
              Matches domain.tld as the domain part of an email address.

              The pattern domain.tld also matches subdomains,  but  only  when
              the  string  smtpd_access_maps  is  listed  in  the Postfix par-
              ent_domain_matches_subdomains configuration setting.

       .domain.tld
              Matches subdomains of  domain.tld,  but  only  when  the  string
              smtpd_access_maps   is   not   listed   in   the   Postfix  par-
              ent_domain_matches_subdomains configuration setting.

http://www.postfix.org/transport.5.html

    TABLE SEARCH ORDER
       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@domain transport:nexthop
              Deliver mail for user+extension@domain through transport to nex-
              thop.

       user@domain transport:nexthop
              Deliver mail for user@domain through transport to nexthop.

       domain transport:nexthop
              Deliver mail for domain through transport to nexthop.

       .domain transport:nexthop
              Deliver mail for any subdomain of domain  through  transport  to
              nexthop. This applies only when the string transport_maps is not
              listed  in  the  parent_domain_matches_subdomains  configuration
              setting.  Otherwise, a domain name matches itself and its subdo-
              mains.

Unfortunately, not all lookup mechanisms have a separate manpage
with this level of detail.  The rest is inferred from economy of
mechanism.  Every table in which parent domain matching is supported
behaves like access(5) and transport(5) with respect to leading
dot.

-- 
        Viktor.

Reply via email to