Michael:
> > Ubuntu Postfix package sets myorigin to /etc/mailname, which seems to
work
Weitse:
> The documented behavior is supported, as in, bugs fixed and backwards
> compatibility provided as Postfix evolves. Undocumented behavior is
> unsupported.
Peter:
> This is a debian modification, it is not supported by Postfix.
Wow. OK. So, I guess I should remove the /etc/mailname setting. Strange.
It's been that way since at least Ubuntu 12.04 LTS., perhaps earlier.
What about viewing the value which is set by reading a file?
For example: mynetworks = ${config_directory}/filename
Postconf -x will resolve $config_directory. But I don't see a postconf
option that would show me what mynetworks is actually set to.
> There is no 'include' command for main.cf or master.cf files, because
> a) it would complicate how commands like 'postconf -e' work, b)
> it would complicate the 'postfix check' that Postfix parameters
> don't come from a file or directory that is writable by non-root
> users, c) other considerations that were hashed out many years ago.
OK. Thanks.
> I suggest that you have a script on each machine that customizes a
> generic Postfix main.cf and master.cf file. As of a few releases
> you can use 'postconf -F' to customize each master.cf field and
> 'postconf -P' to customize each '-o name=value' parameter setting
> in master.cf.
>
> In a distant past I might suggest using rdist to move and customize
> files; nowadays people might use Puppet, Chef, and the like to a
> similar effect.
OK. Thanks.
Michael
