Milter-greylist

Ethan Burnside <burnside@...> wrote:

> I realize that this isn't exactly what you were thinking when talking
> about using SQL, but we have all of the whitelist/blacklist rules dumped
> from SQL on a regular basis onto the tail end of the conf.  (everytime a
> rule is changed...)  So in our case, we would win instant changes rather
> than having end-users waiting 10 mins for their changes to take effect.

Yep. centralized whitelist would be nice. Using some mecanism offering
rundandcy (DNS, LDAP) would be nice.

But I won't code that before months, I have other projects. 
 
> More directly related to where you were going with the memory/db dumps,
> being able to dump/sync/update ram from a central db would be a solution
> for the fact that even with the sync feature, the servers seem to get
> out of wack with regard to each other.  Think 6 servers, acting as one,
> where periodically a server is taken down for a bit for maintainence,
> etc.  If it could populate the tables in RAM from SQL on startup, then
> sync changes with the SQL server at given intervals, it could be pretty
> handy.

The problem is that a centralized DB means a single point of failure. I
designed the MX sync with the idea that you can kill any server without
killing the whole.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...