On Fri, Feb 06, 2004 at 08:00:06AM -0600, Dave Augustus wrote:
3) HA MAIL STORAGE- by modifying the transports for domains that host
email locally, the email could be sent to 2 (or more) systems at the
same time. This would solve the problem of file system corruption
because rsync nor NFS is used. Although each individual file system
could become corrupted, the mail is stored in 2 separate places on 2
separate computers. Use heartbeat to provide the IMAP server to clients-
it would only be using it's local filesystem and only one IMAP server
would be active at a time. The problem with this scenario is that the
status of emails would be lost if a failover between the 2 servers
occurred. BUT the email would be preserved.
How do you intend to syncronize mail deletion in this scenario? You're
still down to using rsync in some way to ensure that the mail spool on
the backup server doesn't grow without bound.
I think you're better off with solution 2 (shared storage). As an
addition, you could put a couple of LVS[1] servers (1 main + 1 HA) in
front of your mail servers and load balance them instead of HA'ing them.
There is no problem with multiple mail servers accessing the mail spool
at the same time with maildir.
You've mentioned file corruption as a possible problem. What kind of
corruption do you anticipate and where are you expecting it to come
from? Just curious.
[1] http://www.linuxvirtualserver.org/
6 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] keeping two email ser...
