[Amavisd-new-debian-devel] suggestions for new configuration

[Brian May]

>>>>> "Paul" == Paul Traina <pst@pst.org> writes:

    Paul> I've got some suggestions on simplifying it.

    Paul> 1.  Remove the run-parts stuff from /etc/init.d/amavis.
    Paul> (Specifying the config file in there makes running
    Paul> amavisd-new debug or any other command run by hand a pain in
    Paul> the butt.)  This is REALLY a problem, if you chose to ignore
    Paul> everything else, don't ignore that.

    Paul> 2.  Replace /etc/amavisd.conf with the attached file, or
    Paul> better yet, just patch it into /usr/sbin/amavisd-new.

    Paul> 3.  Move 00-upstream, 10-debian, and 20-debconf to
    Paul> /usr/share/amavisd/conf.d

Seems good, except 20-debconf is a dynamically generated conffile, I
am not sure it is suited for /usr/share...

    Paul> 4.  Rename 30-user to 30-usertemplate, or better yet, move
    Paul> it to /usr/share/doc and instead document to people that
    Paul> they should create a 40-<blah> with just their changes in it
    Paul> (like my 40-local, also attached).

It already is under /usr/share/doc/amavis/examples/sample.conf.gz, and
installed by default.

The big issue with not installing it by default and allowing the
system administrator to install it is the $mydomain variable.

It seems that the following variables:

@local_domains_maps = ( [".$$mydomain"] );
$virus_admin               = "virusalert\@$$mydomain";  # notifications recip.
$mailfrom_notify_admin     = "virusalert\@$$mydomain";  # notifications sender
$mailfrom_notify_recip     = "virusalert\@$$mydomain";  # notifications sender
$mailfrom_notify_spamadmin = "spam.police\@$$mydomain"; # notifications sender

cannot be configured until *after* $mydomain has been setup, however,
$mydomain is very likely to be a setting the administrator may want to
override.

The current version used a broken system of having $mydomain point to
a reference, it is broken though because doing so doesn't actually
achieve anything. I have started converting $mydomain back to a
non-reference variable in my version.

Another possible solution is just have the rule "if you change
$mydomain then you must change the other values in the same config
file", I don't like this, but it is the only solution I can think of
right now.
-- 
Brian May <bam@snoopy.apana.org.au>