Re: [exim] Whitelist using mySQL

Αρχική Σελίδα
Delete this message
Reply to this message
Συντάκτης: Geoge Ascione
Ημερομηνία:  
Προς: 'Heiko Schlichting', exim-users
Αντικείμενο: Re: [exim] Whitelist using mySQL
This looks very interesting however I cannot find any examples on how to
centralize the white list functionality. All the examples use local white
lists which defeats the purpose of having the system centralized. Any ideas
on how to do that? I am also not up to speed on the Berkeley DB. Will have
to do some reading on that.

Thank You
George Ascione

> -----Original Message-----
> From: exim-users-bounces@??? [mailto:exim-users-bounces@exim.org]
> On Behalf Of Heiko Schlichting
> Sent: Thursday, January 04, 2007 8:00 AM
> To: exim-users@???
> Subject: Re: [exim] Whitelist using mySQL
>
> > We have been using greylistd for six months now and it works fairly
> well
> > except for two issues. You must keep the triplets and states file
> > cleared out when it hits a few MB or greylistd consumes large amounts
> > of cpu and stops working. Second we have several inbound MX servers
> and
> > greylistd doesn't have a common DB so each server may or may not
> > greylist mail. This adds delays.
>
> These are the two reasons why we use "postgrey" as greylist daemon.
> Much
> more robust for large installations than greylistd and it is easy to
> run
> a central instance of postgrey which could be asked via TCP.
>
> Although postgrey is designed for postfix we use it with exim. There
> exists
> a README.exim file in the postgrey source which gives the idea how to
> do
> this. The ACL entry for ${readsocket{inet:greylistserver:port} ... is a
> bit
> longish because the postfix communication protocol is verbose but it is
> flexible and works very well on highly loaded mail servers with one
> centralized greylist server. Together with a 3 seconds timeout in the
> readsocket invocation things running smoothly even if postgrey daemon
> is
> not running or answering which might be the case during internal
> database
> cleanup. Until now the daemon did not crached or stoped working.
>
> postgrey uses Berkeley DB as database which I really prefer over an
> additional daemon for the database. As a little drawback postgrey has
> to
> do cleanups which are integrated into the daemon and the daemon does
> not
> answer in this (more or less) short period. Our postgrey daemon has
> a database of 3,500,000 entries to handle and 350,000 auto-whitelisted
> clients. Auto-whitelisting and handling of the subnet masks are also
> advantages of postgrey.
>
> Although I do have some wishes and ideas how it could be improved, I
> really
> recommend to have a look at postgrey. It works with Exim too, of
> course.
>
> Heiko
>
> Heiko Schlichting        | Freie Universität Berlin
> heiko@???       | Zentraleinrichtung für Datenverarbeitung
> (ZEDAT)
> Telefon +49 30 838-54327 | Fabeckstraße 32
> Telefax +49 30 838454327 | 14195 Berlin

>
> --
> ## List details at http://www.exim.org/mailman/listinfo/exim-users
> ## Exim details at http://www.exim.org/
> ## Please use the Wiki with this list - http://www.exim.org/eximwiki/