Milter-greylist

Hi,

I have two feature requests:

1. perform a consistency check on the greylist.conf file before reloading it.

I made a rule mistake today when modifying the greylist.conf file, and found
that when it auto-reloaded, the greylist was erroring in my maillog as not
functioning any more.

It would be good for milter-greylist to first check that the greylist.conf
file makes sense to it before a reload, and if it doesn't (contains errors)
then not auto-reload it but notifying about the error in the maillog (or email
the admin).

The way it is now is, it's easy to break with any admin keying the wrong
sequence of acl's or even typo's.

2. have the ability to support an external whitelist file.

I've recently started looking at www.dnswl.org which provides a whitelist of
sites that are "trusted" and should not be greylisted.

Obviously it wouldn't make much sense to use their full IP list and import it
into the greylist.conf file, but it would make sense if I could have in the
greylist.conf file something like:

include dnswl.whitelist

so milter-greylist could then load the whitelist whenever it's updated (or
have milter-greylist have the ability to query the dnswl site to check if an
IP is whitelisted and not greylist if it is).

3. have a web interface to the whitelist system.

It would be good to have a web interface for users to be able to access their
own whitelist system so they can enter "from" and "to" etc rules to manage
their greylist. Maybe even keep these in a MySQL database for each management?

4. tools to pull out relevant information from the /var/log/maillog file.

I'm going to start creating some tools myself for this, but the first tool I'd
like is to get emailed periodically for any "Delayed for" greater than
01:00:00 so that I can look into the problem or simply whitelist the sender.

Other tools like summaries of statistics etc, to pull the information out of
/var/log/maillog and summarise any information available.

Any comments are welcome.

Michael.