How amavis reads configuration

[Patrick Ben Koetter]

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?

p at rick


-- 
[*] sys4 AG
 
https://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG,80333 München
 
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief
Aufsichtsratsvorsitzender: Florian Kirstein