Geert Hendrickx wrote: > > What drawbacks did you experience? We run a local policyd instance on each > postfix server too, all connecting to a central (not replicated) MySQL. > Policyd's behaviour when MySQL becomes unavailable is configurable, it can > either tempfail (4xx) all incoming e-mail or "dunno" it. > Yes, that is the benefit of doing it that way. But we experienced problems with recurring corruption of the isam tables when the network connections to the db server were interrupted. Apparently myisam tables don't deal well with interrupted connections, from what I found on google.
At any rate, once we moved policyd to the same host as the mysql database, the corruption issue disappeared permanently, but we have the different issue of smtp transactions failing whenever there are connectivity glitches. I'm going to try out hapolicy first, since it's quite a bit quicker and cheaper to set up than full blown mysql replication. Joe
