Re: Git for redundant mail servers

From: Jon Seymour <jon.seymour@gmail.com>
Date: Apr 23, 2005, 08:24 UTC
Message-ID: <2cfc403205042301243841fe0c@mail.gmail.com>
In-Reply-To: <1114238562.3419.29.camel@localhost.localdomain>

On 4/23/05, David Woodhouse <dwmw2@infradead.org> wrote:

Show 17 quoted lines

> Random alternative use for git... we could use it to provide a cluster
> of redundant mail delivery/storage servers.
> 
> The principle is simple; you use something like a set of Maildir
> folders, stored in a git repository. Any action on the mail storage is
> done as a commit -- that includes delivery of new mail, or user actions
> from the IMAP server such as changing flags, deleting or moving mail.
> These actions are actually fairly efficient when Maildir folders are
> stored in a git repository -- the IMAP model is that mails are
> immutable, and flag changes are done as renames.
> 
> In the normal case where all the servers are online, each commit is
> immediately pushed to each remote server. When a server is offline or
> separated somehow from the rest of the group, it's going to have to do a
> merge when it reconnects -- we'd implement a Maildir-specific merge
> algorithm, which really isn't that hard to do.
>

This is a cool idea. When the concept is rendered this way, it sounds a lot like some of the core principles in the architecture of the Lotus Notes replication engine. I've always thought it would be cool to have an open engine that provided similar functionality to the Lotus Notes replication engine without the naff programming environment that sits on top. I can see how the git concepts and code could provide the basis of such a solution. Very cool.

jon.