Milter-greylist

Hi all
>
> > For scalability, the next step up for Milter-greylist will be to
> > implement a database backend. MySQL is a good candidate.
> >
> > In my discussions with Emmanuel, we have identified the following
> > steps to address this challenge, without breaking any current setups
> > in the mean time. The proposed steps are:
>
> if an db backend is included it would be nice to place config parts
> like whitelists, peers and so on also in the db...
>
> This would make it possible to code a central nice an sweet
> webfrontend for milter-greylist :-)
>
> Mit freundlichen Gruessen || with kind regards
>
> Sven Holz
>
>

Is really so important to have a DB backend? i've more than 20 servers running milter-greylist and they dump the tuples only once a day.

How scalability would be improved? Accessing a mysqldb or any db stored on Hard Disk is slower than accesing memory directly (only mysql memory tables (HEAP) are fast enough.

In the only case i think it might help is in configuration data, but the text file is not so complicated, and adding layers might add problems.

I think that milter-greylisting should focus in performance and the smtp transaction (not body neither headers). In my setup i only use it with spf and some acl to stop DDoS, harvesting, etc. Behind greylisting, i have mailscanner, spamassassin and everything.

Just my 2 cents

Eduardo.