On Mon, Sep 22, 2014 at 10:45:27AM -0400, Wietse Venema wrote:
> Viktor Dukhovni:
> > On Mon, Sep 22, 2014 at 10:32:04AM -0400, Wietse Venema wrote:
> >
> > > Until now, Postfix has a default setting "append_dot_mydomain = yes".
> > > This performs autocompletion from user@host to user@host.$mydomain.
> > > But this default setting is becoming problematic.
> > >
> > > I need to find out what will break when the default is changed to "no".
> >
> > Question:
> >
> > * Will "postfix upgrade-configuration" install a backwards-compatible
> > override when upgrading systems in which the parameter is not set
> > in main.cf? And in fresh installs will the parameter be explicitly
> > set to "no"?
>
> Why do you think that I am sending out this query to the list? I
> cannot count on down-stream distros to implement such workarounds,
> as we found out with smtpd_relay_restrictions which they refused
> to implement. I had to change the built-in default in a stable
> release, and don't want to have to do that again.
I was asking what the plan is for systems that *do* run
# postfix upgrade-configuration
As for Debian, perhaps we can persuade LaMont to fix the Debian package
so that:
# postfix set-permissions
works, and
# postfix upgrade-configuration
is applied on package upgrades, and works correctly with multiple
instances. That would also take care of Ubuntu.
While I don't know what happens with RedHat, SuSE, FreeBSD and
MacOSX ports, NetBSD pkgsrc, ... I thought it would be helpful to
ask about the intended upgrade behaviour. I gather from the above
response that you would attempt to maintain a backwards-compatible
setting, and this thread is to assess impact on users who might not
benefit from the intended upgrade process.
--
Viktor.
