Milter-greylist

AIDA Shinra wrote:
 > Oliver Fromme wrote:
 > [...]
 > > By the way, using an SQL database would also provide more
 > > solutions to the MX synchronization problem.  For example,
 > > instead of using milter-greylist's own MX sync feature,
 > > you could simply let several instances of milter-greylist
 > > (on different MX servers) access the same SQL database.
 > > Or -- for improved redundancy -- let each MX server run its
 > > own SQL server instance, and use SQL replication features
 > > to distribute all changes ("INSERT" commands) to the other
 > > SQL servers.  There are probably even more possibilities,
 > > but the ones mentioned are the most obvious ones.
 > 
 > Replication copies data from the master read/write server to other
 > readonly servers.

Not necessarily.  It depends what kind of replication setup
you use.  It's perfectly possible to have two (or more)
"master" servers (read+write) which replicate changes to
each other.

(Whether it makes sense to do that is another question.
But it's not a bad thing to have the choice to do that, and
the possibility comes for free when an SQL database is
supported.)

Best regards
   Oliver

-- 
Oliver Fromme,  secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.

"Life is short (You need Python)"
        -- Bruce Eckel, ANSI C++ Comitee member, author
           of "Thinking in C++" and "Thinking in Java"