On Mon, Jun 08, 2015 at 09:30:59PM -0400, Alex Regan wrote:
> Jun 8 21:20:03 mail02 postfix[22018]: Postfix is running with
> backwards-compatible default settings
Meaning the compatibility level is not set the requisuite minimum
value. This applies whether or not the relevant parameters have
been explicitly set.
/*
* Alert the sysadmin that the backwards-compatible settings are still in
* effect.
*/
if (var_compat_level < CUR_COMPAT_LEVEL) {
msg_info("Postfix is running with backwards-compatible default "
"settings");
msg_info("See http://www.postfix.org/COMPATIBILITY_README.html "
"for details");
msg_info("To disable backwards compatibility use \"postconf "
VAR_COMPAT_LEVEL "=%d\" and \"postfix reload\"",
CUR_COMPAT_LEVEL);
}
Do set the compatibility level to suppress this warning.
> Is there some log level or something else I'm missing to have postfix reveal
> more specifically which setting is forcing the compatibility mode?
The low compatibility level.
> postconf doesn't print any variables that include ${{compatibility_level}.
Which shows that you've explicitly set all the relevant parameters.
The latest defaults are:
$ postconf -d | grep 'compatibility_level'
compatibility_level = 0
append_dot_mydomain = ${{$compatibility_level} < {1} ? {yes} : {no}}
mynetworks_style = ${{$compatibility_level} < {2} ? {subnet} : {host}}
relay_domains = ${{$compatibility_level} < {2} ? {$mydestination} : {}}
smtputf8_enable = ${{$compatibility_level} < {1} ? {no} : {yes}}
> I realize I could just set the compatibility_level variable, but I'd like to
> understand where the deprecated variables are...
Check "postconf -d" output.
--
Viktor.
