On Mon, Mar 28, 2016 at 04:52:04PM -0700, Michael Fischer wrote:
> In Postfix 2.10, the default value of
> $parent_domain_matches_subdomains changed from:
>
> parent_domain_matches_subdomains =
> debug_peer_list,fast_flush_domains,mynetworks,permit_mx_backup_networks,qmqpd_authorized_clients,smtpd_access_maps
>
> To:
>
> parent_domain_matches_subdomains =
> debug_peer_list,fast_flush_domains,mynetworks,permit_mx_backup_networks,relay_domains,qmqpd_authorized_clients,smtpd_access_maps
No such change took place.
20011119
Feature: configurable parent domain matching strategy for
transport map lookups. File: trivial-rewrite/transport.c.
New parent_domain_matches_subdomains parameter. This lists
all the Postfix features where a domain name matches itself
and all its subdomains (instead of requiring ".domain.name"
for subdomain matches). Planning for future backwards
compatibility :-) File: global/match_parent_style.c.
Since 2001, the default has been:
/*
* Backwards compatibility: foo.com matches itself and names below foo.com.
*/
#define VAR_PAR_DOM_MATCH "parent_domain_matches_subdomains"
#define DEF_PAR_DOM_MATCH VAR_DEBUG_PEER_LIST "," \
VAR_FFLUSH_DOMAINS "," \
VAR_MYNETWORKS "," \
VAR_PERM_MX_NETWORKS "," \
VAR_QMQPD_CLIENTS "," \
VAR_RELAY_DOMAINS "," \
SMTPD_ACCESS_MAPS
> (Note the addition of "relay_domains".)
Sorry, that's simply not the case.
> Although this seemed like an innocuous change, it caused a temporary
> outage for us after we upgraded from 2.9.1 to 2.10.
Any change in your configuration is not the result of upstream
changes in Postfix. The "relay_domains" element is still there
even in 3.2 snapshots.
$ postconf -d mail_version parent_domain_matches_subdomains
mail_version = 3.2-20160314
parent_domain_matches_subdomains =
debug_peer_list,fast_flush_domains,mynetworks,permit_mx_backup_networks,qmqpd_authorized_clients,relay_domains,smtpd_access_maps
--
Viktor.
