[Dovecot] v2.0 configuration parsing

[Charles Marcus]

On 8/10/2009, Timo Sirainen (tss at iki.fi) wrote:
> (I'm also wondering about if it should be the first rule. Somehow to
> me it comes more naturally that last settings always override
> previous settings.

For config files, I agree.

> If we really want to make first settings come first, then the default
> settings must be at the bottom of dovecot.conf, or they'd need some
> exception.)

Or just have the default settings there as an example, but commented
out. Have an explanation at the top of the config file that if you only
need the default settings, they do not need to be uncommented, and that
the last setting wins (or will cause a warning or error, or whatever you
decide).

I like that I can use postconf -d (show default settings - and this is
why I'd like to have a doveconf -d, as well as doveconf -n), to see if I
have specifically set any defaults, and if I did, delete/comment them.
This limits the settings returned by postconf -n, which makes it easier
to read. I'd like dovecot to have the same capability.

When I did this, I cut the ouput down from 80 lines to less than 40.

-- 

Best regards,

Charles