On 2/1/2010 5:47 PM, Timo Sirainen wrote:
On 2.2.2010, at 0.39, David Halik wrote:
Back to dovecot, actually sqlite might work, because then I don't need a database backend, just a local sqlite regex. The question then being, how would dovecot handle multiple servers? For example:
(if '%u' regexp '^[a-d]' then '192.168.xxx.1 || 192.168.xxx.2 || 192.168.xxx.3' else
if '%u' regexp '^[e-k]' then '192.168.xxx.2 || 192.168.xxx.3 || 192.168.xxx.1' else
..) as proxy_maybeThere are ways of doing this in mysql, with heartbeats etc (which we've discussed before), but then I'm back to mysql again. Maybe mysql just has to be the way to go in this case.
Well, continuing my mail about using DNS: You could create a heartbeat that updates DNS records (with low TTL) when it sees that servers are down. Not as good as everything done automated, but maybe easier than making MySQL redundant?
None of our infrastructure uses "real" DNS. Pretty much all of it is private space that is load balanced through our layer4 using VIPs, which is why I wasn't really active in the DNS discussion. ;) While everything is registered, most are just cnames to the VIP.
I think we're going to have to just go with a mysql database like was discussed in earlier threads, or leave it be completely. One thing I did notice was you discussing that if mysql times out I can have it fall back to regular auth. That might be worth trying...