Rewriting amavisd.conf

[Patrick Ben Koetter]

What's in amavis.conf and how it is (not) structured, is one of the biggest
problems amavis users have. I've learned that in many amavis trainings I've
given so far. What also adds is the fact, that amavisd.conf seems to be driven
by a developers mindset/view and not an operators/admin one.

I would like to come up with a completely new amavisd.conf. It should:

- Add a section for general service option
- Add sections that group parameters/options by content class (and not functionality)
- Add a section for policy banks

Opinions? Objections?

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