Wietse Venema:
-X Edit the main.cf configuration file, and remove the parameters
given on the postconf(1) command line. The file is copied to a
temporary file then renamed into place. Specify a list of
parameter names, not name=value pairs. There is no
On Wed, 7 Mar 2012, Quanah Gibson-Mount wrote:
--On Tuesday, March 06, 2012 2:05 PM -0500 Wietse Venema
wie...@porcupine.org wrote:
Quanah Gibson-Mount:
--On Tuesday, March 06, 2012 1:11 PM -0500 Wietse Venema
wie...@porcupine.org wrote:
Hi Wietse,
I noted in my initial email
--On Tuesday, March 06, 2012 2:05 PM -0500 Wietse Venema
wie...@porcupine.org wrote:
Quanah Gibson-Mount:
--On Tuesday, March 06, 2012 1:11 PM -0500 Wietse Venema
wie...@porcupine.org wrote:
Hi Wietse,
I noted in my initial email why this is not desirable solution.
I ignored your
On Wed, 7 Mar 2012, Quanah Gibson-Mount wrote:
# postconf -# policy_time_limit
After:
/etc/postfix/main.cf:
# policy_time_limit = foo
# policy_time_limit = bar
The problem with this approach is that if you later re-enable the
policy, it will not remove the #'d out entries. Over
Larry Stone:
On Wed, 7 Mar 2012, Quanah Gibson-Mount wrote:
# postconf -# policy_time_limit
After:
/etc/postfix/main.cf:
# policy_time_limit = foo
# policy_time_limit = bar
The problem with this approach is that if you later re-enable the
policy, it will not
--On Wednesday, March 07, 2012 4:25 PM -0500 Wietse Venema
wie...@porcupine.org wrote:
This feature is available with Postfix 2.10 and later.
It uses the same code as -#, except it produces no output. And as
with -#, there will be no command to perform the reverse operation.
--On Wednesday, March 07, 2012 3:03 PM -0600 Larry Stone
lston...@stonejongleux.com wrote:
An aside in this: why is this so important for you? What's wrong with
using a text editor to clean up main.cf? Until this thread came along, I
didn't even know you could use postconf to edit main.cf;
With the newer postfix releases (such as 2.9.x), some keys only exist when
a feature is enabled. For example: policy_time_limit
If I set policy_time_limit and then later disable using a policy, I can't
find a way to get it deleted from main.cf with postconf. If I set it to an
empty value,
Quanah Gibson-Mount:
With the newer postfix releases (such as 2.9.x), some keys only exist when
a feature is enabled. For example: policy_time_limit
Correct.
If I set policy_time_limit and then later disable using a policy, I can't
find a way to get it deleted from main.cf with postconf.
--On Tuesday, March 06, 2012 1:11 PM -0500 Wietse Venema
wie...@porcupine.org wrote:
Hi Wietse,
I noted in my initial email why this is not desirable solution.
# postconf -# policy_time_limit
After:
/etc/postfix/main.cf:
#policy_time_limit = foo
#policy_time_limit = bar
The problem
Quanah Gibson-Mount:
--On Tuesday, March 06, 2012 1:11 PM -0500 Wietse Venema
wie...@porcupine.org wrote:
Hi Wietse,
I noted in my initial email why this is not desirable solution.
I ignored your objection, because it made no sense to me. I have
learned that is it better to ignore things
11 matches
Mail list logo