Kenneth Marshall a écrit : > On Tue, Oct 07, 2008 at 02:58:52PM +0200, mouss wrote: > >> Johan Andersson wrote: >> >>> Hi, >>> We are thinking to implement some form of greylisting at one of our sites >>> and wonder which one of the many flavors out there >>> that this group have found reliable? >>> I know postfix has its builting one from a while back, but feel unsure if >>> it viable for our site... postgrey and gps seems they added >>> some features that mighe be usable for us... like automatic trunking of >>> the list >>> I just starting to read up on it so I feel very noobish at the moment :) >>> We have six MTA's that receive approx 1million emails a day (total) on >>> roundrobined addresses. >>> Anyone else out there with some experience on the different greylisting >>> models? >>> >> try (Cami's) policyd. it's written in C as a single threaded daemon. it >> uses mysql (myisam unfortunately!). Cami is no more working on it, but it's >> stable enough (and Cami used it in an ISP environment). >> >> it has other features (rate limiting, blacklist, whitelist, ...) >> >> check >> http://www.policyd.org/ >> and look at the "Old policyd V1". >> >> > > If you do not have anything in place, I would recommend looking at > the version 2 policyd that is more database backend agnostic. It is > written in perl and uses DBD/DBI to connect to the backends. That > way you can avoid being locked in to a particular database backend > be it MySQL, PostgreSQL, Oracle, ... > >
I don't know the status of the V2 (I looked at a long time ago, but it was still a in development/design stage). note that some people don't want perl based solutions. For good or bad reasons, but let's avoid a long debate ;-p
