How amavis reads configuration

[Alexander Wirt]

On Sun, 04 Nov 2018, Patrick Ben Koetter wrote:

> The way amavis reads in configuration today does not meet todays
> requirements:
> 
> - distributions want to add their specific defaults
> - configuration management services want to add site/service specific without
>   touching/breaking default configs
> 
> We can ignore that. I don't want to. I suggest the following:
> 
> - review amavis built-in policies and adapt as (we think to be) apropriate
> - provide a configuration file with documented options one would/could modify
>   in /etc/amavisd.conf
> - provide a mechanism that allows distributions/config management to either
>   - overwrite our one confguration file
>     -> already exists
>   - use our default conf file and try a second conf file, e.g.
>     /etc/amavisd-local.conf
>     -> function exists, but isn't used in amavisd.conf by default
>   - use a directory, e.g. /etc/amavis.d/, and load *.conf
>     -> status unknown
> 
> Opinions? Comments? Ideas?
I would suggest to use the "uncommented, but builtin" option Debian uses for
more than a decade [1]. 

It allows us to have a distributionspecific directory and a conf.d directory
in /etc 

Alex

[1] https://salsa.debian.org/debian/amavisd-new/blob/master/debian/patches/30_conf.d_support_builtin.patch