The challenge of customizing Dovecot

[Steffen Kaiser]

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

On Thu, 23 Mar 2017, Robert Moskowitz wrote:
> On 03/23/2017 12:15 AM, Rob McAninch wrote:
>>> On Mar 22, 2017, at 23:53, Robert Moskowitz<rgm at htt-consult.com>  wrote:

>> It is mentioned here
>> http://wiki.dovecot.org/ConfigFile
>> 
>> Debian Jessie has the last line of dovecot.conf as:
>> 
>> !include_try local.conf
>
> Did a tail and see the same line in Centos.
>
> I will have to think about the best way to use this and if it CAN be used for 
> all the customization.
>
> I have some ideas.  Starting with a comment of which conf.d file a particular 
> section is customizing.

This seems to be the end of the example dovecot.conf:

# Most of the actual configuration gets included below. The filenames are
# first sorted by their ASCII value and parsed in that order. The 00-prefixes
# in filenames are intended to make it easier to understand the ordering.
!include conf.d/*.conf

# A config file can also tried to be included without giving an error if
# it's not found:
!include_try local.conf

========

I put my changes into new files sometimes with the same 00-prefix stem. 
There are settings that e.g. to change defaults, which are not picked up 
by other sections if mentioned in the last include file.

- -- 
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBWNN39Hz1H7kL/d9rAQJRiQgAnL/NcZXOCjNEvY+AgUwQrPbAJz98kR/a
1hGb1FlI4Ssd/ApTIUIHLKRuKAlXt+s7EMMg5zbuKzQWNvXpJodRkkHH5WZcHJkX
cMcT7XxKe7ndt8yBbZ9fAFo5XupcvIyLUfCUb50Izr5HsC6ElXuQ6ntRthO+jbtg
AOkxH02loxhXJdMsJkuLkikIZ8vRAwK1Mo0hmyT2VqfMPJt7qx2GcU1b6Fx90jEj
s3PusBI50ONbp5Sa7z7x1VlJYNxc6hf66lqoWvoY7xayEpCXk+QM+PaR2E/Du2TY
x8JTR09KRNo8ouzZoWjwOuLCdDCrDefeQ5sqhAzN11rEZ4aPmMh6mw==
=sHJC
-----END PGP SIGNATURE-----