Milter-greylist

I do use site-specific configurations (likely anyone does somehow)
by creating a number of files named like "greylist-01-common.conf"
and so on for manual whitelists, balcklists and other exceptions,
some of these are distributed via CVS to maintain commonality of
config on several relays, some files can optionally be local.

There's a cron-script which tries to pull updates from CVS, and if
any exist - in just does "cat greylist-??-*.conf > greylist.conf"
and restarts/refreshes the milter service.

This achieves the same goal as include files in a somewhat more
clumsy way, but without changes to milter-greylist, and works
for years.

Also, user-modifiable include files might be a security-breach
source by fooling the daemon into reading (or doing) something
that it shouldn't. This might be avoidable by some policy in the
milter-greylist (i.e. like sendmail is picky about POSIX flags),
or just make a warning in the docs, but the potential problem
should not be ignored and be kept unaware of. :)

//Jim Klimov