Kevin Baker wrote:
Forrest,
<snip long text>
---postfix+dbmail+mysql---
This seems to solve everything and is easy to setup. 2
node clusters. Each cluster having a primary and
secondary. Secondary uses standard mysql replication with
primary as "master" giving us a hot spare. We will
probably look into master master replication over the
cluster in the future if things go well.
We will be using simple ip takeover to handle fail over to
the secondary if the primary goes down.
Mail is then routed through postfix to the correct server
cluster based on mysql configuration for load balancing.
So to scale we just add a cluster every x number of users.
No need for remote storage solutions... we will get better
performance off the cheap local drives, have fail over
through the cluster and scale by adding clusters. Each
cluster is so cheap it seems to offset the advantage of
SAN or NAS... although that was definitely something we
were looking at early on.
I have a question about delivery:
How do you want to handle delivery to aliases. Say you have the
following scenario:
2 dbmail servers (A and B)
Postfix routes a mail, [EMAIL PROTECTED], to server A. On server A, the
aliases [EMAIL PROTECTED] expands to a local delivery (no problem), and a
delivery to [EMAIL PROTECTED]
Is the mail just sent, eventually going through Postfix again and ending
up on server B?
This would seem the simplest solution, but might be a bit demanding on
resources.
Do you perhaps have a solution that's more clever?
Thanks,
Ilja
--
Ilja Booij
IC&S B.V.
Stadhouderslaan 57
3583 JD Utrecht
www.ic-s.nl
T algemeen: 030 6355730
T direct: 030 6355739
F: 030 6355731
E: [EMAIL PROTECTED]
