On Fri, May 01, 2009 at 01:54:03PM -0400, Eric Cunningham wrote:
> I think I've found a/the fix for re-enabling the original behavior of my
> transport maps and MX relaying. I added .$mydomain to mydestination in
> main.cf. This is in addition to $mydomain which was already in
> mydestination.
>
> $mydomain vs. .$mydomain is subtle but apparently important.
Postfix will never search for ".example.com" domains in the
$mydestination list, so this change has no effect. Perhaps in making
this change you also triggered other changes that solved the problem.
Now, in fact, if you don't set "relay_domains" explicitly, as a matter
of regrettable backwards compatibility requirements, the value of
$relay_domains defaults to to "$mydestination" and in the context of
"$relay_domains", ".example.com" keys do come into play given an
appropriate setting of parent_domain_matches_subdomains.
The right solution is to set relay_domains explicitly and correctly,
rather than rely on side-effects from $mydestination.
Secondly, it appears that you have changed the default value of
parent_domain_matches_subdomains. You should review this parameter
and make sure you understand its impact.
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majord...@postfix.org?body=unsubscribe%20postfix-users>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
