On 11/09/2021 20:05, Wietse Venema wrote:
Nick Howitt:
Partly answering my own question, "postconf -o
body_checks=regexp:/etc/postfix/body_checks" seems to do the right thing
in that the output of the command shows it is set
No it doesn't. Where did you get the idea from that "postconf -o
body_checks=whatever" shows the actual value of body_checks?
In reality, "postconf -o name=value" sets the "name" parameter
*internaly* in the postconf command, so that you can see the effect
that it would have if used as $name in other config parameters.
Like:
postconf -x -o stress=yes
Shows the values of OTHER parameters whose value depends on
stress.
It does not show the settings in main.cf or master.cf.
Wietse
Perhaps I was unclear in what I meant and misinterpreted what I saw.
When I run "postconf -o ...." all the values of the the various
parameters scroll by before you get the command prompt back. You can
then scroll up the the parameter you set and you can see the value you
set. e.g:
[root@server ~]# postconf -o body_checks=regexp:/etc/postfix/body_checks
2bounce_notice_recipient = postmaster
access_map_defer_code = 450
access_map_reject_code = 554
address_verify_cache_cleanup_interval = 12h
<snip>
body_checks = regexp:/etc/postfix/body_checks
<snip>
virtual_recipient_refill_limit = $default_recipient_refill_limit
virtual_transport = virtual
virtual_uid_maps =
[root@server ~]#
I interpreted this, perhaps mistakenly, as if this were now the running
config of postfix. It does not update main.cf, just the current running
config and a reload would get you back to the values in main.cf. I was
then trying to leverage this understanding.
Nick
