[Dovecot] current config: doveconf -n vs. postconf -n

Steffen Kaiser skdovecot at smail.inf.fh-brs.de
Tue Apr 1 12:30:29 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 1 Apr 2014, Charles Marcus wrote:

> It proves that you are using the settings you think you are using.
> simply cat'ing the contents of a file that you areediting is not good enough.

No question about that.
I do not want to argue against doveconf -n, but

> Like postconf -n in postfix, doveconf -n dumps the output of the config that 
> the running version of dovecot is qactually using.

"the running version of dovecot is actually using"
seems to be wrong - as I interprete the phrase.

If I change the config when Dovecot v2.2.10 runs, doveconf -n does not 
show the config of the _running_ Dovecot, but the config that will be used 
after reload.

My steps are:
1) make sure Dovecot runs
2) add a non-existing item to mail_plugins
3) login -> success
4) doveconf -n shows modified config
5) doveadm reload
6) login -> fails

I do not know if postconf -n behaves the same. I just wanted to point that 
out. It seems that one has to also request that everybody does a reload, 
too.

- -- 
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEVAwUBUzqxZXD1/YhP6VMHAQKsCwf6A74puuAQiTafzf4agVj45ZPMcKghmfwh
6CEERoSw6VSZ31WLXZ3wcL/58wiReG234gz+uec0Lhn69Tp/lJmCkUX4JJ/a0j2C
4sGs2aaDqy040jJlLNWD87GurCPvOUAal8WiTvurkQJPqUgMDmIeuIQaaMu/qPGi
QMJ+rvHzBPKeWZyORbcKHnjcsnh/VJiRXmo3ISoLoSoL8M7EfGOXEzBYATv58SGK
CFdXLlIiK6vQhTLJx+lyyqfnGsGmMNb/NMwLVl8Kkv/1NsZCdHhVJM28fPqJp5Uo
lq6r1euUc/IqssVVj7adiLqdr/mEifQMLl08Vj2+kUVKjddTVER2Pw==
=65nT
-----END PGP SIGNATURE-----


More information about the dovecot mailing list