Milter-greylist

Michael Menge a \ufffdcrit :
> I think the great adwantage of milter-greylist is that it can reject an 
> email
> befor the DATA stage. Therefor i don't like and would not use any 
> features that
> would use information from the DATA stage.

I agree milter-greylist should rather concentrate on envelope (pre-DATA) 
stage, maybe SMTP-header stage (but here we already hit the DATA stage ?).

> An SQL backend for the greylist db would be more usefull as it would 
> obsolet
> the mx-sync protocol and the dump of the db

Mmmm... Is that a good idea anyway ? In case of multiple MXes, This 
introduces a single point of failure, or we need complicated setups to 
overcome (SQL mirroring with failover...). MX sync seems quite light and 
efficient in comparison.

More useful would be the ability to include files in greylist.conf, 
which would permit to split configuration in case of long witelists for 
example; I believe it's not possible currently. Another interesting 
feature would be to use SQL and/or LDAP backend for (white, black) 
lists, instead of greylist.conf: this would permit easy dynamic update 
and looong lists without performance/memory hit. Anoter way (which 
doesn't require milter-greylist changes) is to setup a local DNSBL 
server, but this lacks the power of regexps and domain matching.



-- 
Ce message a ete verifie par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a ete trouve.