On 02/10/2014 15:36, Wietse Venema wrote:
Birta Levente:
On 02/10/2014 14:17, Wietse Venema wrote:
Birta Levente:
On 01/10/2014 18:57, Wietse Venema wrote:
Postfix will log all uses of any old default value that will
be affected by an incompatible change.
This is not implemented yet (I installed 20141001 snapshot)? Or there is
other way to see the affected parameters?
It is logged when it is used. For example:
postfix/trivial-rewrite[25835]: using legacy default setting
append_dot_mydomain=yes to rewrite "foo" to "foo.example.com"
postfix/smtpd[27560]: using legacy default setting smtputf8_enable=no
to accept non-ASCII sender address "??@example.org" from
localhost[127.0.0.1]
After introduced these two from your example in main.cf I just saw this
a few times:
Oct 2 10:41:50 srv1 postfix[52814]: warning: Postfix is running with
backwards-compatible default settings
Oct 2 10:41:50 srv1 postfix[52814]: warning: See
http://www.postfix.org/postconf.5.html#compatibility_level for details
Oct 2 10:41:50 srv1 postfix[52814]: warning: Use "postconf
compatibility_level=1" to disable the backwards-compatible default settings
and wonder what parameters referring to.
The full story is in the RELEASE_NOTES. I will move that text into
postconf.5.
Other than that, do the solution and documentation make sense?
Wietse
After reading the RELEASE_NOTES too, I'm a little bit confused:
Let's say I haven't specified at all before the append_dot_mydomain in
main.cf
Now after the upgrade with compatibility_level=0 as default the warning
is show up in log.
If I add to main.cf append_dot_mydomain=yes (knowing that the new
default is no) the warning should be gone or not from log?
As I understand from RELEASE_NOTES should not be gone.
And the internal compatibility_level will be incremental with future
incompatible changes to default value and the administrators after
review these values need to increment the compatibility_level too in
main.cf?
Thanks
--
Levi
