Date: Tue, 22 Jun 2004 15:46:29 +0200 (CEST) From: "David E. Meier" <dev@eth0.ch> To: questions@freebsd.org Subject: Re: [OT] Re: What's the best possible email failover solution Message-ID: <3016.217.162.71.141.1087911989.squirrel@serv04.inetworx.ch> In-Reply-To: <20040622084726.524bfa39.wmoran@potentialtech.com> References: <20040621132006.2b1a296f.wmoran@potentialtech.com><a22ff294040621115173bad2e0@mail.gmail.com><20040621172520.3544d6fe.wmoran@potentialtech.com><20040621214348.GB63857@happy-idiot-talk.infracaninophile.co.uk><20040621175626.3e762448.wmoran@potentialtech.com><40D76DA3.9090809@mac.com><20040621204111.6e684d45.wmoran@potentialtech.com><40D79FF9.20308@mac.com> <20040622084726.524bfa39.wmoran@potentialtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> The other advantages is it would scale like nobody's business. Since the > data is in postgres, you could use multiple backends (replicated with > Slony) > and have the IMAP daemons contact different back ends if the load got > heavy. With a little work, the system could failover silently as well. It would be very nice indeed. > Like I said, we'll never know till someone tries it. It looks like > Dovecot is going to try it eventually, but it seems like they have > other priorities at this time. "Someone" already stores mails in a database: Oracle (Email Server and Collaboration Suite). I set up the Oracle Email Server 5.2 for a company I worked for earlier. And to express it nicely: It was a nightmare! Mails got stuck and rejected because the system was not capable of writing them into the database. Besides, the support for that system was also =0. We were probably the only ones daring to run the system ;-) I am glad I am running cyrus now. Extremly stable and fast. That system was not well thought through at all. I don't know how much work needs to be done for a database email store, but Oracle wasn't (isn't) able to do so. Dave
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3016.217.162.71.141.1087911989.squirrel>